DEV Community

Cover image for What Is Opsgenie? Integrations, Status Pages, Terraform, and Grafana OnCall
Yathartha Shekhar
Yathartha Shekhar

Posted on Originally published at fluidify.ai

What Is Opsgenie? Integrations, Status Pages, Terraform, and Grafana OnCall

Cross-posted from the Fluidify blog.

Opsgenie is Atlassian's alerting and on-call management tool, and it's being shut down on April 5, 2027. This reference guide covers what Opsgenie is and the vocabulary it uses, how Opsgenie integrations work, what the Opsgenie status page features do, how to manage Opsgenie with its Terraform provider, and how Opsgenie compares with Grafana OnCall, the other popular on-call tool that has also been wound down.

Key takeaways

  • Opsgenie routes alerts from monitoring tools to the right on-call person through schedules, escalation policies, and notification rules. Atlassian bought it in 2018 and stopped selling it on June 4, 2025. It shuts down on April 5, 2027.
  • Opsgenie's "status page" features were internal Service Status pages for stakeholders. Public status pages came through its two-way integration with Atlassian Statuspage, a separate product.
  • The official Opsgenie Terraform provider covers teams, users, schedules, rotations, escalations, integrations, and more. Grafana OnCall's open-source edition was archived in March 2026, so both tools now point users to a cloud suite: Jira Service Management for Opsgenie and Grafana Cloud IRM for Grafana OnCall.

What is Opsgenie?

Opsgenie is an incident alerting and on-call management service. Monitoring tools, cloud services, and scripts send it alerts. Opsgenie decides who should know about each one based on on-call schedules and escalation rules, then notifies them by push notification, SMS, voice call, or email, and keeps escalating until someone acknowledges or closes the alert.

Opsgenie dates to 2012. Atlassian announced it was acquiring Opsgenie in September 2018 for about $295 million, roughly $259 million in cash and the rest in restricted shares according to Atlassian's SEC filing, and made it the alerting layer alongside Jira and Statuspage. In 2025 Atlassian folded Opsgenie's alerting and on-call features into Jira Service Management, stopped selling Opsgenie on June 4, 2025, and set end of support for April 5, 2027. Atlassian says data that hasn't been moved by then is deleted. Our post on Opsgenie shutdown dates covers that timeline.

Opsgenie glossary

Alert: a notification that something needs attention, created by an integration or the API. Alerts have a priority from P1 to P5 and can be acknowledged, snoozed, and closed.

Alias: a deduplication key on an alert. A new alert with the same alias as an open one is treated as a duplicate.

Incident: a higher-level record for a service-impacting problem, which can group alerts and drive stakeholder communication.

Team: a group of users that owns integrations, schedules, escalation policies, and routing rules.

Schedule: who is on call when, for a team, in a given timezone.

Rotation: a repeating pattern inside a schedule, hourly, daily, or weekly, with participants in order and optional time restrictions.

Override: a one-off change to who's on call for a time window, without editing the rotation.

Escalation policy: an ordered list of rules saying who to notify, after what delay, if the alert is still unacknowledged or still open. Our guide to Opsgenie escalation policies and notification rules explains these in detail.

Routing rule: a team-level rule that sends an alert to an escalation policy or schedule based on conditions and time of day.

Notification rule: a per-user setting that decides how that person is contacted for each event, such as a new alert or the start of their shift.

Integration: a connection that sends alerts into Opsgenie or sends Opsgenie actions out to another tool. Each has its own API key.

Heartbeat: a check that expects a periodic ping from a system and creates an alert if the ping stops.

Service: a representation of something you run, used by incidents and Service Status pages.

Stakeholder: a user who receives incident updates but doesn't respond to alerts.

Opsgenie integrations overview

Opsgenie integrations are how alerts get in and how actions get out. They come in a few kinds:

API integration: gives you an API key for sending alerts from your own code, scripts, or CI. A team API integration's key only works for that team's alerts, while a global one can make any API request. Our Opsgenie API guide covers keys and the alert endpoints.

Email integration: gives you an email address that turns incoming messages into alerts, useful for tools that can only send email.

Monitoring and cloud integrations: prebuilt connections for monitoring, logging, and cloud tools, which map the tool's alert format to Opsgenie alerts automatically.

