Distributed Tracing Opening the Door to Visualisation and Correlation
summary
Distributed tracing proves a concrete way to stitch microservice calls into one transaction by instrumenting runtimes (Java bytecode agents, Node.js monkey‑patching or an SDK for custom spans), propagating traceparent header metadata, and collecting spans (trace ID, span ID, parent ID, timestamp, duration). A live Instana demo shows a browser → Node → Java → DB2 flow with JSON span payloads and timing: the end‑to‑end request measures 663 ms total with 416 ms attributed to the downstream service.
AI-written summary · about
chapters (11)
- 0:00Introduction to talk
- 2:11What is observability
- 3:16Monolithic to microservices
- 6:13Distributed tracing basics
- 7:41What is a tracer
- 13:02Instrumentation methods
- 16:11Tracing in action
- 23:49Correlation across services
- 31:06Live tracing demo
- 39:14Demo wrap-up and resources
- 40:25Q&A
related talks
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
22mDistributed Tracing
49mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
49mDistributed Tracing in Java? OpenTelemetry for the Rescue!
59mAn introduction to distributed tracing
45mLatency tracing in distributed Java applications
23mIntroduction to OpenTracing
07mWhy Tracing is a Lifesaver for E2E Tests of Distributed Systems?
