Page your on-call team
Open a PagerDuty or Opsgenie alert when a monitor goes down or an incident opens, and resolve it when it’s over.
1 min readUpdated
On-call connections take the status page events that start or end something. Each alert is keyed to the monitor outage or incident it’s about, so the event that ends it resolves the same alert, and repeats don’t page twice.
| Event | What happens |
|---|---|
| Monitor down | Triggers an alert. |
| Monitor back up | Resolves the alert it matches. |
| Incident opened | Triggers an alert. |
| Incident resolved | Resolves the alert it matches. |
| In bynh | PagerDuty severity | Opsgenie priority |
|---|---|---|
| Monitor down | critical | P1 |
| Incident with a major outage | critical | P1 |
| Incident with a partial outage | error | P2 |
| Incident with degraded performance | warning | P3 |
Add a rule to page only for what matters, such as Monitor is any of Payments API, or Impact is any of Major outage. See Route events with rules.
PagerDuty
Step 1: Add an integration in PagerDuty
Open the service, then Integrations, and add the Events API v2 integration.
Step 2: Paste the key
In bynh, open PagerDuty in Settings › Integrations, paste the 32-character integration key, and pick the region your PagerDuty account is in: United States or Europe.
Step 3: Send a test
Choose Send a test to check the key before you save.
Opsgenie
Step 1: Add an API integration in Opsgenie
Open the team, then Integrations, add an API integration and copy its key.
Step 2: Paste the key
Paste it in bynh and pick your region: United States or Europe.
Step 3: Send a test
The test opens a P5 alert and closes it straight away.
To page one service for checkout and another for everything else, add two connections with different rules. Each tool can be connected up to 10 times.
Was this helpful?