Inny So and Andrew Jones explain the fundamentals of observability and how to implement it across complex systems.
Have you ever tried to debug a production outage, when your system comprises of apps your team has written, third-party apps your team runs, with logs going into some system, application performance metrics going into another system, and cloud platform metrics going somewhere else? Did you find yourself switching tabs, trying to correlate metrics with logs and alerts and finding yourself in a huge tangle? It is a nightmare. In the data world, we talk about aggregating all our data so we can derive new insights quickly, but what about our operational data.
Observability is your ability to be able to ask questions of your system without having to write new code, or grab new data. When you've got an observable system, it feels like you have debugging superpowers, but it can be challenging to even know where to start. If you can even convince your colleagues to start, finding the right tools can be challenging.
In this talk Inny and Andrew will talk about what monitoring and logging are not sufficient anymore (if they ever were), observability basics, and demo an observability platform that you can use to start your observability journey today.
––
thoughtworks.com/
Why it's here
2 people recommend this
What people say. Recommended as a helpful tech talk explaining observability standards and practices across multiple systems.
D
u/Diarkin r/ExperiencedDevs • Recommends
On “Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones”
Depends entirely on usecase and the "system".
APMs are the general industry standard but mostly for sync workloads with very real time requirements on alerts.
Asyc flows might require more specific solutions depending on the requirements.
Also implementing the above in one component is very different from doing it at an architectural level across multiple systems.
Here's an interesting tech talk I came across on the same.
