Chapter 14. Under the Hood of a Distributed Tracing System
This last chapter is aimed at engineers or DevOps people tasked with deploying and operating a distributed tracing backend in their organization. Since my own experience is mostly related to Jaeger, I will be using it as an example. I will try to avoid focusing on very specific details of Jaeger configurations, since they may change after the book is published while the project continues evolving. Instead, I will use them to illustrate the general principles and the decisions you need to make when deploying a tracing platform. Many of the topics that we will discuss apply equally well to any other tracing backend, and even to using hosted solutions like AWS X-Ray and Google Stackdriver, or offerings from commercial vendors.
Why host your own?
As the creator and a maintainer of an open source tracing system, I would obviously have a conflict of interest if I were to advocate for everyone to run their own tracing backend...
