Opsgenie and Jira Service Management
Observe opens, updates, acknowledges and closes alerts in Opsgenie and in Jira Service Management (JSM) Operations, its successor. Both use the same alert API, so they behave the same.
Set up Opsgenie
- In Opsgenie, open Teams, pick the team, then Integrations → Add integration → API. Copy its API key and save.
- In Observe, go to Notifications & reports → Add a channel → Opsgenie and paste the key.
- If your Opsgenie account is in the EU (app.eu.opsgenie.com), tick EU region account: alerts then go to api.eu.opsgenie.com instead of api.opsgenie.com.
- Choose a priority and, optionally, a responder team, then Send test.
Set up Jira Service Management Operations
- In Jira Service Management, open your team's Operations page, then Integrations → Add integration, and search for API.
- Name it (for example Observe), optionally pick an assignee team, select Continue, then Turn on integration. Copy the API key.
- In Observe, add a channel of type Jira Service Management (Opsgenie successor) and paste the key.
- Choose a priority and, optionally, a responder team, then Send test.
Observe sends to the JSM integration API with the key in a GenieKey header; no cloud ID or site name is needed:
POST https://api.atlassian.com/jsm/ops/integration/v2/alerts
Authorization: GenieKey YOUR_INTEGRATION_KEY
Fields and priority
The alert in one line, without the "Observe" prefix, cut to 130 characters.
A stable key per problem, so repeats dedupe into one alert and the recovery closes it (see below).
The full alert text.
Automatic: P1 for a monitor marked critical, P3 for everything else. Or a fixed P1 to P5 per channel.
The monitor's URL.
Observe
Observe, the alert category (uptime, ssl, domains, servers, health, content) and the monitor's tags.
event_type, site_id, site_url, incident_id, reason, started_at, status_code, error_message and a link to the monitor, when they apply.
Optional: a team name set on the channel. Left blank, the integration's own team gets the alert.
Dedupe and auto-close
Every alert carries an alias: incident-{id} for downtime, site-{id}-{event} for other monitor alerts (a performance recovery uses the budget alert's alias), server-{id}-{check} for servers and org-{id}-{check} for application health. Opsgenie and JSM fold repeats with the same alias into one alert, and Observe uses the alias to update and close it:
Monitor goes down (or any other problem event)
POST /v2/alerts
Creates the alert.
Still-down reminder
POST /v2/alerts/{alias}/notes?identifierType=alias
Adds a note instead of a new alert.
Someone acknowledges the incident in Observe (dashboard, API or MCP)
POST /v2/alerts/{alias}/acknowledge?identifierType=alias
Acknowledges the alert, with who did it in the note.
Monitor recovers
POST /v2/alerts/{alias}/close?identifierType=alias
Closes the alert. Recoveries always reach on-call tools, even when the monitor is snoozed or the channel is outside its hours.
Send test
create, then close
Opens a test alert and closes it straight away.
On-call channels always deliver immediately: digests and quiet hours do not apply to them. Event, team and tag routing do.
Migrating from Opsgenie
Timeline
- June 4, 2025: end of sale. Opsgenie can no longer be bought or signed up for.
- April 5, 2027: end of support. Atlassian turns Opsgenie off and deletes data that was not migrated.
- Atlassian moves Opsgenie's alerting and on-call into Jira Service Management.
Sources: Atlassian's announcement, Set up an API integration and the JSM Operations integration events API (checked November 2026).
What changes
- Address: api.opsgenie.com (or api.eu.opsgenie.com) becomes api.atlassian.com/jsm/ops/integration. The paths after it, the GenieKey header and the alert fields stay the same.
- Key: use the API key of an integration in JSM Operations.
- Terms: Opsgenie teams, schedules, escalations and routing rules live under a team's Operations page in JSM. Responder team names in Observe must match the JSM team names.
- Nothing else changes in Observe: the channel keeps its name, events, team, tags, delivery hours, priority and responder team.
Step by step
- In Atlassian, move Opsgenie to Jira Service Management (Atlassian's guided migration), or set up JSM Operations with your teams and schedules.
- In JSM, add an API integration to the team that should be paged (see Set up JSM above) and copy its key.
- In Observe, open Notifications & reports. Each Opsgenie channel shows an end-of-support notice: select Switch to JSM, paste the key, and select Switch and send test.
- Check that the test alert appeared in JSM and closed. If it failed, the error is shown and the channel is marked failing; fix the key and use Send test again.
FAQ
- Do I have to do anything before April 5, 2027?
- Yes, if you have an Opsgenie channel. After that date Atlassian switches Opsgenie off, and alerts sent to it are lost. Switch the channel to JSM before then.
- Does my Opsgenie API key work in JSM?
- Use the key of an API integration created in JSM Operations. Atlassian's migration may carry integrations over, but whether an old Opsgenie key keeps working at the JSM address is not documented, so create or copy the key from JSM.
- What about alerts that are open when I switch?
- Observe closes alerts through the channel's current address. An Opsgenie alert still open when you switch is not closed by Observe, so switch while nothing is down, or close it by hand.
- My JSM site is in the EU. Which address does Observe use?
- api.atlassian.com, the only address in Atlassian's integration API reference. Atlassian does not document a separate EU address for it (not verified). If your integration page in JSM shows a different API URL, contact support before switching.
- What about Compass?
- Compass's alert API is different (api.atlassian.com/compass/cloud/{cloudId}/ops/v1/alerts with an email and API token, per Atlassian's Compass REST reference), so it is not a channel. Use JSM Operations for paging.
- Is there a PagerDuty-style severity?
- Opsgenie and JSM use priority (P1 highest to P5). Mark a monitor as critical to have Automatic send P1 for it.