We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design Masterclass · Reliability Resilience
Free preview: the first 2 parts of this 7-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design courseread the rest of this lesson in
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design coursein Reliability Resilience
This lesson is part of the full System Design Masterclass. Unlock it along with 769 other lessons for a one-time payment.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime Access18 Foundation lessons are free, no payment needed. Try them now
It is easy and good
“It is really nice and good Please join the course”
In 2018 Atlassian acquired Opsgenie for 295 million dollars. That is a lot of money for a tool that pages engineers at night. But Atlassian was not buying a paging tool. They were buying the operations layer that Jira and Confluence were missing.
Jira tracks work. Confluence holds documentation. Neither one could wake an engineer at 3 AM, route an alert to the right team, or escalate when nobody responded. Opsgenie filled that gap and, because Atlassian owns both products, the Jira integration is tighter than any third-party connector could achieve. Incident creates Jira ticket. Jira comment flows back to the incident timeline. Resolve closes the ticket. All automatic.
Opsgenie handles millions of alerts daily across Atlassian cloud customers. It supports more than 200 integrations including Alertmanager, New Relic, Datadog, and Grafana. For companies already deep in Atlassian's ecosystem, Opsgenie is the path of least resistance for on-call management.
Opsgenie processes alerts through a pipeline: ingest, policy, routing, schedule resolution, notification waterfall. Each stage is rule-based and auditable, which was a deliberate product decision so customers in regulated industries could explain every paging decision to auditors.
| Stage | What happens | Key feature |
|---|---|---|
| Ingest | Receives events from 200+ integrations | , New Relic, Datadog, custom webhooks |
| Alert policy | Enrichment, dedupe, priority assignment | Rule-based, not ML. Every decision is traceable. |
| Team routing | Matches service tags to owning team | Each team owns its own rule set in isolation |
| Schedule resolution | Resolves to current on-call from layered rotations | Primary + backup + manager in one escalation path |
| Notification waterfall | Mobile push, then SMS, then phone call | Mobile-first hits 92% ack in 3 minutes vs 75% for SMS-first |
The rule-based engine was Opsgenie's key differentiator at acquisition time. PagerDuty was investing in machine learning for alert routing. Opsgenie bet that regulated customers (banking, healthcare, government) would pay for explainability. That bet is what made the product worth 295 million dollars to Atlassian.