Get started with Opsgenie as a user
Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
Use Opsgenie’s Updown.io Integration to forward website's status notifications to Opsgenie. Opsgenie determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, iOS and Android push notifications, and escalates alerts until the alert is acknowledged or closed.
Updown.io sends JSON notifications when a website is down, which creates an alert in Opsgenie. As soon as the website gets up back, the alert created is closed automatically.
Alias should be set while adding a new website to monitor in Updown.io. Otherwise, alert will be created in the case of website is down but will not be closed.
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 Updown.io and select Add.
Specify who is notified of Updown.io notifications using the Responders field. Autocomplete suggestions are provided as you type.
Copy the integration URL which includes Opsgenie’s endpoint as well as the API key.
Select Save Integration.
In Updown.io, navigate to the Settings page by clicking Settings in the nav bar.
Navigate to the Webhooks section.
Fill the URL field with the integration URL copied from Opsgenie.
Click Save.
All set! Now manage your Updown.io notifications at Opsgenie and leverage its full alerting functionality.
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
35
36
37
38
39
40
41
[
{
"event": "check.up",
"check": {
"token": "jzu3",
"url": "https:\/\/asdf.cm",
"alias": "asdf",
"last_status": null,
"uptime": 97.338,
"down": false,
"down_since": "2018-06-07T11:18:06Z",
"error": "Couldn't connect to server",
"period": 30,
"apdex_t": 0.5,
"string_match": "",
"enabled": true,
"published": false,
"disabled_locations": [
],
"last_check_at": "2018-06-07T11:18:36Z",
"next_check_at": "2018-06-07T11:19:06Z",
"mute_until": null,
"favicon_url": null,
"custom_headers": {
},
"ssl": {
"tested_at": "2018-06-07T11:17:16Z",
"valid": false,
"error": null
}
},
"downtime": {
"error": "Couldn't connect to server",
"started_at": "2018-06-07T11:18:06Z",
"ended_at": null,
"duration": null
}
}
]
Was this helpful?