This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Friday, January 29 • 10:10 - 11:00
How to properly blame things for causing latency: An introduction to Distributed Tracing and Zipkin

Sign up or log in to save this to your schedule and see who's attending!

Latency analysis is the act of blaming components for causing user perceptible delay. In today's world of microservices, this can be tricky as requests can fan out across polyglot components and even data-centers. In many cases, the root source of latency isn't a component, but rather a link between components.

This session will overview how to debug latency problems, using call graphs created by Zipkin. We'll use trace zipkin itself, setting up from scratch using docker. While we're at it, we'll discuss how the model works, and how to safely trace production. Finally, we'll overview the ecosystem, including tools to trace ruby, c#, java and spring boot apps. We'll wrap up with a look at simulation with Spigo and future works in Distributed Context Propagation.

When you leave, you'll at least know something about distributed tracing, and hopefully be on your way to blaming things for causing latency!


Adrian Cole

Adrian is an active member of cloud interoperability circles. He is the founder of a few popular open source projects, notably Apache jclouds and Netflix feign. Recently, he’s focused on distributed tracing, particularly in the OpenZipkin project. Adrian works at Pivotal in the Spring Cloud OSS team.

Friday January 29, 2016 10:10 - 11:00
Kosmos - Room 02

Attendees (14)