Over the last few weeks, I spoke at our live tech show Elastic Byte - Season 3 about Observability, a topic that is so popular in DevOps circles.
If you are new to this term about Observability
(o11y), I’d recommend you look at one of my talks
where I specifically explain it!
I think there are many definitions now for Observability, but, for me, it always points back to this blog post written by Cindy Sridharan
I have always felt Observability like a developer productivity initiative than a new thing in the DevOps world 😅
Observability can help you gather evidence to investigate an intermittent issue that is not getting reproduced in your developer environment or help you correlate infrastructure metrics and code performance.
Observability is not just collecting data or monitoring alerts, even though they are quintessential in today’s cloud world.
Today, O11y is reality. Many engineering organizations have realized the importance of this. Some show these metrics in real-time as analytics on their platform, like loading a page in X milliseconds, etc.
The only problem I observe in this space is the growing tool fad. I believe there is always more than one way to solve a problem. There are many frameworks for Distributed Tracing, Logs Collection, Metrics Servers, but the concept remains the same.
Like Cindy said in the blog post, “No amount of "observability” or “monitoring” tooling can ever be a substitute to good engineering intuition and instincts.“
Watch our Observability series, where we focus on a wide variety of topics like JSON Logging, Open Telemetry, observing Kubernetes, and more.