Lesson 3 of 4 · Free to read
Session guide
Session guide — Distributed Tracing & TraceQL
Visual companion to the Lesson. Use in study groups or when you want the diagram first.
Watch
Course video
Course video
Flow
60-second summary
Metrics say p95 is high. Traces show which span — SNS publish vs S3 put — ate the time. TraceQL lets you ask about the shape of the request tree, not just attributes.
MNC 2026: OpenTelemetry semantic conventions + W3C tracecontext across async messaging is table stakes. Tempo + TraceQL replace “SSH and guess” for latency RCAs.
Chunks
- A trace is a tree: Parent/child/descendant relationships answer “was this error inside a user request or a background retry?”
- Async is where traces break: HTTP headers don’t exist on SNS→SQS — inject/extract via message attributes (or OTel AWS instrumentation).
- Sampling is upstream of queries: If the sampler dropped a trace, TraceQL returns empty — that is not “no bug.”
- TraceQL vs PromQL/LogQL: Same
{ }filter feel, plus>/>>structural operators.
Session guide — Distributed Tracing & TraceQL.