Loading…
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, February 17 • 15:05 - 15:55
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!

Feedback form is now closed.
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. While we're at it, we'll discuss how the
model works, and how to safely trace production. We'll demo with an
example app you can download, using spring boot with spring cloud
sleuth. Finally, we'll overview the ecosystem, including tools to
trace other languages and frameworks.

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

Speakers
avatar for Adrian Cole

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 February 17, 2017 15:05 - 15:55
Gallery (1st floor)