PagerDuty
Connect PagerDuty so triggered incidents are investigated as they open and the root cause is added to the incident as a note.
Triggered incidents (high urgency by default) are investigated as they open, and the root cause is added to the incident as a note.
Why connect PagerDuty
Section titled “Why connect PagerDuty”When the pager goes off, the first minutes go into figuring out what’s wrong. With PagerDuty connected, TraceX starts investigating the moment the incident triggers, so by the time the on-call engineer has opened their laptop, the incident already has a note with the likely cause and the change that lines up with it.
Connect
Section titled “Connect”-
Open Integrations → PagerDuty and fill in:
Field Value REST API key Integrations → API access keys (read/write) PagerDuty user email for notes [email protected]Investigate High-urgency incidents · All incidents Service region United States · Europe Keys are checked with a real read, then encrypted and never shown again.
-
TraceX shows a webhook address. Copy it and finish in PagerDuty:
- Integrations → Generic Webhooks (v3) → New webhook: paste the address.
- Scope it to the services TraceX should watch and subscribe to
incident.triggered. - The next triggered incident is investigated and gets a note with the root cause.
TraceX only reads the items it is sent and adds internal notes. It never replies to customers on its own.
Troubleshooting
Section titled “Troubleshooting”| Problem | What to check |
|---|---|
| Incidents aren’t investigated | Check the webhook is scoped to the right services and subscribed to incident.triggered, and the urgency setting matches. |
| Notes fail to post | The user email must be a PagerDuty user; the key needs write access to add notes. |
Remove access
Section titled “Remove access”Disconnect PagerDuty in Integrations, delete the webhook and revoke the API key.