Oracle Apps DBA: Keeping E-Business Suite Alive · Module 13 · Monitoring, and knowing before the client does
What is worth watching
Lesson 133 of 184 · 3 min
Availability, space, the concurrent queue, backup success and error rates. A SHORT LIST ON PURPOSE. The list is short because a long one is not read, and a monitoring system nobody reads is worse than none — it produces the belief that somebody is watching. AVAILABILITY, MEANING WHAT A USER WOULD DO RATHER THAN WHETHER A PROCESS EXISTS. Lesson 2, and it is first because everything else is secondary to the system being usable. SPACE, BECAUSE IT IS THE MOST PREDICTABLE FAILURE THERE IS. Module 12 Lesson 2's thresholds — time remaining rather than a percentage. It earns its place because it is the one failure you can always prevent given warning, and the archive destination alone justifies the whole item. THE CONCURRENT QUEUE, BECAUSE IT IS THE SILENT ONE. Requests pending far longer than usual, or managers that are not running — Module 8 Lesson 11's failures, none of…
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