Incident Management (PagerDuty, Opsgenie, GoAlert)
On-call incidents for DORA recovery metrics in SDLC Insights.
What you get
Connecting an incident-management tool feeds Time to Restore Service (MTTR) and helps Change Failure Rate (CFR) in SDLC Insights → DORA Metrics. Data syncs on the productivity ingest schedule after you connect (not instantly).
Supported today:
| Tool | Auth | Notes |
|---|---|---|
| PagerDuty | API token | Optional custom API base URL |
| Opsgenie | GenieKey API token | Optional custom API base URL |
| GoAlert | API token + instance URL | Self-hosted GoAlert base URL is required |
Before you connect
- You need a workspace admin (or equivalent) role to add integrations.
- Create a read-only or alerts-list API credential in your incident tool. We store the token encrypted on the workspace.
- For GoAlert, use your instance root URL (for example
https://goalert.example.com).
Setup
- In the platform: Settings → Integrations → Monitoring & Observability.
- Choose PagerDuty, Opsgenie, or GoAlert → Connect.
- Paste the API key (and GoAlert instance URL for GoAlert).
- Test connection, then Connect.
After the next productivity ingest run, open Insights → SDLC Insights → DORA Metrics to confirm MTTR and related cards populate.
When something’s wrong
Test fails: Confirm the token is valid and not revoked. For GoAlert, check the instance URL (no trailing path) and that the token can call /api/v2/alerts.
Metrics still locked: GitHub (deployments) is still required for deployment-frequency and lead-time cards. MTTR needs a connected incident tool plus ingest data in range.
Rotating a key: Disconnect or update the source under Settings → Integrations, test, and save. Historical metrics already stored are not removed.