PagerDuty alerts
Send Glowo alerts into PagerDuty's Events API v2 for real on-call rotations.
If you have an on-call rotation, PagerDuty should be your critical channel. Glowo detects the problem; PagerDuty decides who to wake, escalates when they do not answer, and tracks the response.
Configuration
| Field | Value |
|---|---|
routingKey |
An Events API v2 integration key |
Getting a routing key
Open the service
In PagerDuty, go to Services and pick the service Glowo alerts belong to — or create one.
Add an integration
Under Integrations, add one and choose Events API v2.
Copy the Integration Key
This is the routing key. It is a secret.
Paste it into Glowo
Create a PagerDuty channel with the key and press Test — a test incident should appear on the service.
How incidents behave
Glowo sends a trigger event when a monitor goes down and a resolve event
when it recovers, keyed to the monitor. PagerDuty therefore closes the incident
by itself on recovery — you do not need to resolve it manually.
For that to work, the channel must be subscribed to both MONITOR_DOWN
and MONITOR_UP. Subscribing only to MONITOR_DOWN leaves incidents open
forever, which is the single most common misconfiguration here.
Where escalation lives
Escalation policies, on-call schedules and rotations are configured in PagerDuty, not in Glowo. Glowo’s job is to detect and report; PagerDuty owns who gets woken and in what order.
Practical notes
- One channel per PagerDuty service. That keeps Glowo’s scoping aligned with PagerDuty’s routing.
- Send
MONITOR_DEGRADEDto Slack rather than PagerDuty unless degradation genuinely warrants waking someone.