Download to read offline
Uploaded byGianluca Arbezzano
Value of your metrics: goodbye monitoring, welcome observability
The document discusses the differences between observability and monitoring, emphasizing the importance of debugging and operational work. It highlights the need for teams to run their code and to utilize tools for better insights in cloud, containers, and distributed systems. The author includes references to their Twitter and blog for further information on the topic.
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
Value of your metrics: goodbye monitoring, welcome observability
- 1. Value of yourmetrics Goodbye monitoring, welcome observability @gianarb - gianarb.it
- 2. Observability vs Monitoring Learningvs eye examination Debugging vs Ops work
- 3. SWEs should runtheir code We need Ops people. I Ops
- 4. ● Event ● Metric ●Tracing Terms: Logs are just a transport layer
- 5. Instrumentation is partof the development workflow
- 6.
- 7. Staging environment areuseless Allow your team to test in production
- 8. Why all thistroubles? ● Cloud ● Containers ● Distributed systems
- 9. Build tools tohave a better point of view on your system
- 10. Do you needmore? ● @mipsytipsy Charity Major on twitter ● @gianarb (it’s my twitter username) ● https://gianarb.it/blog/observability ● https://www.youtube.com/watch?v=1wj ovFSCGhE
Editor's Notes
- #3 Observability is more around how to learn a codebase. It is about debugging not about dashboards or graphs. When you get paged and you look at one of your dashboards you troubleshoot quick because you already know what the problem is. Dashboard don’t speak enough for somebody that doesn’t know the app.
- #4 I am Software Engineer, deploy my code to production is the best experience I never had and it took me to the next level. Production environment is the best learning experience for a developer to understand how its code really works or does not with real traffic, real customers but you need to give them the right tools and the right skills to build a comfortable production environment
- #5 All of them are useful
- #6 Instrument application for logs, metrics, traces can be expensive
- #7 You build dashboard from answer that you had after a page. A lot of pages, a lot of dashbords... It doesn’t scale and it doesn’t look a work for engineers
- #8 Distributed system are complicated. Replicate them is hard and keep databases in sync, reproduce traffic is hard.. So the best place to test is production.