Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Distributed System Tracing

Distributed System Tracing

Once you’ve broken up your monolithic application into a micro services architecture like everyone’s been telling you to you’ll come upon a horrible realization. The profiling and analysis tools you’ve been using to monitor the performance of your application are no longer quite as useful as they once were. Most traditional profilers have no way to cross process and service boundaries and give meaningful insights into inter-process performance issues. This session will demonstrate the a tracing infrastructure you can put in place to monitor your distributed service oriented architecture. You’ll discover just how easy it is to instrument a system for tracing and visualize tracing data for highlighting issues and insights.

Dusty Burwell

January 07, 2016
Tweet

More Decks by Dusty Burwell

Other Decks in Technology

Transcript

  1. Trace ID Span ID Parent Span ID Client Start -

    timestamp Server Start - timestamp Server End - timestamp Client End - timestamp
  2. Trace ID Span ID Parent Span ID Client Start -

    timestamp Server Start - timestamp Server End - timestamp Client End - timestamp
  3. Trace ID Span ID Parent Span ID Client Start -

    timestamp Server Start - timestamp Server End - timestamp Client End - timestamp
  4. Trace ID Span ID Parent Span ID Client Start -

    timestamp Server Start - timestamp Server End - timestamp Client End - timestamp Service Name Endpoint Is Error? Error code Etc.
  5. Transport libraries (HTTP, etc) Middleware or similar Headers passed from

    instrumented libraries and received by middleware pass along Trace ID and Parent Span ID