Let’s debunk the myths that go around the topic!
Monitoring vs. Observability
The definitive guide to best practices of observability. Or maybe not so much …
In a world where every job title uses acronyms or abbreviations from all sorts of different words — I’m looking at you SRE, DevOps, NetOps, NetSecOps, and all the other combinations of the words Site, Networking, Operations, Development, and Security.
Surely there are more combinations generated daily and to be fair, it’s getting really hard already to stay on top of it.
However, we are gathered here to talk about another phenomenon that is — observability (or o11y for those of you who like to nerd out with numeronyms). I’ll quickly plug in a good tweet about numeronyms that surely made me chuckle.
Getting deeper into the subject between m8g and o11y (that’s monitoring and observability, folks) then Yuri Shkuro, a software engineer at Uber has put it this way: Monitoring is about measuring what you decide in advance is important while observability is the ability to ask questions that you don’t know upfront about your system.
