Skip to content

Observability & incidents

Connect a PagerDuty account with a read-only REST API key so Dave can see who is on call.

PagerDuty lets Dave see who is on call and what is paging. Read-only.

  1. Note your region: US (api.pagerduty.com) or EU (api.eu.pagerduty.com). EU accounts sign in at a .eu.pagerduty.com domain.

  2. In PagerDuty, go to Integrations → API Access Keys → Create New API Key, tick Read-only API Key, and copy the key. PagerDuty shows it once.

  3. In Dave, go to Integrations → Add integration → PagerDuty.

  4. Pick the Service region and paste the REST API key.

  5. Set a Label — the name you will use to refer to this account, e.g. prod.

  6. Choose Connect PagerDuty.

The key is stored encrypted and never shown again.

Dave needs a General Access REST API key with Read-only API Key ticked. PagerDuty keys have no finer scopes. Dave only sends read requests, so it never needs write access.

Creating the key needs an account Admin or the Account Owner.

Review or revoke the key in PagerDuty under Integrations → API Access Keys, on the domain you sign in at.

Disconnect in Dave stops Dave using the key, but the key stays active in PagerDuty until you revoke it there.

To rotate the key, Disconnect, then add the connection again with the same label and the new key. Connect again only re-checks the key Dave already has.

  • PagerDuty rejected the credentials. Check the region first: an EU key will not authenticate against the US region, and the error looks like a bad key. Then check the key is still active.
  • Validation takes long. Dave keeps retrying while PagerDuty is unreachable. Confirm the key is still active and belongs to the selected region.