Source: thenewstack.io
Distributed Tracing: Why It’s Needed and How It EvolvedCategory: Software, Data, Kubernetes
Other people may go a step further, and think of the action of tracing — navigating through logs from different services and computers, literally tracing the path of a request as it moves through a system. Conveniently enough, “distributed tracing” is really a combination of both of these processes — you can think of it as the “call stack” for a distributed system, a way to represent a single request as it flows from one computer to another.
The cloud made it possible to easily provision new infrastructure and scale it around the world, and all of this led to even more complexity and confusion.
One solution to this constellation of complexity is distributed tracing — specifically, distributed tracing built for cloud native, polyglot applications.
In the next part of this series, I’ll cover the issues that distributed systems can lead to, and why distributed tracing is the backbone of understanding how our systems function.
The cloud made it possible to easily provision new infrastructure and scale it around the world, and all of this led to even more complexity and confusion.
One solution to this constellation of complexity is distributed tracing — specifically, distributed tracing built for cloud native, polyglot applications.
In the next part of this series, I’ll cover the issues that distributed systems can lead to, and why distributed tracing is the backbone of understanding how our systems function.
Related Articles
Community Partners
DevOps Careers