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

Why is it hard to deploy tracing instrumentation?


Before we talk about solving the organizational challenges of deploying tracing, let's talk about what those challenges are. What is so different about end-to-end tracing? It seems all we need to do is add some instrumentation, just like we do for gathering metrics or logs. We spent several chapters in Part II on the technical aspects of adding instrumentation, including solutions to make it easier through auto-instrumentation, so what have we missed?

Consider a small tech company that has about a dozen software engineers. If this company embraces the idea of microservices-based architecture, it can build a system that contains from 10 to 20 microservices. Most engineers would know what each service does, if not necessarily the details of how they all interact. If they decide to add distributed tracing instrumentation to the system, it is generally not a large task, and it can be accomplished by one or two people in a short period of time...