Forum Discussion
We have accomplished this 90% on our own, but would love to see LM take it the rest of the way.
- We have a added a custom field in ConnectWise to store the resource name
"customFields": [ { "id": 11, "value": "##HOSTNAME##" } ]
- We have a nightly PowerAutomate flow which looks at all tickets sourced by LM, and checks if the custom field value matches a config within the company. It can then be attached with a simple POST call.
POST URL:
https://{URL}/v4_6_release/apis/3.0/service/tickets/{ticketID}/configurations
BODY:
{
"id": "{ConfigID}"
}
- Justin_Lanoue12 days ago
Advisor
Just wanted to bring this back to life as I noticed LogicMonitor added a "Connectwise Configuration Sync" to the Integration.
With that being said, I reviewed it, and it seems lackluster as it just creates configurations and doesn't auto-map to existing configurations which needs to be done manually or via a script by pre-populating all the resources with their associated IDs.
Regardless, I am also using Power Automate to attach the configurations to tickets along with the creating/syncing the configurations so I experimented/revisited to see if LogicMonitor can attach the configurations.ConnectWise doesn't allow you to attach the configurations using the ticket creation POST...BUT LogicMonitor has the "Escalated" status in the integration which can reference the ##EXTERNALTICKETID##. Therefore, you can utilize that to attach your configurations.
Example:
Stage 1: Creates the ticket
Stage 2: Attaches the configuration
Stage 3: Do Nothing to prevent the further attaching attempts.
Payload for Escalated.
Does anyone see any downside with this? The only thing I can think of is someone acknowledging the alert within 1 minute of the escalation interval but that would be rare as we don't really ACK the alerts in LogicMonitor anyways.