How Testability Drives Observability
Talkat ContainerCon @ Open Source Summit Europe 2022 · on Wednesday, 2022-09-14· at 16:40· Wicklow Hall 1 (Level 2), Convention Centre Dublin, Spencer Dock, N Wall Quay, North Wall Dublin 1, D01 T1·
summary
Shows how OpenTelemetry traces become executable assertions using trace-based testing with the open source Tracetest (Kubeshop) tool. Demonstrates a Pokemon microservice, creates UI and CLI tests that fail, adds span attributes for HTTP status and response body, and reruns tests to prove instrumentation fixes the issue. Finds the external API returns 404 not 500, publishes tests, runs them in CI, and exports JUnit results. Live demo proves trace assertions improve observability and catch gaps before production.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:29Agenda
- 6:39What Distributed Tracing Is
- 9:17The Life Cycle of Adding Instrumentation to Your App
- 10:49Observability Is Hard
- 12:37Api Testing
- 12:52Response-Based Testing Trace-Based Testing
- 15:03Advantages of Trace-Based Testing
- 15:52Create a Feedback Loop
- 17:37Test Driven Development
- 22:12Trace-Based Testing
- 25:07Timing Based Test
- 32:11Semantic Attributes
- 35:01Benefits
related talks
36mHow Testability Drives Observability- 36mHow Testability Drives Observability
43mObservability-Driven Development with Kubernetes
24mWhat is observability-driven development?
16mBreaking the Chain of Blame: How to Get True Test Observability?
21mThe Road to Observability Everywhere at Monday.Com
33mThe Observant Developer - OpenTelemetry from code to prod
39mEfficient Debugging and Logging with OpenTelemetry in Go