Monitoring
Alert Fatigue
Alert fatigue is the desensitisation that happens when an on-call team receives too many alerts, especially false positives. It causes real incidents to be missed, slows MTTR, and burns out engineers.
In depth
Alert fatigue typically begins with well-meaning monitors that alert on every threshold breach, regardless of duration or impact. Within weeks, the on-call rotation learns to ignore the noise — and then misses a real incident buried in the same channel.
Fixes include: confirm-and-retry logic before alerting, severity-aware routing (only critical alerts page the on-call), grouping related alerts into a single incident, and regular reviews of the noisiest monitors with a bias toward deleting them.
Why it matters
Every false alert is a tax on the team's attention. A monitoring system that emits 50 alerts a day is worse than one that emits 5, even if the 50-alert system technically catches more. Quality of alerting beats quantity every time.
How Lemwatch helps with alert fatigue
Lemwatch monitors alert fatigue continuously and alerts you the moment something changes.
Smart alerting →Related terms
Incident
An incident is a confirmed period of degraded or unavailable service that requires human attention. Incidents …
Website Monitoring
Website monitoring is the continuous automated checking of a website's availability, performance, security, co…
False Positive
A false positive is a monitoring alert that fires when nothing is actually wrong — a transient network blip, a…
Recovery Point Objective
Recovery Point Objective (RPO) is the maximum amount of data loss (measured in time) a business can tolerate a…
Mean Time Between Failures
Mean Time Between Failures (MTBF) is the average time a system operates between one incident and the next. MTB…
Browse the full Lemwatch monitoring glossary (47 terms).

