PagerDuty Integration

The PagerDuty integration triggers incident assembly when a PagerDuty alert fires. Incidentary assembles the causal artifact from the events your services have already captured and posts the shared incident URL back to the PagerDuty incident.

How it works

1. An alert fires in PagerDuty
2. PagerDuty sends a webhook to Incidentary via the V3 events API
3. Incidentary identifies the alerting service, assembles the causal chain from the pre-alert capture window, and creates an incident
4. The shared incident URL is posted to the PagerDuty incident

The artifact is ready before the first responder opens the PagerDuty incident page — it assembles from already-captured data.

Setup

Step 1: Get your Incidentary webhook URL

In the Incidentary dashboard, go to Settings → Integrations → PagerDuty. Copy the webhook URL shown there.

Step 2: Create a PagerDuty webhook subscription

1. In PagerDuty, go to Integrations → Generic Webhooks (V3)
2. Click New Webhook
3. Webhook URL: paste the Incidentary webhook URL from Step 1
4. Scope Type: select Service (to receive alerts for a specific service) or Account (for all services)
5. Event Subscription: select incident.triggered
6. Click Add Webhook

Step 3: Map your PagerDuty services to Incidentary service names

For Incidentary to assemble the correct trace, the alerting PagerDuty service must match the serviceName configured in your SDK. In Settings → Integrations → PagerDuty, configure the mapping between PagerDuty service names and Incidentary service IDs.

Step 4: Test the integration

Trigger a test incident in PagerDuty for a service that has the Incidentary SDK installed. Within a few seconds, a shared incident URL should appear in the PagerDuty incident timeline.

What Incidentary receives from PagerDuty

Incidentary reads the alerting service name from the PagerDuty webhook payload. It uses this to identify which service triggered the alert and assembles the causal chain starting from that service's most recent trace.

No PagerDuty API credentials are stored in Incidentary. The integration is inbound-only: PagerDuty sends webhooks to Incidentary.