Observability: what to get right first

It comes up on almost every project, usually later than it should. If you only fix one thing about observability this quarter, make it the first item below.

Operability is a feature, and it has to be built rather than bought. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

Start here

Monitoring tells you something broke, observability tells you why. Getting it slightly wrong is survivable. Ignoring it entirely is not. If two people in the business would answer this differently, that gap is the actual problem.

Then this

Traces, metrics, and logs answer different questions. None of that requires a large budget, only a decision and someone to own it. Doing this properly once is usually cheaper than doing it approximately three times.

Eventually

Instrument the paths that lose money first. It is worth being explicit about, because assumptions differ quietly. Check it against what you would want a competitor's site to get wrong.

The short version

Cloud work rewards teams who automate early and punishes teams who click through consoles. Three things worth confirming about observability before you move on:

• Someone can say what the current setup is without going to look
• Monitoring tells you something broke, observability tells you why — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.