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

Don't be on the critical path


The practitioners of distributed tracing and performance optimization should know all about not being on the critical path. This applies to the organizational aspects as well. A tracing team cannot scale its effort in a large organization if it needs to go and make changes in hundreds of microservices. Tracing Quality Metrics was specifically designed to be a self-service tool that service owners may consult, make changes to the instrumentation, and check if that improves the metrics, all without involving the tracing team. The same principle applies to all other advice in this chapter: the tracing team should be doing surgical strikes to improve instrumentation in widely used frameworks, providing excellent documentation and troubleshooting guides, and focusing on the tracing platform. Ultimately, application developers are the domain experts for their own applications, the internal structure of those applications, and the internal threading model. The objective...