Connect to PagerDuty¶

Noctuary enriches PagerDuty incidents with pre-built context before your engineer opens them.

How it works¶

PagerDuty fires alert
    │
    │  webhook (PagerDuty → Noctuary)
    ▼
Noctuary correlates alert with recent ContextEvents
    │
    │  LLM generates hypothesis + recommended action
    ▼
Noctuary posts note back to PagerDuty incident
    │
    ▼
Engineer opens incident — context is already there

Setup¶

1. Create a PagerDuty integration in Noctuary¶

In the dashboard, go to Settings → Integrations and click Add integration.

Type: PagerDuty
Direction: bidirectional

Copy the Webhook URL shown after creation. It looks like:

https://api.noctuary.io/webhooks/pagerduty/tok_abc123...

2. Add the webhook to PagerDuty¶

In PagerDuty, go to Integrations → Generic Webhooks (V3) and add a new webhook:

Field	Value
Name	Noctuary context
Webhook URL	Your webhook URL from step 1
Events	`incident.triggered`, `incident.acknowledged`

3. Provide your PagerDuty API token (outbound)¶

Noctuary posts enrichment notes back to PagerDuty incidents. To enable this:

In PagerDuty, create a Read/Write API token under Integrations → API Access Keys
In the Noctuary dashboard, go to Settings → Integrations and edit your PagerDuty integration
Set pagerduty_token in the config to your token

4. Test the connection¶

Trigger a test incident in PagerDuty. Within 10–15 seconds, Noctuary should post a note to the incident with a context summary. If no ContextEvents have been received for that service yet, the note will indicate that context is not yet available.

What engineers see¶

When an incident fires, Noctuary adds a note like:

Noctuary Context

Hypothesis: Deploy sha=a4f2c1 rolled out 4 minutes before onset (confidence: 94%)

Recent signals: deploy (argocd, 02:10:41), deadlock (postgres, 02:14:33), OOMKill (kubernetes, 02:14:41)

Recommended action: Rollback to sha=f8b3e22

Tip

No context is wasted. If Noctuary has no relevant events for the service, it says so explicitly — engineers know immediately that the cause is likely external rather than a recent change.