Latency tracing in distributed Java applications
summary
Shows a working prototype of two simple services (one Spring, one Kotlin-like) that propagate a request id and produce spans collected by Zipkin; demonstrates how a Java agent instrumentation injects bytecode to record spans without changing source, how HTTP and JMS headers carry trace ids, and how custom socket protocols need manual extraction. Live demo queries recent traces (e.g. last 100) and visualizes per-span timings, warns about added latency and gaps for reactive streams and unsupported protocols.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 5:52Production performance issues
- 10:51What is latency tracing
- 18:44Tracing theory
- 23:39Live demo
- 36:36Tracing pros and cons
- 40:52Q&A
related talks
01h 11mDistributed Tracing : Latency Analysis for Your Microservices
42mAn introduction to distributed tracing and Zipkin
46mHow to Properly Blame Things for Causing Latency
33mDistributed Tracing - Implementing Latency Analysis for microservices on Cloud Foundry
49mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems
42mDistributed Tracing Opening the Door to Visualisation and Correlation
29mDistributed Tracing of Microservices - Neil Stevenson, Hazelcast
49mDistributed Tracing in Java? OpenTelemetry for the Rescue!