Guide

How to set up PagerDuty uptime monitoring

PagerDuty handles on-call routing and escalation. Larm handles the monitoring. Wire them together and your on-call engineer gets paged only when multiple probe locations confirm a real outage — not when a single check times out.

STEP 1

Get your PagerDuty integration key

In PagerDuty, go to your service and add an integration. Choose "Events API v2" and copy the 32-character integration key. This key tells PagerDuty which service the alerts belong to and which escalation policy to follow.

STEP 2

Add PagerDuty as an alert channel in Larm

In Larm, go to Alert Channels and create a new PagerDuty channel. Paste the integration key. Give it a name that matches your PagerDuty service ("Production API - PagerDuty").

STEP 3

Attach to your monitors

Link the PagerDuty channel to the monitors that should page your on-call team. When Larm confirms a service is down — verified by multi-probe voting across multiple continents — it triggers a PagerDuty incident. When the service recovers, Larm automatically resolves the incident using a stable dedup key. No manual cleanup needed.

Why pair PagerDuty with Larm?

PagerDuty is great at routing alerts to the right person at the right time. What it doesn't do is verify that the alert is real. If your monitoring tool triggers on a single failed check from a single location, PagerDuty faithfully wakes someone up for nothing.

Larm's multi-probe voting ensures that an alert only fires when a majority of probe locations across multiple continents agree something is actually wrong. By the time PagerDuty pages your on-call engineer, the problem has been independently verified. That's the difference between a team that trusts their alerts and a team that sleeps through them.

Pages your on-call engineer can trust.

Multi-probe voting. Automatic PagerDuty incident creation and resolution. Free to start.