# Pingdom

## Overview​

This webhook integration lets you track a variety of events logged by Pingdom.

Available events are:

• Incident assigned
• Incident notification of being closed

## Setup​

Integrating Pingdom's webhooks into Snowplow is a two-stage process:

1. Configure Pingdom to send events to Snowplow
2. (Optional) Create the Pingdom events tables into Amazon Redshift

## Configure Pingdom​

First login to your Pingdom account and click on the Alerting button which will be on the left hand side of the screen.

You should now see the following screen:

Fill in the name of your new Alerting Endpoint; for example: 'Snowplow Pingdom Webhook'.

• Select Url/Webhook for the How should we contact you? dropdown menu.
• Fill in your Collector URL in the Webhook URL field.

For the Webhook URL field you will need to provide the URI to your Snowplow Collector. We use a special path to tell Snowplow that these events are generated by Pingdom:

http://<collector host>/com.pingdom/v1?aid=<company code>

The aid= name-value pair in your URI's querystring is optional; this is the app_id parameter taken from the Snowplow Tracker Protocol. You can use it to specify which company in Pingdom these call complete events belong to. Putting it all together, our setup screen now looks like this:

If you want, you can also manually override the event's platform parameter like so:

http://<collector host>/com.pingdom/v1?aid=<company code>&p=<platform code>

Supported platform codes can again be found in the Snowplow Tracker Protocol; if not set, then the value for platform will default to srv for a server-side application.

After we have finished adding the contact method simply click Save Settings.

You will now need to add this endpoint to your Alert Policies for the webhook to be used.