Distributed Tracing is Awesome, Testing is Not... Until Now
summary
Distributed traces become test assertions: instrumentation with openTelemetry sends spans to a central collector (Tempo) and Grafana for inspection, while Trace test polls for an embedded parent span ID and asserts on spans (for example “import span must not contain an exception”). The system is open source (MIT), has ~12 integrations, a server+UI+CLI that exports JUnit, handles delayed traces via configurable polling and sampling via collector rules, and a SaaS option is planned.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:02Why tracing is awesome
- 2:03Testing tools gap today
- 3:27OpenTelemetry and Grafana
- 4:09Trace-based assertions
- 5:34Demo: Pokemon import failure
- 7:00Fixing with Trace Test
- 8:25Trace testing advantages
- 9:07Q&A: Trace delays and sampling
- 11:36Q&A: Trace sources and integrations
- 12:17Q&A: Dynamic tests and data
- 12:58Q&A: Exporting test results
- 13:41Q&A: YAML vs UI
- 14:46Q&A: Trace Test license
related talks
22mDistributed Tracing
30mTesting in A Distributed Systems World
32mDistributed Tracing in Action: Our Journey with OpenTelemetry
29mIntroduction to Distributed Tracing
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
01h 28mUnderstanding Distributed Systems with OpenTelemetry
49mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
57mYour Distributed System is Talking to You: OpenTelemetry
