PagerDuty alerts
PagerDuty is the channel for serious on-call. Instead of a single message, PingArk opens an incident when a check goes down and resolves the same incident when it recovers, so PagerDuty can handle phone calls, escalation, and repeat until someone acknowledges.
Prerequisites
A PagerDuty account and a service you can add an integration to.
Setup
- In PagerDuty, go to Services, then Service Directory, and open or create the service you want alerts on.
- Open the Integrations tab and click Add another integration.
- Search for and select Events API V2, then click Add.
- Copy the Integration Key, which PagerDuty also calls the routing key.
- In PingArk, open Channels, click Add channel, pick PagerDuty, and paste it into the Integration (routing) key field.
Config fields
| Field | What to enter |
|---|---|
| Integration (routing) key | The Events API v2 integration key from your PagerDuty service, a 32-character string. |
Click Send test in the add-channel modal to fire a test incident and confirm the routing key works before you save.
How incidents map
A down triggers a critical incident, and the matching recovery resolves that exact incident rather than opening a new one, because PingArk uses a stable dedup key per check. The result is a clean timeline: one incident per outage, opened and closed by PingArk.
Troubleshooting
If incidents do not open, confirm you copied the Events API v2 integration key, not an older Events API v1 key or a REST API token. Leave the escalation policy, schedules, and acknowledgement rules to PagerDuty. PingArk's job is to open and close the incident accurately. Opsgenie support is on the roadmap.
Which plans include which channels is on the pricing page.