The first useful health check is external.
A daemon can be alive while the service is unreachable. Start with the interface people actually depend on, then work inward.
Read field note →
JOURNAL / SHORT OBSERVATIONS
Notes from the
operating edge.
Field Notes are deliberately small. They record an observation, a question or an operating pattern without pretending that every problem requires a framework.
Latency budgets are more useful than latency goals.
Separate DNS, connection setup, transport and processing instead of hiding them behind one number.
Read field note →Recovery should be practiced before it is urgent.
The worst time to discover that a backup is incomplete is during the incident it was supposed to solve.
Read field note →A quiet log is not the same as a healthy service.
Absence of errors can mean stability, missing instrumentation, or simply that no useful request reached the system.