PagerDuty alerts for website monitoring
Quick answer
Can Lemwatch send website monitoring that pages on-call through PagerDuty?
Lemwatch raises PagerDuty incidents through the Events API v2 and resolves them automatically when the site recovers, so on-call rotation, escalation and acknowledgement all stay in PagerDuty.
How to set it up
What you need: An Events API v2 integration key from the PagerDuty service.
- In PagerDuty, open the service that should receive the alerts and add an Events API v2 integration.
- Copy the integration key.
- Paste the key into the PagerDuty field in Lemwatch notification settings.
- Trigger a test so the on-call person sees the alert format before a real outage.
What the alert contains
A failure triggers an incident against your service with the site, the failure reason and a link back to Lemwatch. When the site recovers, Lemwatch sends the resolve event so nobody has to close it by hand.
What Lemwatch watches
Every alert that reaches PagerDuty comes from the same checks: uptime and response time, SSL and domain expiry, DNS changes, broken links, visual and content changes, Core Web Vitals and SEO regressions. You choose which of them are worth interrupting the channel for.
free for 10 sites — enough to wire the channel up and see real alerts before you decide on a paid plan.
Create a free accountOther channels
You can run several at once — chat for the team, on-call paging for the serious ones, a webhook for everything else.
PagerDuty alerts — common questions
Send your first PagerDuty alert today
Free forever for up to 10 sites. No credit card required.