PagerDuty

Updated 11 October 2026 · BugsRadar team

Alerts open incidents on a PagerDuty service through its Events API v2 integration. You provide the integration key. PagerDuty comes with the Business plan.

Steps

1. In PagerDuty, open Services and the service that should get the incidents; its escalation policy decides who is paged.
2. Open the Integrations tab and press Add integration.
3. Choose Events API V2 and add it.
4. Copy the Integration Key: 32 letters and digits. Keep it secret: whoever has it can open incidents on the service.
5. In BugsRadar, add a PagerDuty channel and paste the key.

Test it

BugsRadar checks the key's format before saving. Press Send test: a test alert is triggered and resolved at once, so it appears in the service's activity without paging anyone. A key PagerDuty refuses turns the channel off with the reason.

How incidents behave

• The first occurrence of an error triggers an alert: the summary is the project, the level and the exception's message, the source is the host, the severity follows the level (Critical, Error, Warning; everything else is info), and the custom details carry where it happened, the environment, version and time, the properties and the stack trace.
• Repeats of the same error carry the same deduplication key and join the open incident; the counts of repeats go there too, at the moments described in What you receive.
• You resolve the incident in PagerDuty. An error that comes back after a quiet window opens a new one.
• To page only on Critical errors, put a rule with the level Critical on the PagerDuty channel of the project.

Changing the service

Credentials can't be edited: to open incidents on another service, add an Events API v2 integration there, add a new PagerDuty channel in BugsRadar with that key and delete the old one. If the integration is deleted or the key is refused, BugsRadar turns the channel off and shows the reason: see When a channel fails.