Skip to content
Jacob NolletteCloud & software engineer
Topic · 8 case studies

Reliability

Monitoring that watches outcomes instead of jobs, backups that have actually been restored, and the incidents that taught me the difference.

Every Log in One Place

Logs are the thing everyone agrees they should centralise and nobody wants to pay for. The usual outcome is that the noisy source drowns the useful one, retention gets cut to a week, and the one event you needed is three days past the edge of the index. I centralised...

Every Disk in the Organisation, on One Dashboard

Half the drives in my fleet had no reported age, no wear level and no temperature. Not wrong values — no values. And I did not know, because the dashboard showed the drives that did report, and a missing row does not look like anything. Why the standard collector was...

When the Failure Domain Was a Lie

A replicated storage cluster’s core promise is that a copy of your data lives on more than one machine, so losing a machine loses no data. That promise is enforced by a placement rule, and the rule has a setting for what counts as a separate failure domain: a...

Backups Nobody Had Ever Restored

There is a specific kind of confidence that comes from a backup job with a green checkmark, and it is unearned. A backup is a hypothesis. The test is a restore. The databases in my cluster were being captured by filesystem-level replication — the volumes were mirrored...