Alert Costs allows you to review triggered alerts and the human cost these have on your team. With Alert Costs you can find out which alerts are keeping your on call team awake at night and distracting them throughout the day so that you can find patterns and trends to prevent your team from burning out and suffering alert fatigue.
This is part of our ongoing HumanOps philosophy to make operations more human.
Cost & Cost Calculation
The human cost of the alert events. This is calculated as
the total amount of time the events are open + (number of times the alert is triggered * 23 minutes)
We've calculated this so that you can understand the human impact of the triggered alerts from your infrastructure and which events have the most effect on your team.
Why 23 minutes? Because each time an alert opens it costs you an additional 23 minutes of lost productivity due to a context switch or sleep loss (our source).
Best practice dictates you should prioritise fixing the underlying issue causing the alerts that have the highest cost.
The time of the alert triggered. When multiple alerts are aggregated together this is the last event in the aggregate.
The sum of all event durations. Data is aggregated by the alert configId and the itemId (either the device or service ID).
The peak value seen during the event, for multiple events this is the peak value seen for the last event. Peak values are only available on alerts where <, >, <= or >= comparisons are used.
For < and <= alerts the lowest value is the peak. For > and >= alerts the highest value is the peak.
The events column indicates the amount of alerts that were triggered in your selected time frame.