Skip to content
TraceStax Docs

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.

TraceStax alert fires → Events API v2 → PagerDuty incident → your on-call schedule
TraceStax alert resolves → Events API v2 → PagerDuty incident auto-resolved

  1. 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.

  2. 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

  3. Add the key in TraceStax

    In the TraceStax dashboard, go to your project → IntegrationsPagerDuty → paste the Integration Key → Save.


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 (criticalcritical, warningwarning, infoinfo)
  • 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.


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.