Open an alert on a confirmed outage
The alert is created once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with Opsgenie.
One API key, and a confirmed outage opens an alert that follows your on-call rules and closes itself when the site is back.
What lands in Opsgenie
Everything the alert pipeline sends into Opsgenie is on this list, and nothing beyond it. Read it once and you know what your team will see.
Close it on recovery
The recovery closes the alert by its alias, so nobody has to acknowledge a page for a site that is already back.
Add a note instead of a second alert
A reminder about an ongoing outage is appended as a note to the open alert, so a long incident stays one thread.
Deduplicate by alias
The alias is built from incident and channel, so repeated events land on the alert you already have instead of opening another.
Send it at your priority
Alerts go out at the priority you set on the channel, P3 unless you choose otherwise.
Tag and describe the alert
Every alert carries the tags uptimeify and monitoring plus the incident type, with site, customer, status code and locations as details.
Stay in your region
Only the official EU and US API hosts are accepted, so an EU-hosted account never has its alerts sent through the US endpoint.
Send a test alert
The dashboard fires a test while you set it up, so a wrong API key is caught before the first real page.
Keep the API key encrypted
The key is stored encrypted rather than as plain text in the channel configuration.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create an API integration
In Opsgenie open Settings, then Integrations, and create an API integration. On Free and Essentials it sits under Teams, then your team, then Integrations.
API key
1a2b3c4d-5e6f-7890-abcd-ef1234567890Stored encrypted
2. Copy the API key
Copy the key the integration shows and note whether your account is hosted in the EU or the US.
3. Paste it into Uptimeify
Add the key as an Opsgenie channel, pick the region and priority, assign the monitors, and send the test alert.
Before you connect Opsgenie.
Yes. The recovery closes the alert by the same alias the outage opened it with, so Opsgenie closes the alert it created rather than leaving a stale page behind.
Because the Alert API can close and annotate an existing alert by alias. A webhook rule can only push new alerts, which would turn one long outage into a stack of pages.
The one you pick on the channel. Only the official EU and US API hosts are accepted, so an EU-hosted account keeps its alerts inside the EU endpoint.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Opsgenie, email, webhook or Slack do not draw on it.
Opsgenie accepts an alert with a 202 and nothing else counts as success, so anything different is recorded as a failed delivery on the Alerts tab under History & Logs, with the status code it returned.
Atlassian closed Opsgenie to new customers in June 2025 and ends support on 5 April 2027. Until then the integration carries. If you are moving to Jira Service Management Operations, the Jira channel is already here.
Every alert, where your team already works.
Connect Opsgenie once, and every confirmed outage opens an alert that closes itself when the site is back.