Making it observable

The SHORT MONITORING LIST from Module 13, in place and PROVEN TO FIRE. "Proven to fire" is the requirement, because monitoring that has never alerted is untested infrastructure — Module 13 Lesson 9's three failures are all monitoring that existed and did not work. THE LIST IS MODULE 13 LESSON 1 AND IT IS SHORT ON PURPOSE. Availability, space, the concurrent queue, backup success and error rates. Resist adding more on an estate you have just met — a long list produces alert fatigue before it produces value, and you do not yet know what normal looks like here. AVAILABILITY NEEDS BOTH AN EXTERNAL CHECK AND A DEEP ONE. External because a check on the box cannot report the box being down — Module 13 Lesson 3 — and deep because a process check passes for a system nobody can use, which is Module 13 Lesson 2. SPACE IS THE…

In this module: Module 18 · Capstone: a system handed over

1. 1The brief
2. 2Establishing what you have
3. 3Making it recoverable
4. 4Making it observable
5. 5The performance complaint
6. 6The handover