Skip to main content
Connecting PagerDuty lets Traversal pull incident details, on-call coverage, and escalation history into an investigation: who’s on call right now, what’s currently firing, and how an incident has escalated so far.

​
What Traversal reads

  • Incidents: status, urgency, service, escalation policy, and assignees, filterable by service, status, and time window
  • Alerts and log entries: the full alert and notification/escalation timeline for a specific incident
  • On-calls: who’s on call, for a given escalation policy or schedule, at any point in time (past, current, or future)
  • Schedules and escalation policies: rotation and escalation-chain configuration
  • Services, teams, users, and maintenance windows
This is a read-only integration. Traversal never acknowledges, resolves, escalates, or creates anything in PagerDuty.

​
Setup

1

Create an API key

  1. In PagerDuty, go to Integrations → API Access Keys.
  2. Click Create New API Key and name it (for example, “traversal-prod”).
  3. Set the access level to Read-only. Traversal only reads from PagerDuty, so enforcing that on PagerDuty’s side also limits what a leaked key could do.
  4. Copy the generated key. PagerDuty shows it only once.
2

Configure in Traversal

Go to Integrations, select PagerDuty, and paste the API key.
This integration only requires a PagerDuty API key. You don’t need to enter a base URL or any other authentication fields.PagerDuty’s account-level API keys aren’t tied to a single user, so Traversal can see any user or service that the key can see. You can’t scope a single key to specific teams or services.

​
More information