Field notes
Field notes
Short pieces on application analytics choices and the craft of writing cluster reliability reports.
Notes from engagements and roundtables. Nothing here replaces a formal assessment; these pieces share vocabulary and judgement calls we see repeatedly.
Reading failover drills as reliability evidence
Failover exercises produce some of the richest material for cluster reliability reporting — if you capture more than a pass/fail tick.
Read the note
Ranking reliability actions after the report
A simple consequence-first ranking for actions that fall out of application analytics — so the backlog does not swallow the only fixes that matter.
Read the note
Draft readings without softening the findings
How we run draft reviews so technical contacts can correct facts without sanding consequence out of a reliability report.
Read the note
When healthy CPU hides a dying dependency
Why cluster reliability reports should treat dependency lag as a first-class signal, not a footnote under infrastructure metrics.
Read the note