Peek into Observability from testers lens
summary
A tester adopts instrumentation and builds a lightweight observability stack: centralized structured logs, plus traces metrics and logs to answer specific questions like which service failed and which request trace shows the error. The team proves a proof of concept that turns scattered per-service notepad log searches into searchable context, reduces blocked investigations, and surfaces unknown failure modes; the effort starts working but remains a partial rollout not yet fully complete.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:17Observability for testers
- 4:49Real-world observability need
- 8:00Observability concepts
- 9:05Logs metrics traces
- 13:19Questions observability answers
- 14:43Testers and observability
- 17:49Key takeaways
- 20:21Q&A
related talks
41mA peek into observability from testers lens
08m“Observability for testers”
23mA peek into observability from a tester's lens
24mWhat is observability-driven development?
24mBeyond Regression Testing: Observability for QA
39mHow Testability Drives Observability
47mObservability - Holistic Quality across Software Systems
01h 14mVisualizing Testability