PagerDuty Integration
Ingest incidents for MTTR and DORA recovery metrics.
Why connect PagerDuty
PagerDuty is a Monitoring & Observability source. After you connect, the platform reads your account’s incidents on a schedule and uses them for Quality (incident rates, MTTR) and DORA (change failure rate, time to restore service) views.
The integration is read-only. We never change incidents, services, escalation policies, or on-call schedules in PagerDuty.
What you need
- A PagerDuty account with incidents you want reflected in Quality/DORA metrics.
- A REST API v2 token (“API Access Key” — not a webhook secret or events integration key).
- Optionally, a custom API base URL if PagerDuty support gave you a dedicated endpoint (most
accounts leave this blank and use the default
https://api.pagerduty.com).
Select PagerDuty in your tech stack under Monitoring & Observability if you use it today.
Setup
- In PagerDuty, go to Integrations → API Access Keys and create a new REST API v2 key with read access.
- In the platform, go to Settings → Integrations (or onboarding Integrations) and choose Connect on PagerDuty.
- Enter the API token. Leave API base URL blank unless told otherwise.
- Click Test connection. A successful test shows the PagerDuty user name and email associated with the token.
- Click Connect (or Save changes) to store encrypted credentials.
Incidents sync on the platform’s batch schedule after the first successful save.
Data we read
| PagerDuty data | Platform use |
|---|---|
| Incidents (declared, acknowledged, resolved) | Quality metrics, MTTR, escaped-incident signals; SDLC Engineering Health “Time to Restore Service” and “Change Failure Rate” |
We fetch roughly the last 30 days of incidents on each sync (scheduled daily).
Verification status: this integration is newly productized. Some account-identity and 30-day summary fields shown in the connect dialog are labeled placeholder until a live-token verification pass in staging confirms exact response shapes from the PagerDuty API.
Data we do not read or change
The integration is read-only. We never create, update, or delete anything in your PagerDuty account.
| Not accessed | Notes |
|---|---|
| Escalation policies or on-call schedules | Not read or modified |
| Services, teams, or notification rules | Not exported |
| Webhooks or event orchestration rules | Not modified |
| Status pages | Not accessed |
| Events API v2 integration keys | Connect uses a REST API v2 token only |
Repository Readiness observability scans (dimension E) remain repo-based; connecting PagerDuty improves live Quality/DORA metrics, not automatic readiness score bumps.
Sync schedule
After connect, the platform syncs on a daily batch schedule alongside other monitoring sources. There is no dedicated Sync now button for PagerDuty yet — the next scheduled batch run picks up new credentials automatically.
SDLC Engineering Health (Insights)
Under Insights → Engineering Health, the platform reads the same weekly dashboard metrics PagerDuty sync writes. You do not connect PagerDuty twice.
| SDLC metric (when available) | Powered by PagerDuty when |
|---|---|
| Time to Restore Service (MTTR) | Incidents were declared and resolved in the selected period |
| Change Failure Rate | Incidents correlate with deployments in the bucket |
If a tile shows unavailable, confirm PagerDuty has incidents in the last ~30 days and wait for the next scheduled sync.
Other live monitoring connectors that feed the same Insights buckets:
- New Relic (alert issues + deployment markers → MTTR and deployment frequency)
- Prometheus (Alertmanager alerts → MTTR)
- Grafana (Unified Alerting + deploy annotations → MTTR and deployment frequency)
Disconnect
Remove PagerDuty under Integrations → Disconnect. Polling stops; previously ingested events remain in historical metrics until retention policies apply.