See below for a detailed overview of how to configure your Pingdom integration in the NS1 portal and your Pingdom account.
The NS1 integration only supports Pingdom BeepManager.
A data source is an object within the NS1 platform that is associated with an NS1 monitor, third-party integration, or integration via NS1 API. Each monitor or integration observes an endpoint in your network and communicates status changes back to the relevant data source object configured in the NS1 platform. Once notified of a change, the data source engages its associated data feeds to update the relevant DNS resources (records or answers). All types of data sources use similar methods to ingest, process, and distribute the data to the edge. The DNS servers use this real-time data to inform traffic routing decisions. Refer to Understanding NS1 data sources & feeds for details.
Follow the instructions below in the NS1 portal (i.e., http://my.nsone.net) to configure Pingdom as an NS1 data source.
In the NS1 portal, navigate to the Integrations page from the main navigation.
Click the + button in the upper right corner to add a new data source.
Under Pick a source type, click the Pingdom logo, and then enter a name for the new data source (for internal reference only).
Click Create Data Source, and then click Create new feed from this data source (same button).
Enter a name for the data feed (for internal reference) and the Pingdom check ID. For now, enter a placeholder value in this field. We'll update this later after creating the Pingdom alert.
You are redirected to the Incoming Feeds tab. The new Pingdom data source appears in the list of configured data sources with an icon next to it displaying the number of associated data feeds. For now, there is just one data feed associated with the data source, but you can create more feeds from the Pingdom data source later on.
Scroll to the bottom of the page, and locate the Pingdom data source and feed you just created. Record the Feeds URL associated with this data feed. You'll need to enter this in the Pingdom portal in the next step.
Log in to your Pindgom account and navigate to the Integrations page. Click Add Integration.
Next to Type, select Webhook from the dropdown menu, and then enter a name for the webhook and then enter the URL copied from the NS1 portal in the previous step.
Click Save integration.
Navigate to the Uptime page (under Experience Monitoring in the side navigation) and click Add Check.
Enter a name of the check, and then navigate to the Network tag. Select the type of check (e.g., TCP, Ping, etc.). Next to Domain/IP, enter ns1.com.
Scroll down to the Connect Integrations section of the modal, and select the checkbox next to NS1 Webhook Alert (or the appropriate NS1 webhook you created earlier) to connect this uptime check to NS1. NS1 recommends setting no delay on notifications. Fill in all other fields as you wish and hit Create check.
NS1 recommends setting no delay on notifications.
Complete the additional form fields as desired, and then click Create check.
Click the new uptime check from the list to display the Edit Check modal. When this modal is open, you can view the check ID in your browser search bar (at the end of the URL). Copy this value as you will need to enter it in the NS1 portal to complete the configuration.
To complete configuration, you must modify the data feed you created in step 1 — replacing the placeholder check ID with the real one generated in the previous step.
In the NS1 portal, navigate to Integrations > Incoming Feeds.
Scroll down to the Pingdom data source in the list, and navigate to the feed you created in Step 1. Click the pencil icon to the right of it to edit the Pingdom data feed.
Replace the Pingdom check ID with the actual check ID generated in Step 2. The, click Submit.
Once you configure the new data source and data feed from Pingdom, you can connect the data source to the appropriate DNS answer(s) to configure automatic updates. For example, as the Pingdom alert detects an endpoint is down, it notifies the NS1 platform and automatically adjusts the relevant answer metadata to indicate that answer (i.e., endpoint) is down.
In the NS1 portal, navigate to DNS > Zones, and then select the name of a zone to drill down into zone details. Specifically, select the zone containing the record with the relevant DNS answer.
Click the name of the record containing the relevant answer to drill down into record details — including a list of answers associated with that record.
Next to the relevant DNS answer, click the menu icon to the right of it and select Edit Answer Metadata.
From the list of metadata fields on the left, locate the Up metadata and click the "Feeds" icon to the right of it to display a list of available monitors and data sources.
Select the Pingdom data feed you created earlier to attach it to the Up metadata for this answer. Then, click Ok to exit the modal.
Now, when the Pingdom alert detects a change in the status of the monitored endpoint, it will automatically adjust the metadata value (i.e., up = true/false). If the Filter Chain configuration for this record contains the "Up" filter, it will refer to this metadata field for each answer — eliminating unavailable answers (i.e., endpoints).