PagerDuty integration
Page the on-call engineer only for confirmed outages
MoniterMySite's PagerDuty integration turns a confirmed outage into a PagerDuty incident through the Events API v2, with the monitor name as the summary and the regions and error as details. When the monitor recovers, the same incident is resolved automatically, so nobody has to close it by hand. It is included on the Growth plan and above.
- Events API v2: one integration key per PagerDuty service, no REST API access needed
- Auto-resolve on recovery, so incidents close themselves
- Included on Growth ($29/mo) and Summit
Set it up in four steps
Add an Events API v2 integration
In PagerDuty, open the service that should receive alerts → Integrations → Add integration → Events API v2, and copy the 32-character Integration Key.
Create a PagerDuty contact
In MoniterMySite, Alert contacts → Add contact → PagerDuty. Paste the key and name the contact, for example “On-call (production)”.
Send a test event
Press the paper-plane icon on the contact. A test event should appear in PagerDuty within seconds; if it does not, check that you pasted an Events API key rather than a REST API key.
Attach it to critical monitors
Add the contact to the monitors that justify a page. Keep everything else on Slack or email so PagerDuty stays quiet unless customers are affected.
What you get
Confirmed before it pages
A region must fail your consecutive-check threshold and the number of regions you require must agree before an incident opens and PagerDuty is triggered.
Automatic resolve
Recovery is declared only when every selected region is healthy again, and the PagerDuty incident resolves at that moment with the downtime recorded.
Context in the incident
The summary is the monitor name; the details carry the regions that saw the failure and the exact error, so the responder starts with evidence.
Down-only mode
Suppress recovery events on the PagerDuty contact if your escalation policy should only ever page on new incidents.
Maintenance windows
Planned work silences PagerDuty along with every other channel and is excluded from uptime figures.
Delivery log
Every event sent to PagerDuty is recorded per contact and per incident, so you can prove when the page went out.
Events API v2, not a REST key
PagerDuty offers two kinds of credentials. An Events API v2 integration key belongs to one service and can only create, acknowledge and resolve events for it; that is what MoniterMySite uses, and it is the safest option because it cannot read or change anything else in your account. A REST API key grants broad account access and will not work in the PagerDuty contact.
Designing an escalation that stays quiet
Most noisy on-call rotations come from monitors that page on a single failed check from one location. On MoniterMySite, set the fail threshold to 2 or more consecutive failures and require at least two regions to agree before an incident opens. Route only customer-facing monitors (the homepage, login, checkout or API health endpoint) to PagerDuty and send the rest to Slack.
Plans and limits
PagerDuty is available on Growth and Summit.
| Plan | Price per month | PagerDuty | Regions per monitor |
|---|---|---|---|
| Starter | Free | No | 1 |
| Launch | $9 | No | Up to 3 |
| Growth | $29 | Yes | All |
| Summit | $79 | Yes | All |
Using webhooks for other on-call tools
If your team uses Opsgenie, Grafana OnCall or a home-grown pager, the signed webhook contact delivers the same events as JSON with an HMAC-SHA256 signature, retried three times if your endpoint does not answer within 10 seconds. The payload format is documented on the webhooks page.
Frequently asked questions
Does the PagerDuty incident close itself?
Yes. When the monitor recovers, MoniterMySite sends a resolve event for the same incident key, and PagerDuty closes the incident automatically.
Which PagerDuty key do I need?
An Events API v2 integration key from the service that should receive alerts. REST API keys are not accepted.
Can I test it without causing an outage?
Yes. The paper-plane icon on the contact sends a test event that appears in PagerDuty and is labelled as a test.
What happens during maintenance windows?
Alerts to every channel, including PagerDuty, are suppressed for the window, and the downtime is excluded from uptime statistics.
Is PagerDuty available on the free or Launch plan?
No. PagerDuty starts on the Growth plan. Launch includes Slack, Discord, Teams, Google Chat and Telegram; Starter includes email and webhooks.
Keep reading
Start monitoring in 30 seconds.
Nothing to install. No credit card. 10 monitors free, forever.