Pingdom Server Monitor Alerts
The built-in Pingdom Server Monitor Alerts trigger initiates flows when it receives a request from a webhook in Pingdom Server Monitor.
- Go to the Triggers tab in the palette, expand the App Triggers section and drag the trigger onto the canvas.
- Double-click the trigger (or click the pencil icon).
- Set the authenticating user, then copy the URL — you'll use this to set up the webhook in Pingdom Server Monitor. Alternatively, you can create an integration user to use as the authenticating user. The Pingdom Server Monitor trigger only supports URL authentication.
- Click the Flood Control tab to edit the trigger's default flood control settings. For more information about these settings, see Trigger Flood Control.
- Connect the steps you want to run when xMatters receives a request to that URL.
You're now ready to configure Pingdom Server Monitor to target the trigger.
Configure Pingdom Server Monitor to send requests to the trigger URL
To have Pingdom Server Monitor send alerts to the flow trigger, you need to configure a webhook and set it to use the trigger URL.
- On the Pingdom Server Monitor homepage, go to your company settings drop-down menu (located on the top-right corner of the screen), and select Notifications.
- Under Notification Channels, click Add Webhook to create a new webhook.
- On the New Webhook page, fill in the following fields:
- Webhook Name: give your webhook a unique, descriptive name.
- Webhook URL: paste the trigger URL you copied from the Pingdom Server Monitor Alerts trigger in Flow Designer.
- Add the target names of any recipients you want xMatters to notify when the monitor creates an alert.
- For example, if you want to notify Emma Pearson, Mary McBride, and the on-call members in the Monitor Team responsible for the service, you'd add ?recipients=epearson,mmcbride,monitor%20team to the URL.
- You must URL-encode any special characters or spaces in the target names.
- Click Submit to create the webhook.
- To check that alerts go to the right recipients, click Send a test post.
You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use.
The trigger has the following outputs you can use as inputs to steps further along the flow.
|List of targeted recipients. Recipients are set by adding a recipients query parameter to the trigger URL when you configure the webhook in Pingdom Server Monitor.|
|Signal Mode||Determines the path the flow will take based on the value of the Lifecycle parameter.|
|Signal ID||Key or identifier used to terminate or correlate events/signals.|
|ID||Unique identifier of the alert.|
Current state of the alert. Available options are:
|Server Hostname||Host name of the server that triggered the alert in Pingdom Server Monitor.|
|Server Name||Name of the relevant Pingdom Server Monitor server.|
|Time||Time when the alert entered the Lifecycle state.|
|Title||Title of the alert as provided by Pingdom Server Monitor.|
|Trigger||Description of the trigger condition fired in Pingdom Server Monitor.|
|URL||Direct URL to the Pingdom Server Monitor alert.|
|Raw Request||JSON representation of the request. You can parse the raw request if you need additional details beyond the standard outputs.|