Follow The (Full)stack Trace: Understand Your App with Distributed Tracing
summary
A concrete claim: distributed traces make a user click visible across frontend and backend so bottlenecks are found and fixes validated. Example stack: the Conduit demo uses Redux middleware to start/finish spans, a trace ID header on superagent requests, and Express/mongoose on the server, with traces visualized in Jaeger. The Jaeger JavaScript client is incomplete, so vendor libraries are often used; traces prove whether changes actually reduce latency.
AI-written summary · about
chapters (8)
- 0:00Introduction to tracing
- 2:42The challenge of observability
- 5:59Traditional debugging methods
- 9:40Visualizing distributed traces
- 12:43Strategies for instrumentation
- 15:06Implementing tracing in apps
- 17:57Tools and the future of Jaeger
- 20:30Real-world impact and conclusion
related talks
20mThe (Full)stack Trace: Understand Your App with Distributed Tracing
22mTracing is for Everyone, Not Just Backend Engineers. (How Tracing Could Help Front-e...
51mNavigating Distributed Traces
22mDistributed Tracing
59mAn introduction to distributed tracing
24mDistributed Tracing : New DevOps Foundation.
42mDistributed Tracing Opening the Door to Visualisation and Correlation
57mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
