A peek into observability from a tester's lens
summary
An invoice microservices system shows daily production incidents and developers debugging with many Notepad++ windows and manual Control F searches. Introducing trial tools like Honeycomb trial plus centralized dashboards, structured logs, traces and metrics makes root cause tracing possible without shipping code. The claim is observability requires a mindset not just shiny tools; implementing structured, centralized logs plus alerts and traces reduces context switching, surfaces unknown unknowns, and turns incidents into feedback that prevents repeats.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:31What is observability?
- 7:36By using data
- 14:23How does it help testers?
- 20:12Key takeaways
related talks
41mA peek into observability from testers lens
21mPeek into Observability from testers lens
31mObservability for Developers: How to Get There
44mObservability: Superpowers for Developers
08m“Observability for testers”
29mObservability for Developers: How to Get From Here to There
29mObservability; a gentle introduction
33mWhat Developers Should Know About Observability