PagerDuty Integration
PagerDuty is Koalr's primary incident data source. Koalr reads incident timelines, on-call schedules, and responder data to calculate MTTR, change failure rate, and on-call load metrics. The integration is read-only — Koalr never writes to PagerDuty.
What Koalr pulls from PagerDuty
- Incidents with severity, status, and full timeline (triggered → acknowledged → resolved)
- On-call schedules and rotation assignments
- Escalation policy definitions and escalation event history
- Alert deduplication and grouping data
- Mean time to acknowledge (MTTA) per incident and per responder
- Responder workload: alerts per engineer per week, after-hours pages
How PagerDuty data feeds into Koalr
- MTTR (mean time to restore) calculation — the fourth DORA metric
- On-call load distribution — identifies responders carrying disproportionate alert volume
- Incident-deployment correlation — flags which deploys preceded incidents
- Burnout risk detection — sustained after-hours page volume per engineer
- Change failure rate calculation — incidents linked to recent deployments
How to connect PagerDuty
- 1
Go to Settings → Integrations in your Koalr dashboard.
- 2
Find PagerDuty in the integrations list and click Connect.
- 3
Generate a read-only API token in PagerDuty and paste it into Koalr. No OAuth flow required — the token is encrypted at rest.
- 4
Koalr begins syncing historical data immediately. Most integrations backfill 90 days of history on first connect.
Permissions and scopes requested
Koalr requests the minimum permissions required to read the data above. All access is read-only unless noted otherwise.
Read-only REST API access (incidents, schedules, escalation policies)No write access — Koalr never acknowledges, resolves, or modifies PagerDuty incidents
Ready to connect PagerDuty?
Connect in under 5 minutes. Koalr backfills 90 days of history automatically — no manual imports, no CSV uploads.