Question

Automatic Incident creation via SolarWinds Pingdom Alert

  • 19 December 2023
  • 5 replies
  • 76 views

Badge +6

We are looking to create a webhook in IFS. We are using SolarWinds Pingdom as a Web application monitoring system so whenever web app is down it generates an alert. Pingdom has capability to send a payload to Webhook with status change details from success to failure. Basically, we are trying to create IFS incident automatically when Pingdom generates an alert. Has anyone done something like this?


5 replies

Userlevel 2
Badge +9

You should be able to do this by having Solwarwinds send a request to assyst to create the incident via either the REST API or a  Remote Upload ETM channel. 

If Solwarwinds can construct a valid XML or JSON assyst REST request then this is possibly the simpler route.

The ETM route offers more flexibility in terms of the message format and the ability to transform the message before updating assyst. For example ETM could use Solarwinds own message format, or try and identify an appropriate CI to to use, or identify an existing ticket to update.

If you need to respond to Solarwinds with the assyst ticket reference then either use REST, or ETM Response mappers (added in version 1.7).

Badge +6

Thanks, Paul, for the quick response.

Were already using REST API from SolarWinds to generate incidents in Assyst.

However, the Pingdom tool does not have that option but instead mentions using a Webhook for 3rd party integration.

Pingdom sends this JSON response to webhook Post endpoint (see attachment for example).

 

Badge +6

https://www.pingdom.com/resources/webhooks/

Userlevel 2
Badge +9

ETM can (probably) handle this. Create a remote upload channel. In a mapper create a variable called “check” to parse the JSON from pingdom (a mapper variable with the expression “JSON.parse(inbound);”.

In subsequent mapper fields you can access this variable. For example you could get the description via the expression “check.description” and use this to specify the assyst event remarks.

One possible issue is that ETM remote upload channels require http basic authentication headers to be included in the request. I don’t know if pingdom supports this.

Badge +6

Ok thanks for the additional information Paul.

Appreciate it and happy holidays.

Reply