Oracle Apps DBA: Keeping E-Business Suite Alive · Module 13 · Monitoring, and knowing before the client does
Checking availability honestly
Lesson 134 of 184 · 3 min
A PROCESS THAT IS RUNNING IS NOT A SYSTEM THAT WORKS. Checking the thing a user would do rather than THE THING THAT IS EASY TO CHECK. Every estate's availability check is easier to write than it is useful, and the gap between the two is where outages hide. CHECKING A PROCESS EXISTS IS THE EASIEST AND THE WEAKEST. Module 4 Lesson 9's first failure — a service that started and answers nothing — passes this check perfectly. So does a managed server that is up and not accepting requests, and an application tier pointing at a database that is not open. CHECKING A PORT ANSWERS IS BETTER AND STILL WEAK. Something is listening; whether it can do anything is untested. CHECKING A PAGE LOADS IS BETTER AGAIN AND STOPS SHORT OF THE ONE THING THAT MATTERS. A login page that renders proves the web layer and the managed server…
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