Webook HTTP Response Capturing/Parsing | Archive

Jerry_Wiltse · 2015-07-13T20:40:16Z

Every ticket system that could make use of Webhooks for opening ticket for new alerts generates a ticket number for every new alert. Most provide the ticket number as JSON or XML in the response. Most also support updating and closing of said tickets via API, however they require the "Ticket Number" as a parameter. A key to more advanced and flexible ticket integration would be for Logicmonitor to have a new field on every alert called "Ticket Number". That field could be populated by parsing the API response, an SMTP email reply, or manually entered. The tricky thing is that all email and HTTP responses from various ticket systems are diverse in format. So, then we will at least regular expression matching on HTTP header/body or email subject/body. Maybe copy functionality from the datapoint parser, enabling XPATH and JSON PATH. Would be amazing. Alternatively, you could start to add your own code to handle each unique integration. Seems unmanageable though. Better to let people "Script" their own parsing, and provide examples in the documentation as a guide for popular systems.

MoreDiscussions

Webook HTTP Response Capturing/Parsing | Archive | LogicMonitor Community