Alert fatigue is the desensitization that happens when people receive more alerts than they can meaningfully handle. Noisy, repetitive or non-actionable notifications teach responders that most pages can be safely dismissed.
Why it matters
The danger is that a real outage looks the same as the hundredth false alarm. Fatigue lengthens response times, causes missed incidents and contributes to burnout and turnover on on-call teams. It is usually a sign of poorly tuned alerting rather than lazy people.
Example
A team receives 150 alerts a week, and 120 of them need no action. Reviewing the list shows three causes: a flapping check on a staging server, a CPU alert with a threshold too low, and duplicate notifications for one incident. After fixing these, weekly alerts fall to 30 and nearly every one needs a response.
Common mistakes
- Adding alerts after every incident without removing old ones.
- Paging for conditions that can wait until morning. Route them to a ticket or chat channel instead.
- Alerting on single failed checks with no retry or multi-location confirmation.
- Never reviewing which alerts were acted on.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.