OpsGenie Integration
Connect OpsGenie to sync incidents, on-call schedules, and MTTR into Koalr's engineering metrics.
OpsGenie Integration
Connecting OpsGenie lets Koalr pull incident data for DORA change failure rate (CFR) and mean time to recovery (MTTR) calculations.
What Koalr syncs
- Incidents — status, priority, responders, open/close timestamps
- On-call schedules — who is on call per team per rotation
- Alert escalations — escalation policy details
- MTTR — calculated from incident open → close timestamps, attributed to the deployment that triggered the alert (matched by service + timestamp proximity)
Prerequisites
- OpsGenie account with Owner or Admin role
- An API key with Read scope (Configuration Management → API key management)
Setup
- In Koalr, go to Settings → Integrations.
- Click Connect next to OpsGenie.
- Paste your OpsGenie API key.
- Select the OpsGenie region: US (
api.opsgenie.com) or EU (api.eu.opsgenie.com). - Click Save. Koalr immediately validates the key and starts a historical sync covering the past 90 days.
Migrating from PagerDuty?
If your organization is moving from PagerDuty to OpsGenie, use Koalr's OpsGenie Migration Tool at Settings → OpsGenie Migration. It extracts your PagerDuty incident history, transforms it to OpsGenie format, and imports it — preserving your MTTR trend data.
MTTR attribution
Koalr correlates incidents to deployments using a ±4 hour window around each deployment's triggeredAt timestamp. When a match is found:
- The incident's resolution time is attributed as MTTR for that deployment
- The deployment is counted as a change failure in your DORA CFR metric
- The incident appears in Delivery → Deploy Risk → Incident History linked to the PR
Permissions
The API key only needs Read access. Koalr never writes to OpsGenie (no alert creation, no acknowledgement).
Troubleshooting
Incidents not appearing: Ensure the API key has access to the correct OpsGenie team. Team-scoped API keys only return incidents for that team.
MTTR looks incorrect: Check that your deployment webhooks are configured correctly. Koalr needs accurate triggeredAt timestamps for incident attribution. See Webhook Setup.