Oracle Apps DBA: Keeping E-Business Suite Alive · Module 13 · Monitoring, and knowing before the client does
Alerting somebody who will act
Lesson 137 of 184 · 3 min
Who, how, and at what hour. AN ALERT WITH NO OWNER AND NO ACTION IS A LOG ENTRY WITH A NOTIFICATION ATTACHED. An alert exists to cause an action, and one that causes none is noise wearing an urgent costume. SO THE TEST BEFORE CREATING ANY ALERT IS TWO QUESTIONS: WHO ACTS ON THIS, AND WHAT DO THEY DO? If either has no answer, it belongs on a report rather than in an alert channel. Every estate has alerts nobody can act on, and each one erodes the credibility of the ones that matter. WHO MEANS A NAMED ROLE RATHER THAN A DISTRIBUTION LIST. An alert to a team address is an alert everybody assumes somebody else has seen — which is Lesson 9's first failure. Route by who can fix it: space to the administrator, a rejected business record to the business, a certificate to whoever owns it. HOW…
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