Outgoing and bidirectional integrations: connections that also send Opsgenie actions back out, such as creating a ticket when an alert opens, or closing the source alert when the Opsgenie alert closes. Chat tools like Slack and Microsoft Teams are in this group.

Opsgenie Edge Connector: a connector you run on your own infrastructure so Opsgenie actions can trigger scripts and reach systems that aren't on the public internet.

Integrations can be owned by a team, which routes their alerts to that team, or be global.

What happens to integrations when you leave Opsgenie

Integrations are usually the most work in a migration, because each one lives in the sending tool's configuration, not in Opsgenie. Moving to Jira Service Management, Atlassian's docs say chat integrations like Slack and Teams have to be reconnected by hand, bidirectional integrations only work on JSM Premium and Enterprise, and about two dozen outdated integration versions can be moved but not created new. Moving to any other tool, every alert source has to be repointed at the new tool's endpoint. Our Opsgenie migration checklist has an inventory step for exactly this.

Opsgenie status page features

"Opsgenie status page" usually means one of two different things.

Service Status pages (internal): inside Opsgenie, each service has a Service Status page listing its incidents with their status, creation time, and latest update, plus written updates for open incidents. Stakeholders can view these pages read-only and subscribe to a service to get notified. Responders post updates to the page with Send update from the incident. These pages are for people inside your organization, not customers. Atlassian notes that stakeholders aren't available on old plans from before November 2, 2018.

Public status pages via Statuspage: for customer-facing status, Opsgenie integrates two ways with Atlassian Statuspage, which is a separate product. Atlassian's docs describe Statuspage incidents creating Opsgenie alerts, with later updates added as notes, and Opsgenie actions creating or resolving Statuspage incidents. Closing an incident in Statuspage closes the matching Opsgenie alert. Third-party status page tools such as Statuspal also have Opsgenie integrations.

If you rely on either, check them during a migration. Internal Service Status pages depend on Opsgenie's services and stakeholders, so they need an equivalent in the destination tool. The Statuspage connection needs to be rebuilt against whatever replaces Opsgenie as your alerting tool, even if Statuspage itself stays.

For comparison, FluidifyAI Regen, our on-call tool, includes a basic public status page that shows active incidents and those resolved in the last seven days, drawn from its incident list. It's not a replacement for a full Statuspage setup with components and subscribers, but it covers the "is something broken right now" case without another product.

Opsgenie Terraform provider and infrastructure as code

Teams with many Opsgenie teams and schedules often manage them as code. The official Opsgenie Terraform provider is published by Opsgenie on GitHub under the MPL-2.0 license. As of October 2026, its latest release is v0.6.40 from October 2025.

Configuration: the provider takes an api_key, or reads OPSGENIE_API_KEY from the environment, and an optional api_url, which EU accounts set to api.eu.opsgenie.com. The provider docs say to create an API integration with read and write permissions to get the key.

Resources: opsgenie_team, opsgenie_user, opsgenie_user_contact, opsgenie_schedule, opsgenie_schedule_rotation, opsgenie_escalation, opsgenie_team_routing_rule, opsgenie_notification_rule, opsgenie_notification_policy, opsgenie_alert_policy, opsgenie_api_integration, opsgenie_email_integration, opsgenie_integration_action, opsgenie_heartbeat, opsgenie_maintenance, opsgenie_service, opsgenie_service_incident_rule, opsgenie_incident_template, and opsgenie_role.

A minimal team with a weekly rotation looks like this:

provider "opsgenie" {
  # api_key from OPSGENIE_API_KEY
  api_url = "api.opsgenie.com"
}

resource "opsgenie_team" "payments" {
  name        = "payments"
  description = "Payments on-call"
}

resource "opsgenie_schedule" "payments_primary" {
  name          = "payments-primary"
  timezone      = "America/New_York"
  owner_team_id = opsgenie_team.payments.id
}

# Assumes opsgenie_user.alice and opsgenie_user.bob are defined elsewhere.
resource "opsgenie_schedule_rotation" "weekly" {
  schedule_id = opsgenie_schedule.payments_primary.id
  name        = "weekly"
  start_date  = "2026-10-12T09:00:00Z"
  type        = "weekly"
  length      = 1

  participant {
    type = "user"
    id   = opsgenie_user.alice.id
  }

  participant {
    type = "user"
    id   = opsgenie_user.bob.id
  }
}
Enter fullscreen mode Exit fullscreen mode

