PagerDuty
TraceStax integrates with PagerDuty using the Events API v2. When a TraceStax alert fires, it opens a PagerDuty incident and pages your on-call rotation. When the alert resolves, the incident is automatically resolved in PagerDuty.
How it works
Section titled “How it works”TraceStax alert fires → Events API v2 → PagerDuty incident → your on-call scheduleTraceStax alert resolves → Events API v2 → PagerDuty incident auto-resolved-
Create a service integration in PagerDuty
In PagerDuty, go to Services → select or create a service → Integrations tab → Add an integration.
Search for Events API v2 and add it.
-
Copy the Integration Key
After adding the integration, PagerDuty shows a 32-character Integration Key (also called a routing key). Copy it.
It looks like:
a1b2c3d4e5f678901234567890abcdef -
Add the key in TraceStax
In the TraceStax dashboard, go to your project → Integrations → PagerDuty → paste the Integration Key → Save.
What triggers a PagerDuty incident
Section titled “What triggers a PagerDuty incident”Any alert policy that fires creates a PagerDuty incident with:
- Summary — the alert title (e.g. “Worker failure rate exceeded 5%”)
- Severity — mapped from the TraceStax alert severity (
critical→critical,warning→warning,info→info) - Source — the project name
- Dedup key — the alert ID, so repeat fires don’t open duplicate incidents
When the alert condition clears, TraceStax sends a resolve event and PagerDuty closes the incident automatically.
Troubleshooting
Section titled “Troubleshooting”Incidents not appearing in PagerDuty
- Verify the Integration Key is 32 characters with no spaces.
- Check that the PagerDuty service is not in maintenance mode.
- Confirm the alert policy has PagerDuty selected as a notification channel.
Duplicate incidents
- This shouldn’t happen due to dedup keys, but if it does, check that you haven’t added the same Integration Key under multiple projects.