The real cost of ignoring observability
The version of this that works is simpler than the version most people imagine. Nobody bills you for neglecting observability. The cost shows up somewhere else.
Operability is a feature, and it has to be built rather than bought. Check it against what you would want a competitor's site to get wrong.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Monitoring tells you something broke, observability tells you why
- Rework, once the problem is finally visible
Traces, metrics, and logs answer different questions. Getting it slightly wrong is survivable. Ignoring it entirely is not. It is the sort of thing that looks like polish right up until it costs you an enquiry.
What to do next
Instrument the paths that lose money first. The reasoning matters more than the rule, because the rule has exceptions. It is worth deciding this deliberately rather than inheriting whatever the last person set up.
What this looks like day to day
The bill is a design document: it tells you exactly what your architecture actually does. Three things worth confirming about observability before you move on:
- Someone can say what the current setup is without going to look
- Instrument the paths that lose money first — and you know whether that is true here
- There is a way to tell whether the last change to this helped
The point is not perfection, it is knowing which of these you have consciously chosen to skip.