Page Disruptions
Last updated
Was this helpful?
Last updated
Was this helpful?
What it is: The number of pages over time. You can see Out-of-hours pages (the ones outside of the responder’s preferred working hours*, which can contribute to burnout), or All pages (includes pages during work hours, whch are still disruptive to a team's focus).
*By default, this is set to 8am-6pm weekdays, local time. Given that more and more people are working flexible hours, our metric is configurable for different timezones and different preferred working hours and days on each team member's profile in Settings.
You will need to integrate with PagerDuty to get this metric.
🌱 Coming soon to our OpsGenie integration
Why it matters: Being woken up in the middle of the night is never fun. Continued disruptions to sleep impact people's productivity, wellbeing, and satisfaction in their workplace. What's more, lots of pages disrupting a team (no matter the hour) can interrupt delivery.
How we calculate it: We use the time of acknowledgement as a proxy for when the page was sent out (when the responder was disturbed). We count the number of acknowledgements on incidents, using the time that each incident.acknowledged event occurs*. We then compare this time to the responder's preferred working hours, and figure out if it was an out-of-hours page.
If multiple people acknowledged the incident on PagerDuty, the chart will count all acknowledgements. For example, if Person A acknowledges an incident, then reassigns to Person B who also acknowledges it, both Person A and Person B (and their respective teams) will have +1 to their Page Disruptions on this chart.
*If an incident was resolved without getting acknowledged, we count the incident.resolved event as the acknowledgement for that incident.
This metric is not available on historical data, because we don't have access to the incident's history of events.
Incidents with the keyword [test] in the title (case insensitive) will not be processed.
What good looks like
Generally, the less pages means the more reliable your tech stack, and the less disruptions to workflow. If the number rises above 1-2, especially for out-of-hours pages, it’s important to ensure that it doesn’t become a trend so that people aren't doing sustained days of long hours and interrupted sleep. Multiple weeks of someone being paged out-of-hours might indicate some QA process changes or reliability work is needed.
