PagerDuty website monitoring
When a monitor finds a problem — a broken checkout, a failing login, a site that's down — Relvato opens an incident on your PagerDuty service, and your escalation policies decide who gets paged. When the monitor passes again, Relvato resolves the incident.
PagerDuty alerts are on the Business ($79 a month) and Agency plans. The button takes you to Alert settings, where you paste your service's Integration Key.
Checkout broke on My Shop
- Severity
- critical
- Source
- store.example.com
- Component
- Guest checkout
- Group
- User flows
View the run in Relvato
- 2:14 AMTriggeredGuest checkout failed — via Events API v2
- 2:41 AMResolvedMonitor passed again — via Events API v2
Connected in a few minutes
Nothing to install in PagerDuty: an Events API v2 integration on one service is enough.
Add an integration in PagerDuty
Open Services, pick the service that should get the incidents, then Integrations → Add an integration → Events API v2. Copy its Integration Key: 32 letters and digits.
Paste it into Relvato
Open Alert settings and find the PagerDuty card. Choose the service region — US, or EU if your PagerDuty address ends in .eu.pagerduty.com — give it a name, paste the key and click Add PagerDuty.
Send a test
Click Send test. Relvato opens a test incident and resolves it straight away; PagerDuty may still notify whoever is on call. From then on, a failing monitor opens an incident on that service.
Who gets paged, when and how is up to the service's escalation policy in PagerDuty. Relvato opens the incident and resolves it; it never pages anyone directly.
It can open and resolve incidents on one service. That's all.
An Integration Key belongs to one PagerDuty service, and events sent with it go only to that service. Relvato calls PagerDuty's own Events API and nothing else.
What Relvato can do
- Open an incident on the service the key belongs to when a monitor starts failing
- Resolve that incident when the monitor passes again
- Include the site, the monitor and its group, the severity, the error, the failed step, what triggered the run and a link to the run
- Stop at once when you switch it off or remove it in Alert settings
What it can't
- Read incidents, on that service or any other
- See your schedules, users or other services
- Choose who gets paged — your escalation policy does that
- Show you the key again — it's stored encrypted
One incident per monitor, resolved when it passes again
One incident per monitor
Each monitor on each site gets its own incident. A repeat failure adds to the open incident instead of paging again, and the recovery resolves exactly that one.
Uptime, heartbeats and ports too
Down opens an incident, back up resolves it. A short outage that's already over arrives as an incident that's already resolved. Quarantine mode's unexpected changes open one, and the end of the 48 hours resolves it.
Your switches and threshold
Under What goes where, the PagerDuty column has a switch per monitor type, from Uptime to Legal compliance. Muted sites stay quiet, and the “Alert me on” level applies.
It tells you when PagerDuty stops answering
After 20 failed deliveries in a row — say, someone removed the integration — Relvato pauses that PagerDuty service and says so in the notification bell. One click resumes it.
PagerDuty alerts, answered
Which plans include PagerDuty alerts?
Business ($79 a month) and Agency. Pro includes email, Slack, Teams, Discord, Google Chat, Telegram and webhook alerts, but not PagerDuty. On Free, alerts show in the app and by email once a month.
Will a monitor that keeps failing page us again and again?
No. Relvato keeps one incident per monitor per site, so a repeat failure adds to the incident that's already open. When the monitor passes again, Relvato resolves it.
What's in the incident?
The summary is the alert headline, such as “Checkout broke on My Shop”, or “Checkout couldn't run on My Shop — Cloudflare blocked Relvato” when a monitor couldn't run. The source is the site's address, the component is the monitor and the group is its monitor group: User flows, Security, Design, Performance, SEO / AEO, Domain lifecycle, Legal compliance or Uptime. Custom details carry the site, the monitor, the error, the failed step and what triggered the run, and the incident links to the run: View the run in Relvato.
How do Relvato's severities map to PagerDuty's?
Critical stays critical, high becomes error, medium and low become warning, and warning becomes info.
Does it work with PagerDuty's EU service region?
Yes. Choose EU when you add the service if your PagerDuty address ends in .eu.pagerduty.com, and US otherwise. Relvato then sends to that region's Events API.
Can I send alerts to more than one PagerDuty service?
Yes. Add an Events API v2 integration on each service and add each key in Alert settings — up to 10 chat apps and PagerDuty services per account, together. Each one has its own on/off switch.
How is the key kept safe?
Anyone with the key can open incidents on that service, so Relvato treats it like a password: it's stored encrypted and never shown again. Relvato only calls PagerDuty's own Events API, and the key can't read incidents, schedules, users or other services.
Send alerts where your team already works
Put your site's failures in front of whoever is on call
Add PagerDuty in Alert settings and send a test. If a checkout breaks at 3 a.m., your escalation policy takes it from there, and Relvato resolves the incident when the monitor passes again.