Oracle Apps DBA: Keeping E-Business Suite Alive · Module 13 · Monitoring, and knowing before the client does
The check that runs on the box it watches
Lesson 135 of 184 · 3 min
IT CANNOT REPORT THAT THE HOST IS DOWN. Why an external check is NOT OPTIONAL, and what an internal one is STILL GOOD FOR. A check that runs on the machine it is watching shares that machine's fate, and this is not a subtle limitation — it is total for the failure that matters most. WHEN THE HOST GOES DOWN, THE CHECK GOES DOWN WITH IT. It sends no alert, because it is not running. And the absence of an alert is exactly what a healthy system also produces, so the monitoring record shows an uninterrupted good day across a complete outage. WHICH IS THE WORST PROPERTY A MONITOR CAN HAVE: IT IS SILENT IN PRECISELY THE CASE IT EXISTS FOR. Everything else it reports is true, and the one event it must catch is invisible to it by construction. SO AN EXTERNAL CHECK IS NOT AN IMPROVEMENT, IT IS…
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