Use when performing alert fatigue reduction — analyzes alerting configurations to identify noise, redundancy, and low-value alerts that contribute to on-call fatigue. This template walks teams through auditing their alert rules, measuring signal-to-noise ratios, and implementing changes to ensure every page is actionable and meaningful.
Gather alert data for the analysis window.
Classify every alert rule that fired during the window.
| Alert Rule | Fires (count) | Actionable (%) | Avg Resolution Time | Auto-resolved (%) | Category |
|---|
Categories:
| Category | Definition |
|---|---|
| Actionable | Required human intervention that prevented or mitigated user impact |
| Informational | Provided useful context but required no action |
| Noisy | Fired frequently without requiring action; contributes to fatigue |
| Redundant | Duplicates another alert for the same condition |
| Stale | Monitors a condition that is no longer relevant |
| Misconfigured | Threshold too sensitive or monitoring wrong metric |
actionable_alerts / total_alerts * 100Decision Matrix — Alert Disposition:
| Category | Action |
|---|---|
| Actionable | Keep. Review thresholds for optimization. |
| Informational | Convert to dashboard or log-based notification. Remove paging. |
| Noisy | Adjust thresholds, add dampening, or consolidate with related alerts. |
| Redundant | Delete or merge into parent alert. |
| Stale | Delete after confirming with service owner. |
| Misconfigured | Fix threshold, metric, or query. Revalidate. |
For each alert requiring changes:
| Shortcut | Counter | Why |
|---|---|---|
| "We can skip some steps for this case" | Adapt the workflow steps, don't skip them | Skipped steps are where incidents and oversights originate |
| "The user seems to already know what to do" | Complete all workflow phases with the user | The workflow catches blind spots that experience alone misses |
| "This is a minor case, full process is overkill" | Scale the process down, don't turn it off | Minor cases become major when unstructured; the process scales, not disappears |
| "I'll fill in the details later" | Complete each section before moving on | Deferred details are forgotten; real-time capture is more accurate |
| "The template output isn't necessary" | Always produce the structured output format | Structured output enables comparison, audit trails, and handoff to other teams |