Skip to content
Go to dashboard

10.7PagerDuty

A PagerDuty channel opens a PagerDuty incident when a monitor goes down, so whoever is on call gets paged. You need an integration key: a code PagerDuty gives you for one of your services.

  1. In PagerDuty, open the service that should be paged. Go to Integrations and add an Events API V2 integration.
  2. Copy the integration key. It is 32 letters and digits.
  3. In obsrvly, in New alert channel, choose PagerDuty.
  4. Enter a Name and paste the key into Integration key.
  5. If your PagerDuty account is hosted in the EU, tick My PagerDuty account is hosted in the EU.
  6. Select Create channel, then send a test alert (10.9).

If the key is not 32 letters and digits, the dashboard shows "An integration key is 32 letters and digits". The API returns invalid input: pagerduty_routing_key must be the 32-character integration key of an Events API v2 integration.

What happens in PagerDuty#

The dashboard says: "Each outage opens one PagerDuty incident. Acknowledging it here acknowledges it there, and the recovery resolves it."

  • Down: one incident opens, with severity critical.
  • Degraded: one incident opens, with severity warning.
  • Reminders go to the same incident. They do not open a new one.
  • Acknowledge in obsrvly (9.6), and the PagerDuty incident is acknowledged too.
  • Recovery: when the monitor passes again, the PagerDuty incident is resolved.
  • Alerts to a PagerDuty channel are never grouped. Each outage is its own incident (9.8).

In the channels list, a PagerDuty channel shows the last 4 characters of its key, such as key …a1b2, and EU when the EU box is ticked.

API: CreatePagerDutyChannel with name, pagerdutyRoutingKey and, for an EU account, pagerdutyEu: true. pagerdutyRoutingKey always comes back empty, to the dashboard and to an API key; credentialHints gives its last characters (10.1).

Last updated