Available now
OpsGenie + OnCallReady: Auto-Resolve Alerts Before the April 2027 Shutdown
Migrate off OpsGenie in 30 minutes — without paying 2.4x for JSM. OnCallReady bridges your existing OpsGenie escalation policies through an AI engine that auto-resolves low-severity alerts before they reach the on-call rotation.
Replace or augment — your choice
Replace before EOL
- OnCallReady handles P3/P4 autonomously, on-call handles P1/P2
- Import OpsGenie schedules, rotations, escalation policies
- Cut over cleanly before the April 5, 2027 shutdown
- Audit trail replaces manual incident notes
Augment — bridge mode
- Point OpsGenie webhook at OnCallReady — AI runs first
- Resolved = OpsGenie escalation never fires
- Unresolved = forwarded back into OpsGenie API v2 (opsgenie.com/v2/alerts)
- Migration in your own time — no big-bang cutover needed
How it works
Spin up an OpsGenie webhook integration pointing at OnCallReady. We attempt auto-resolution; anything we can't close we forward back into OpsGenie's existing escalation chain so the on-call engineer still gets paged with full diagnostic context.
Monitoring tool fires alert
│
▼
OpsGenie — webhook to OnCallReady
│
▼
OnCallReady — matches runbook, executes fix
│
├── Resolved ──▶ Post to Slack. OpsGenie never fires.
│
└── Unresolved ──▶ OpsGenie API v2 (opsgenie.com/v2/alerts)
severity: original priority
details: {
attempted_runbook: "disk-full",
actions_run: ["purge_logs", "purge_tmp"],
failure_reason: "disk still > 85% after purge",
diagnostic_context: {...}
}
→ OpsGenie pages on-call with full context
Signal → Action table
| OpsGenie priority |
OnCallReady behavior |
OpsGenie outcome |
| P5 — disk > 90% |
Disk Full Remediation (28s avg) |
Never fires — resolved autonomously |
| P4 — service degraded |
Service Restart & Recovery |
Never fires if recovery succeeds |
| P3 — memory high |
Memory Exhaustion runbook |
Never fires if stabilized |
| P2 — DB pool exhausted |
Attempt DB Connection Pool runbook |
Fires with diagnostic context if runbook fails |
| P1 — production down |
Immediate forward to OpsGenie |
Always fires — no autonomous delay on P1 |
| Any — no runbook match |
Diagnose, capture context, escalate |
Fires with pre-populated diagnostic data |
Setup in 3 minutes
Configure OnCallReady to forward unresolved incidents back into OpsGenie's API v2 so existing escalation policies still fire.
OnCallReady configuration
# 1. In OpsGenie: Settings → Integrations → Add Webhook
# URL: https://oncallready.polsia.app/api/alerts
# 2. In OnCallReady config — enable OpsGenie fallback:
OPSGENIE_API_KEY=your_opsgenie_api_key_here
OPSGENIE_FORWARD_UNRESOLVED=true
OPSGENIE_MIN_PRIORITY=P2 # P3/P4/P5 auto-resolved, never escalated
# 3. OpsGenie → Settings → Integrations → Add API integration
# Copy the API key above. OnCallReady uses it to post unresolved
# incidents back to opsgenie.com/v2/alerts so your escalation chain fires.
# Result: OnCallReady resolves low-priority automatically, OpsGenie
# escalates the rest with full context — same coverage, far fewer pages.
What stays on-call
OnCallReady doesn't replace your escalation chain — it protects it from noise:
- P1 incidents — always forwarded to OpsGenie immediately, no autonomous delay
- Any incident you configure with
opsgenie_always: true — bypasses OnCallReady entirely
- Security incidents — never auto-resolved, always human-reviewed
- Autonomous action failures — escalated via opsgenie.com/v2/alerts with full diagnostic context
- Incidents during configured maintenance windows — OnCallReady suppresses, OpsGenie stays silent
Related
OpsGenie users typically run the full OpsGenie migration playbook alongside Datadog and PagerDuty connectors:
Move before Mar 2027.
Atlassian's cutover gun lands April 5, 2027. Migrate on your own timeline.