Leaving Opsgenie
Atlassian stopped selling Opsgenie on 4 June 2025 and shuts it off on 5 April 2027. StatOSS takes Opsgenie's Alert API at its own address, and imports schedules, escalation policies and integrations from an Opsgenie account.
curl -X POST https://api.statoss.com/v2/alerts \
-H "Authorization: GenieKey <the source's key>" \
-H "Content-Type: application/json" \
-d '{"message": "Checkout error rate above 5%",
"alias": "checkout-errors", "priority": "P1"}'What Atlassian is doing
Opsgenie sales and sign-ups ended on 4 June 2025. On 5 April 2027 access to Opsgenie is shut off and any data not migrated is deleted, according to Atlassian's Opsgenie page. Atlassian's path is Jira Service Management or Compass. In Jira Service Management, heartbeats, voice calls and incoming call routing are on Premium and Enterprise, and the Incident Command Center and incident templates are not there, by Atlassian's list of feature changes.
Side by side
| StatOSS | Jira Service Management | |
|---|---|---|
| Heartbeats | Opsgenie's heartbeat pings, to a heartbeat monitor of the same name, on Hobby and Pro | Premium and Enterprise |
| Voice calls | None | Premium and Enterprise |
| Incoming call routing | None | Premium and Enterprise |
| Slack and Microsoft Teams | Alerts in Slack with Acknowledge and Resolve buttons, and in Teams, on Hobby and Pro | A team's Slack and Teams alert integrations on every plan; incident ChatOps in Slack, Teams and Zoom, and global alert integrations, on Premium and Enterprise |
| Incident Command Center | None; an alert opens an incident, internal until published | Not available |
| Incident templates | Templates for incidents and maintenance | Replaced by incident configurations |
Facts about the other product were read from its own site on 6 October 2026. Prices and limits change; check theirs before deciding, and tell [email protected] if something here is out of date.
What the import brings
On Pro, owners and admins import under On-call, Import, with an Opsgenie API key with Read and Configuration access, from the US or the EU region. The key is used for the import and not kept. A preview shows what the import makes and what it leaves out, and the import makes what was previewed.
- People are matched to the team by email. Invite them first; until then their turns go to the next person in the rotation.
- Each rotation becomes a schedule of its own, with its time restrictions and overrides, since Opsgenie pages every rotation in a schedule at once.
- Escalations become escalation policies. Opsgenie counts each rule's delay from when the alert opened; StatOSS waits between levels, so the delays are turned into waits.
- API, Prometheus and Grafana integrations become sources with new keys. After the import, the list gives each one's base URL and key to put in the tool.
What stays behind
- Phone, SMS and push contact methods. Each person adds their own ways in StatOSS. StatOSS makes no phone calls and sends no SMS.
- Routing rules. A source pages through its page's escalation policy, or one picked for it.
- Integrations of other types, which send in a format of their own. Those tools get a source by hand, as PagerDuty, Opsgenie or Sentry senders.
- Rotations with a turn for a team or an escalation, and rules that notify a team. Rules for the next or previous person page whoever is on call, and levels stop at acknowledgement, not at close.
- Heartbeats, alert history, teams and schedules turned off in Opsgenie.
Pointing senders at StatOSS
Anything that sends to api.opsgenie.com or api.eu.opsgenie.com sends to https://api.statoss.com instead: the same paths, the same GenieKey header, with the source's key. Create, acknowledge, close and notes, by id, tiny id or alias, and the request status answer as Opsgenie's do. Alertmanager takes the address as the api_url of its opsgenie_configs, Kibana as the URL of an Opsgenie connector, and Opsgenie's Go and Python SDKs as their host. Grafana and Zabbix take https://api.statoss.com/v2/alerts, as the Alert API URL of an Opsgenie contact point and as opsgenie_api.
A heartbeat pings /v2/heartbeats/<name>/ping on the same address. Add a heartbeat monitor with that name to the page, and each ping counts for it; a missed one is an outage and an alert. The on-call docs list every address, PagerDuty's and Sentry's too.
Reaching people
On Pro each person picks their ways: email, Pushover (at emergency priority, repeated until acknowledged, if they want), ntfy and Telegram, and when each is used once they are paged. A source can also send to the page's destinations: Slack, Discord, Microsoft Teams, a webhook and the rest. An alert repeats until someone acknowledges it, from the dashboard, the links in the email, Pushover, the buttons in Slack, the API, or the sender itself.
Price
Pro is $15 a month: 3 people included and $5 a month for each one after, up to 25, with 50 alert sources, schedules, escalation and the import. Hobby is $4 a month for one person with 3 sources and repeats until acknowledged, without schedules, escalation or the import. Both include the status page and the monitors.
Moving over
- Sign up, pick Pro, and invite the team with the addresses they have in Opsgenie.
- Make a status page; sources belong to one. On Pro it can be private.
- Under On-call, Import, pick Opsgenie, the region, the key and the page. Preview, then import.
- Change each tool's base URL and key as the list says, and add a heartbeat monitor for each Opsgenie heartbeat.
- Each person sets their ways under On-call, Your notifications.
Opsgenie keeps working until 5 April 2027, so the two can run side by side while the senders move. The import section of the docs has the details.