Book Image

Mastering Distributed Tracing

By : Yuri Shkuro
Book Image

Mastering Distributed Tracing

By: Yuri Shkuro

Overview of this book

Mastering Distributed Tracing will equip you to operate and enhance your own tracing infrastructure. Through practical exercises and code examples, you will learn how end-to-end tracing can be used as a powerful application performance management and comprehension tool. The rise of Internet-scale companies, like Google and Amazon, ushered in a new era of distributed systems operating on thousands of nodes across multiple data centers. Microservices increased that complexity, often exponentially. It is harder to debug these systems, track down failures, detect bottlenecks, or even simply understand what is going on. Distributed tracing focuses on solving these problems for complex distributed systems. Today, tracing standards have developed and we have much faster systems, making instrumentation less intrusive and data more valuable. Yuri Shkuro, the creator of Jaeger, a popular open-source distributed tracing system, delivers end-to-end coverage of the field in Mastering Distributed Tracing. Review the history and theoretical foundations of tracing; solve the data gathering problem through code instrumentation, with open standards like OpenTracing, W3C Trace Context, and OpenCensus; and discuss the benefits and applications of a distributed tracing infrastructure for understanding, and profiling, complex systems.
Table of Contents (21 chapters)
Mastering Distributed Tracing
Contributors
Preface
Other Books You May Enjoy
Leave a review - let other readers know what you think
15
Afterword
Index

Feature extraction


The number of possible aggregations and data mining approaches is probably only limited by engineers' ingenuity. One very common and relatively easy-to-implement approach is "feature extraction." It refers to a process that takes a full trace and calculates one or more values, called features, that are otherwise not possible to compute from a single span. Feature extraction represents a significant reduction in the complexity of the data because instead of dealing with a large directed acyclic graph (DAG) of spans, we reduce it to a single sparse record per trace, with columns representing different features. Here are some examples of the trace features:

  • Total latency of the trace

  • Trace start time

  • Number of spans

  • Number of network calls

  • Root service (entry point) and its endpoint name

  • Type of client (Android app or iOS app)

  • Breakdown of latency: CDN, backend, network, storage, and so on

  • Various metadata: Country of origin of the client call, data center handling the request, and...