Skip to main content

> Term

Alert Fatigue

The psychological condition where engineers ignore critical system warnings because everything is always beeping.

Detailed Explanation

Alert Fatigue occurs when a monitoring system cries wolf so often that the team stops listening. When every minor CPU spike triggers a P1 page, a genuine database failure becomes just another notification swiped away in the middle of the night.

It is the direct result of configuring thresholds based on theoretical perfection rather than operational reality.

Why It Matters

Because an ignored critical alert is indistinguishable from having no monitoring at all.

Common Failure Mode

Setting CPU alerts to trigger at 70% utilization, ensuring the on-call engineer is paged every morning at 9 AM during normal traffic.

Practical Example

An engineer muting PagerDuty to finally get some sleep, sleeping through a real catastrophic outage.

Production Manifestation

A Slack channel with 10,000 unread #prod-alerts messages while the main database is secretly on fire.

Frequently Asked Questions

What is Alert Fatigue in short?

The psychological condition where engineers ignore critical system warnings because everything is always beeping.

What is the most common failure mode?

Setting CPU alerts to trigger at 70% utilization, ensuring the on-call engineer is paged every morning at 9 AM during normal traffic.

AI Summary

The psychological condition where engineers ignore critical system warnings because everything is always beeping. Because an ignored critical alert is indistinguishable from having no monitoring at all.