MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 13 · Monitoring, and knowing before the client does

Reporting to somebody non-technical

Lesson 140 of 184 · 3 min

What a monthly summary should contain, IN THEIR LANGUAGE, and WHAT IT SHOULD NOT CONTAIN AT ALL. The audience for this report is somebody who pays for the system and does not administer it, and almost every technical report written for them answers questions they did not ask. THEY WANT FOUR THINGS AND ALL FOUR ARE ABOUT OUTCOMES. WAS IT AVAILABLE? How much downtime, when, and what caused it — in a sentence each. Not a percentage on its own: "99.8%" sounds excellent and is four hours, and it matters entirely whether those were at 03:00 on a Sunday or 10:00 on the last day of the month. IS IT RECOVERABLE? Backups succeeded on this many nights, and a restore was last tested on this date. That second sentence is the most valuable thing in the whole report — Module 5 Lesson 2 — and it is the one nobody…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 13 · Monitoring, and knowing before the client does

  1. 1What is worth watching
  2. 2Checking availability honestly
  3. 3The check that runs on the box it watches
  4. 4Polling intervals, and what they cannot see
  5. 5Alerting somebody who will act
  6. 6Alert fatigue as a design failure
  7. 7The silent failure: nothing ran
  8. 8Reporting to somebody non-technical
  9. 9What breaks: the outage nobody was told about