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

Styles of instrumentation


The completely manual instrumentation we did in Chapter 4, Instrumentation Basics with OpenTracing, was useful to demonstrate the core principles, but in practice, that instrumentation style is very rare, as it is very expensive and simply not scalable for large, cloud-native applications. It is also quite unnecessary because in a microservices-based application, most instrumentation trace points occur next to process boundaries, where the communications are performed by the means of a small number of frameworks, such as RPC libraries.

If we instrument the frameworks, we need to do it only once and then reuse that instrumentation across the application. This does not mean that manual instrumentation in the application has no place at all, but usually it is reserved for special cases where some unique application logic warrants it, for example, to monitor access to some custom shared resource.

There is another style of instrumentation commonly referred to as agent...