Forum Discussion
I'm sure I exactly follow your logic. My understanding is that when using the AutoTask integration, each alarm in LM would create a ticket in AT, meaning there would be a one-to-one ratio. Is your intent just to list all open tickets in AT and indicate whether or not the corresponding LM alarm is open/cleared?
I'd start with the REST API. Look at the /santaba/rest/alert/alerts resource. This returns JSON that looks like this. The "items" object is a list of alarms. You could cycle through that looking only at the alarms where "cleared" is equal to "true". There should be an ##EXTERNAL_TICKET_ID##, but it's not showing in the documentation and I need to fix my Postman so i can do a pull against a system that actually has that field.
{ "items": [ { "SDT": {}, "ackComment": "string", "acked": true, "ackedBy": "string", "ackedEpoch": 0, "alertValue": "string", "chain": "string", "chainId": 0, "clearValue": "string", "cleared": true, "customColumns": {}, "dataPointId": 0, "dataPointName": "string", "detailMessage": {}, "endEpoch": 0, "id": "string", "instanceDescription": "string", "instanceId": 0, "instanceName": "string", "internalId": "string", "monitorObjectGroups": {}, "monitorObjectId": 0, "monitorObjectName": "string", "monitorObjectType": "string", "nextRecipient": 0, "receivedList": "string", "resourceId": 0, "resourceTemplateId": 0, "resourceTemplateName": "string", "resourceTemplateType": "string", "rule": "string", "ruleId": 0, "sdted": true, "severity": 0, "startEpoch": 0, "subChainId": 0, "threshold": "string", "type": "string" } ], "searchId": "string", "total": 0 }
Related Content
- 11 months agoAnonymous
- 10 months ago