The provider's docs note that rotation start and end times only accept minutes of 0 or 30. Other values are rounded to the nearest half hour.

Using Terraform during the shutdown: if your Opsgenie setup is in Terraform, your state is already a complete inventory of what to migrate, which makes the first step of a migration much easier. Plan the end too. Once Opsgenie is gone, the provider has nothing to talk to, so remove Opsgenie resources from your configuration and state as part of decommissioning rather than leaving plans that fail after April 5, 2027. Our post on escalation policies as code covers how to keep on-call config in Git whichever tool you move to.

Opsgenie vs Grafana OnCall

Opsgenie and Grafana OnCall were both common choices for on-call scheduling and alert escalation, and both have now been wound down in favor of a larger cloud product.

Opsgenie Grafana OnCall
Vendor Atlassian Grafana Labs
Deployment SaaS only Open source (self-hosted) or Grafana Cloud
License Proprietary AGPLv3 (OSS edition)
Status End of sale June 4, 2025, shutdown April 5, 2027 OSS in maintenance mode March 11, 2025, archived March 24, 2026
Successor Jira Service Management Grafana Cloud IRM
Pricing at end Per user: Free up to 5 users, then $9.45 to $31.90 per user per month (annual) OSS free. Grafana Cloud IRM free for 3 active users, then a $19 platform fee plus $20 per active user
Strength Mature escalation and notification rules, Jira and Statuspage integration Tight integration with Grafana dashboards and alerting

Where they differed: Opsgenie was a standalone SaaS product with deep escalation options and a large integration catalog. Grafana OnCall was built around Grafana's own alerting, with an open-source edition teams could run themselves.

Where they ended up: both now send users to a bundled cloud suite. Grafana says it moved development to Grafana Cloud IRM, which combines the former OnCall and Incident apps. Self-hosted OnCall stopped receiving new features in March 2025, and the repository became read-only in March 2026, with the Cloud Connection feature for SMS, phone, and push on self-hosted stacks also ending. Grafana also maintains an open-source migrator that moves Opsgenie schedules, escalation policies, integrations, and notification rules into Grafana Cloud IRM.

Which to pick now: neither, in its original form. If you were choosing between Opsgenie and Grafana OnCall, the real choice today is between their successors, Jira Service Management and Grafana Cloud IRM, or a different tool entirely. If self-hosting was why you picked Grafana OnCall, Regen can import Grafana OnCall schedules as well as Opsgenie's. Our Opsgenie alternatives comparison covers the options, and the Regen vs Grafana OnCall page goes deeper on that pair.

FAQ

What is Opsgenie used for? Routing alerts from monitoring and other tools to the right on-call engineer, based on schedules and escalation policies, and notifying them until someone responds.

Is Opsgenie being discontinued? Yes. Atlassian stopped selling Opsgenie on June 4, 2025, and ends support on April 5, 2027, when it shuts down and deletes data that hasn't been moved.

Who owns Opsgenie? Atlassian, which acquired it in 2018.

Does Opsgenie have a status page? Opsgenie has internal Service Status pages for stakeholders. Public status pages come from its integration with Atlassian Statuspage or third-party status page tools.

Is there an official Opsgenie Terraform provider? Yes, opsgenie/opsgenie on the Terraform Registry, maintained in Opsgenie's GitHub organization. It covers teams, users, schedules, rotations, escalations, routing rules, integrations, heartbeats, services, and more.

How many integrations does Opsgenie have? Opsgenie supports a long catalog of prebuilt integrations plus generic API, email, and webhook options. The exact count has changed over time, so check Atlassian's integration list for the tool you need.

Is Grafana OnCall still available? The open-source edition was archived on March 24, 2026 and is read-only. Grafana Cloud IRM is the supported product.

Opsgenie vs Grafana OnCall: which is better? Both have been retired in their original form. Compare their successors, Jira Service Management and Grafana Cloud IRM, against other on-call tools instead.

If you're replacing Opsgenie

Most of what's in this guide, from integrations and status pages to Terraform state, becomes a migration inventory once you decide to leave. If you're weighing destinations, FluidifyAI Regen imports Opsgenie schedules and escalation policies at a flat $100 a month with no per-seat pricing, and our Opsgenie-to-Regen walkthrough shows the full path.

Top comments (0)