PagerDuty
Leak events are turned into PagerDuty incidents and the on-call team is alerted.
How it works
The connection uses an Events API v2 integration key. The key only sends events to that service; it cannot read the account.
If the same leak is seen again, no new incident is opened and the existing one is updated. When the event is closed it is resolved on the PagerDuty side too.
PagerDuty’s acknowledgement does not mean the on-call person was reached. Whether the notification goes out depends on your escalation policy and notification preferences.
Severity mapping
| Dark Radar | PagerDuty |
|---|---|
| Critical | critical |
| High | error |
| Medium | warning |
| Low | info |
Limits
Escalation policies, users and account settings are not read.
There is no region or custom address option; delivery goes to PagerDuty’s official events address.
The leaked value itself is not in the incident.
Setup
The setup steps are in the panel, on the integration’s own screen. What to do on the provider side and which value goes where is written there.