Integrate with Pingdom

This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.

What does the integration offer?

With the Pingdom integration, you can take advantage of Jira Service Management’s advanced alert & notifications management capabilities, such as escalations, on-call schedule management, and extensive alert notification controls.

How does the integration work?

When an alert is created in Pingdom, an alert is also created in Jira Service Management automatically through the integration. When the alert is closed in Pingdom, the related alert is also closed in Jira Service Management.

Set up the integration

Pingdom is an API-based integration. Setting it up involves the following steps:

Add a Pingdom integration in Jira Service Management
Configure the integration in Pingdom

Add a Pingdom integration

Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.

Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.

To add a Pingdom integration in Jira Service Management, complete the following steps:

Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “Pingdom”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the integration URL.
You will use this URL while configuring the integration in Pingdom later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Pingdom

To configure the integration in Pingdom, complete the following steps:

Go to the Pingdom dashboard.
Select Settings > Integrations > Add integration.
Select "Webhook" for Type.
Enter a name into Webhook name.
Paste the API URL copied previously into Webhook URL.
Check if the Active checkbox is selected.
Select Save integration.
The Webhook integration is ready to use in the "Uptime" and "Transaction" checks.
Ensure Jira Service Management Webhook integration is selected in the Check settings.

Sample payloads sent from Pingdom Close

HTTP check [POST] (in JSON format)

{
  "check_id": 12345,
  "check_name": "Name of HTTP check",
  "check_type": "HTTP",
  "check_params": {
    "basic_auth": false,
    "encryption": true,
    "full_url": "https://www.example.com/path",
    "header": "User-Agent:Pingdom.com_bot",
    "hostname": "www.example.com",
    "ipv6": false,
    "port": 443,
    "url": "/path"
  },
  "tags": [
    "example_tag"
  ],
  "previous_state": "UP",
  "current_state": "DOWN",
  "state_changed_timestamp": 1451610061,
  "state_changed_utc_time": "2016-01-01T01:01:01",
  "long_description": "Long error message",
  "description": "Short error message",
  "first_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Stockholm, Sweden"
  },
  "second_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Austin, US"
  }
}

Ping check [POST] (in JSON format)

{
  "check_id": 12345,
  "check_name": "Name of Ping check",
  "check_type": "PING",
  "check_params": {
    "hostname": "www.example.com",
    "basic_auth": false,
    "ipv6": false
  },
  "tags": [
    "example_tag"
  ],
  "previous_state": "UP",
  "current_state": "DOWN",
  "state_changed_timestamp": 1451610061,
  "state_changed_utc_time": "2016-01-01T01:01:01",
  "long_description": "Long error message",
  "description": "Short error message",
  "first_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Stockholm, Sweden"
  },
  "second_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Austin, US"
  }
}

IMAP check [POST] (in JSON format)

{
  "check_id": 12345,
  "check_name": "Name of IMAP check",
  "check_type": "IMAP",
  "check_params": {
    "hostname": "www.example.com",
    "basic_auth": false,
    "encryption": false,
    "ipv6": false,
    "port": 143
  },
  "tags": [
    "example_tag"
  ],
  "previous_state": "UP",
  "current_state": "DOWN",
  "state_changed_timestamp": 1451610061,
  "state_changed_utc_time": "2016-01-01T01:01:01",
  "long_description": "Long error message",
  "description": "Short error message",
  "first_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Stockholm, Sweden"
  },
  "second_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Austin, US"
  }
}

Transaction check [POST] (in JSON format)

{
  "check_id": 12345,
  "check_name": "Name of transaction check",
  "check_type": "TRANSACTION",
  "check_params": {
    "encryption": true,
    "port": 443,
    "url": "https://www.example.com/"
  },
  "tags": [
    "example_tag"
  ],
  "previous_state": "FAILING",
  "current_state": "SUCCESS",
  "state_changed_timestamp": 1451610061,
  "state_changed_utc_time": "2016-01-01T01:01:01",
  "description": "Error message",
  "first_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Stockholm, Sweden"
  },
  "second_probe": {
    "ip": "123.4.5.6",
    "ipv6": "2001:4800:1020:209::5",
    "location": "Austin, US"
  }
}

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community