Opsgenie
Leak events are turned into Opsgenie alerts and the right person is paged according to the on-call schedule.
How it works
The connection uses the key of a team API integration. The account’s region is selected during setup.
Every alert carries a deduplication key specific to the event. The key is derived from the company, the connection and the event together; two customers’ alerts never mix.
Only leak alerts go out. Scan summaries and scan failures do not wake the rotation.
Atlassian is retiring Opsgenie; its alerting and on-call features moved into Jira Service Management. New setups use the JSM alert integration.
Severity mapping
| Dark Radar | Opsgenie |
|---|---|
| Critical | P1 |
| High | P2 |
| Medium | P3 |
| Low | P4 |
| Info | P5 |
Limits
Only alerts are created. The on-call schedule, users and existing alerts are not read.
The leaked value itself is not in the alert.
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.