Oracle Apps DBA: Keeping E-Business Suite Alive · Module 13 · Monitoring, and knowing before the client does
Polling intervals, and what they cannot see
Lesson 136 of 184 · 3 min
A five-minute check CANNOT SEE a three-minute outage, and its record will show AN UNINTERRUPTED HEALTHY DAY. SAMPLING IS NOT MEASUREMENT. This is a structural property rather than a tuning question, and it is the one people misunderstand most about monitoring. A POLLED CHECK TAKES SAMPLES. Anything shorter than the interval can fall entirely between two samples — and it is not that the outage is uncertain or partially recorded. It is invisible, and the record positively asserts that everything was fine. WHICH MEANS "NO ALERTS FIRED" MUST BE READ AS "NO ALERT FIRED AT A SAMPLE POINT". Those are different statements and only the second is true. AND A SHORT OUTAGE IS NOT A SMALL ONE. Three minutes is enough for every in-flight transaction to fail, for a batch job to abort, for an interface to miss its window, and for a room full of users to notice. The…
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