Observability-Driven Development with Kubernetes

on YouTube ↗43m

" summary

Describes using Tracetest with OpenTelemetry on Kubernetes to make integration tests assert on distributed traces instead of internal code. Shows a concrete example where a book-list endpoint exposes a custom span attribute (booklist count = 3), and tests detect availability spans mismatch (true vs false) causing a test failure even though infra and HTTP status are fine. Notes Tracetest installs in ~40s, supports chained test suites, duration checks (<500ms), and only reads the traces it generates.

AI-written summary · about

" chapters (17)

1. 0:00Welcome
2. 1:11Microservice testing challenges
3. 3:43Distributed tracing use
4. 6:13Book system example
5. 8:18Traditional integration limits
6. 10:48Trace-based testing alternative
7. 12:11Observability-Driven Development
8. 15:29Tracetest intro
9. 17:38Tracetest in Kubernetes
10. 21:55Tracetest example
11. 25:52Timing and attributes
12. 28:21External service integration
13. 33:18Tracetest setup
14. 35:28OpenTelemetry benefits
15. 37:58Observability benefits
16. 38:41Tracetest resources
17. 39:25Q&A

" related talks

• 39mHow Testability Drives ObservabilityKen Hamric · ContainerCon @ Open Source Summit Europe 2022
• 24mWhat is observability-driven development?Adnan Rahic · Conf42 Observability 2023
• 36mHow Testability Drives ObservabilityMatheus Henrique Pereira Nogueira de Paula · Open Source Summit Latin America 2022
• 16mDistributed Tracing is Awesome, Testing is Not... Until NowAdnan Rahic · KCD Austria 2023
• 28mImplementing Observability in KubernetesJose Romero · KCD Lima, Perú 2024
• 21mThe Road to Observability Everywhere at Monday.ComDavid Gohberg · Observability Day North America 2024
• 36mHow Testability Drives ObservabilityMatheus Henrique Pereira Nogueira de Paula · CloudOpen @ OSS LATAM 2022
• 34mReduce Complexity with Distributing TracingSherwood Zern · Developer Summit 2020