Get started with Opsgenie as a user
Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
Integrate Opsgenie with Pingdom
What does Opsgenie offer Pingdom users?
Opsgenie’s Pingdom integration enables Pingdom users to take advantage of Opsgenie’s advanced alert & notifications management capabilities such as escalations, on-call schedule management, and extensive alert notification controls.
Functionality of the integration
When an alert is created in Pingdom, an alert is also created in Opsgenie automatically through the integration.
When the alert is closed in Pingdom, the related alert is also closed in Opsgenie.
Add Pingdom Integration in Opsgenie
You can add this integration from your team dashboard
If you're using Opsgenie's Free or Essentials plan, or if you’re using Opsgenie with Jira Service Management's Standard plan, you can only add this integration from your team dashboard as the Integrations page under Settings is not available in your plan.
Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only.
To do that,
Go to your team’s dashboard from Teams,
Select Integrations, and select Add integration.
Follow the rest of the steps to complete the integration.
Go to Settings > Integrations. Search for Pingdom and select Add.
Specify who is notified of Pingdom alerts using the Responders field. Auto-complete suggestions are provided as you type.
Copy the Webhook URL.
Select Save Integration.
Configuration in Pingdom
Go to the Pingdom dashboard.
Click Integrations > Integrations > Add integrations.
3. Select Webhook as integration "Type".
4. Enter a valid name into "Webhook name" field.
5. Paste Webhook URL into the "Webhook URL" field.
6. Make sure "Active" field is checked.
7. Click Save integration.
8. Opsgenie Webhook integration is ready to use into "Uptime" and "Transaction" checks.
9. Make sure Opsgenie Webhook integration is enabled at "Check" settings.
Advanced Configuration Settings in Opsgenie
Sample payloads sent from Pingdom Close
HTTP check [POST]:
JSON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
{
"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]:
JSON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
{
"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]:
JSON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
{
"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]:
JSON
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
{
"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?