PagerDuty Alerts
What the PagerDuty channel does
The PagerDuty channel turns monitor state changes into PagerDuty incidents through the Events API v2. A failing check triggers an incident so your on-call rotation is paged; when the check recovers, LoadFocus resolves the incident automatically. Degraded runs and upcoming SSL certificate expiry also send events. Events are correlated per check, so each check maps to its own incident instead of piling into one.
Get the integration key from PagerDuty
- In PagerDuty, open the service that should receive the incidents.
- Go to Integrations and add an Events API v2 integration.
- Copy the Integration Key (also called the routing key).
Add the channel in LoadFocus
- Go to the Alert Channels page.
- Click New Alert Channel and choose PagerDuty in the channel list.
- Give the channel a name and paste the key into Integration/Routing Key.
- Click Save Configuration.
Right after the channel is created, LoadFocus sends a one-time confirmation notification so you can verify delivery without waiting for a real failure. There is no separate test button.
Attach it to your checks
The channel is available to your whole team. Select it in a check's notification settings to page on that check's failures, see Alert Channels on a check. Combine it with retries and alert thresholds so a single network blip does not page anyone at 3am.
Troubleshooting
- No incident appears: confirm you copied an Events API v2 key from a service integration, not a REST API key from your account settings.
- Incidents are not auto-resolving: the resolve event uses the same per-check correlation; if you manually resolved or merged the incident in PagerDuty, the next failure opens a fresh one.
- Team members with a view-only role can see channels but cannot create or delete them.