All integrations
Alert destination

PulseTrace + PagerDuty

Trigger and auto-resolve PagerDuty incidents.

PulseTrace triggers a PagerDuty incident when a monitor goes down and resolves the same incident when it recovers, using the Events API v2 with a stable deduplication key — so a flapping monitor never floods the on-call with duplicates.

Set it up in three steps

  1. 1In PagerDuty, add an Events API v2 integration to the service that should page and copy the integration (routing) key.
  2. 2In PulseTrace, add a destination of type PagerDuty and paste the key.
  3. 3Choose the destination on the monitors that should page. Recovery resolves the PagerDuty incident automatically.

Events it receives

  • Monitor down / recovered
  • Still-down reminders
  • Certificate expiring
  • Security grade downgraded / recovered
  • Performance anomaly opened / closed
  • Significant external change (DNS, TLS, HTTP fingerprint, content)
  • Incident opened / acknowledged / resolved
  • Auto-resolve — recovery closes the open alert instead of posting a second message.
PagerDuty event
{
  "routing_key": "••••••••",
  "event_action": "trigger",
  "dedup_key": "pulsetrace:monitor:8f3a…:down",
  "payload": {
    "summary": "Checkout API is DOWN (HTTP 503 from 2/3 regions)",
    "severity": "critical",
    "source": "pulsetrace",
    "custom_details": { "incident_url": "https://app.pulsetrace.app/dashboard/incidents/4821" }
  }
}

Questions about PagerDuty

Will recovery close the PagerDuty incident?
Yes. PulseTrace sends a resolve event with the same dedup key, so the PagerDuty incident closes itself when the monitor recovers.
Which severity is used?
Down events are critical; certificate expiry and security-grade downgrades are warning; anomalies are info unless you raise them in the monitor's alert rules.