Pingdom Webhook

You can configure the Pingdom webhook to post notifications to a custom integration endpoint when events of interest occur.

Before you begin

This integration was validated with Pingdom on February 10, 2021.

Before you start to set up your integration, make sure:

  • You have an active Pingdom account.

  • You have the necessary permissions to create alerts and notifications channels in Pingdom.

  • Pingdom can make requests to external endpoints over port 443. This is the default.

  • You have created a Moogsoft API key and have access to a copy of it.

Configure the integration in Moogsoft

To configure the integration:

  1. Click Data Config > Ingestion Services.

  2. Under Ingestion Services, click Create your own integration.

  3. Click ADD NEW INTEGRATION.

  4. In the MOOGSOFT ENDPOINT field, provide a unique integration name.

    You can give it the same name as the target application or customize the name according to your business needs.

  5. In the API DESCRIPTION field, enter a description (optional) of the purpose for the API or other information relevant to your business needs.

  6. Under DATA TYPE, select Events.

  7. Click Save.

The custom API is now provisioned.

Note

Leave this browser tab open as you will use it later on in the procedure.

Note

See Create your own integration for additional help.

Define the webhook in Pingdom

To create a new webhook in Pingdom, do the following:

  1. Log in to Pingdom.

  2. Click Settings.

  3. Click Integrations.

  4. Click Add Integration.

  5. Complete the following information.

    1. Type: Webhook

    2. Name: Moogsoft

    3. URL: Enter the endpoint URL and API key in this field using the following format: https://moog:[API Key]@Moogsoft Endpoint URL

      Example: https://moog:user_!ac1d2345-678d-91e2-34fg-56h7891i23j@api.moogsoft.ai/express/v1/integrations/custom/1aaab122343b/Pingdom

      The endpoint displays in Moogsoft under Data Config > Ingestion Services > Create Your Own Integration > <Your Integration> > Configuration Information after you save your integration

      Example:

      https://api.moogsoft.ai/express/v1/integrations/custom/cc11a9e714d1/your_application

    4. Active: Checked

  6. Click Save Integration.

Map Pingdom data to event fields

To map Ping data to event fields in Moogsoft, do the following:

  1. In the Pingdom application, configure a Pingdom check (monitor) to send alerts to your custom integration. Send a sample payload when the check is configured. For more information on how to complete this process, refer to the Pingdom documentation.

    NOTE: If possible, generate an event to send a payload to your Moogsoft Enterprise endpoint instead of clicking Test. Mapping is easier with a real event payload because some of the fields are not present in the test version.

  2. Go back to your Moogsoft tab.

    If you closed your tab, navigate to the Map your Data section of your integration:

    1. Click Data Config > Ingestion Services.

    2. Click Create your own integration.

    3. Click the custom integration that you created in the first part of this procedure.

  3. Under Map Your Data, click the received payload to view the fields.

  4. Scroll down and map the source fields from Pingdom to target fields relevant in Moogsoft.

    The mappings for SourceDescriptionServiceCheck and Severity in the following table should work for most cases, but you may prefer to map the fields according to your own business needs.

    • Click Add a Mapping to add new rows for additional mappings.

    • To add a default value, click inside a field, scroll to the end of the list of possible source fields, and then click Default Value. You can then type in the default text to display.

    • To create a Tag: mapping in the Moogsoft Target Fields column, click inside a field and then click Add Tag.

    • After creating a mapping, click Add to save it.

    Pingdom Source Fields

    Moogsoft Target Fields

    check_params.hostname

    Source

    description

    Description

    check_type

    Check

    current_state

    Severity

    first_probe.ip

    Tag: probeDetails

    importance_level

    Tag: importance

    tags

    Tag: pingdomTags

    first_probe.location

    Tag: location

    custom_message

    Service

    check_name

    Class

  5. Click Map Values and map the following severity values:

    Source Fields

    Moogsoft Severity

    Down

    Clear

    Up

    Major

    Click Save.

  6. Scroll down to the Set Your Deduplication Key section.

    Review the default deduplication key.

    Important

    Customizing the deduplication key is an advanced feature. The default fields are recommended unless customizations are required for your specific use case.

    Default Deduplication Key

    source

    class

    service

    check

  7. Click TEST DEDUPLICATION KEY.

  8. Click SAVE AND ENABLE.