Pingdom

Prerequisites

• An active Pingdom account from which data is to be ingested.

• You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.

• The API credentials to provide Hevo access to your Pingdom account data.

• You must be logged in as an Account Owner, Editor, or Admin user, to obtain the API key. Else, you can obtain it from your account editor, owner or administrator.

Obtaining the API Token

The API token that you generate in Pingdom does not expire. Therefore, you can use an existing token or create a new one to authenticate Hevo on your Pingdom account.

Note: You must log in as an Account Owner, Editor, or Admin user to perform these steps.

To obtain the API token:

1. Log in to your Pingdom account.

2. In the bottom left corner of the page, click the Arrow ( ) icon to expand the left navigation panel.

3. In the Home navigation panel, Settings section, click Pingdom API.

   

4. In the Pingdom API page, click Add API token.

   

5. In the Add API token pop-up window, specify the following:

   

   • Name: A unique name for your API token.

   • Access Level: Select the Read access permission to allow Hevo to ingest your data.

6. Click Generate token.

7. In the API token pop-up dialog, under the Your new API token section, click Copy corresponding to the API token to copy it and save it securely like any other password. Use this token while configuring your Hevo Pipeline.

   

Configuring Pingdom as a Source

Perform the following steps to configure Pingdom as the Source in your Pipeline:

1. Click PIPELINES in the Navigation Bar.

2. Click + CREATE in the Pipelines List View.

3. In the Select Source Type page, select Pingdom.

4. In the Configure your Pingdom Source page, specify the following:

   

   • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.

   • API Token: The API token that you generated in your Pingdom account to allow Hevo to access your data.

5. Click TEST & CONTINUE.

6. Proceed to configuring the data ingestion and setting up the Destination.