Exercise 2: Alert Fatigue and Level Misuse — Possible Solution
====================================================================

WHAT ALERT FATIGUE MEANS
------------------------------
Per this chapter, alert fatigue is what happens once "ERROR-level logs
(or alerts built on top of them) routinely include things that aren't
actually problems" - the people reading them "learn - correctly, given
the evidence - to stop trusting that an ERROR line means something
worth acting on." It's a rational response to bad evidence, not a
character flaw in whoever stops paying attention.

HOW MISUSING ERROR DIRECTLY CAUSES IT
------------------------------
Per this chapter, if routine events (like a mistyped password) are
repeatedly logged at ERROR alongside genuine failures, the ERROR level
stops being a reliable signal of "something is actually wrong." Every
time a reader investigates an ERROR and finds a routine, harmless
event behind it, their trust that ERROR means "worth investigating"
erodes a little further - and this happens specifically BECAUSE the
level was misused, not for any other reason.

THE CONSEQUENCE ONCE FATIGUE SETS IN
------------------------------
Per this chapter, "by the time a genuine, serious error appears, it's
just one more line in a stream that's already been mentally tuned
out." The real danger isn't just annoyance - it's that the one ERROR
that actually mattered gets missed, precisely because the level had
already been trained (by its own past misuse) to not be trusted.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly defines alert fatigue using this chapter's own language,
and correctly traces the causal chain from level misuse to eroded
trust to a real error eventually being missed.