Integration · On-call and incidents
Send server alerts to PagerDuty
Opservo triggers a PagerDuty incident through the Events API v2 when a server alert fires and resolves it when the alert clears. Setup takes one key.
In short
Opservo triggers a PagerDuty incident through the Events API v2 for each new server alert, with the summary, the server and a link back to Opservo, and resolves the same incident when the alert clears. A repeat of the same alert folds into the open incident instead of opening a new one. Setup takes the integration key of one PagerDuty service.
What you get
Your existing PagerDuty schedules and escalations page people for server problems.
- A triggered incident per new alert, with severity mapped to PagerDuty severity.
- A stable dedup key per alert, so a re-fire joins the open incident and the resolve closes exactly that one.
- An Open Opservo link on the incident for the plain-English explanation.
How to set it up
Create an Events API v2 integration in PagerDuty and paste its key into Opservo.
- In PagerDuty, open the service that should be paged → Integrations → Add an integration → Events API V2, and copy the Integration Key.
- In Opservo, open Account → Notifications, pick PagerDuty, paste the key, choose a minimum severity and click Add.
- Click Test to trigger a sample incident.
Good to know
- If you do not use PagerDuty, Opservo has its own on-call rotations and escalation on the Growth plan.
PagerDuty and Opservo, answered
Does Opservo integrate with PagerDuty?+
Yes. A PagerDuty channel uses the Events API v2: each new alert triggers an incident and the incident is resolved when the alert clears.
Will a flapping alert open many PagerDuty incidents?+
No. Each alert carries a stable dedup key, so a re-fire joins the open incident, and delivery is throttled to once per distinct problem per 24 hours.
Read next
Free for 2 servers, no card. Install the agent in about 30 seconds, then connect PagerDuty.