Oracle Apps DBA: Keeping E-Business Suite Alive · Module 13 · Monitoring, and knowing before the client does
Alert fatigue as a design failure
Lesson 138 of 184 · 3 min
A monitor that fires EVERY DAY teaches people to ignore it, and IT WILL BE IGNORED ON THE DAY IT IS RIGHT. Alert fatigue is treated as a discipline problem — people should read their alerts — and it is a design failure, because the behaviour it produces is correct. A PERSON WHO IGNORES AN ALERT THAT HAS BEEN WRONG FORTY TIMES HAS LEARNED SOMETHING TRUE ABOUT IT. It does not predict anything worth acting on. They are not being careless; they are responding rationally to a signal with no information in it — and telling them to be more diligent does not change the signal. SO THE FIX IS ALWAYS TO THE ALERT RATHER THAN TO THE PEOPLE. Either it should not fire in those cases, or it should not exist. AND THE COST IS NOT THE IGNORED ALERT — IT IS THE CHANNEL. One noisy alert teaches people…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 13 · Monitoring, and knowing before the client does
- 1What is worth watching
- 2Checking availability honestly
- 3The check that runs on the box it watches
- 4Polling intervals, and what they cannot see
- 5Alerting somebody who will act
- 6Alert fatigue as a design failure
- 7The silent failure: nothing ran
- 8Reporting to somebody non-technical
- 9What breaks: the outage nobody was told about