Understanding Distributed Tracing
Introduction
In today’s world, applications use complex structures because a large number of microservices are deployed. As a result, it can be difficult to troubleshoot problems that may arise in the processing of a request if we are not familiar with the code or the internal structure of the application or with the microservice in which the problem is located. Microservices may contain hundreds or even thousands of processes that are all active at the same time. In certain cases, each task that is performed within a process may also have its own microservice or two. It is therefore not an easy task to determine which microservices belong to which piece of code or application, how these services are related to one another, which team is responsible for which services, and how much time is required for these microservices to carry out their respective tasks.
Therefore, the first challenge that comes from this situation is how to locate the microservices that are being negatively impacted so that it can be fixed. In most cases, the applications will keep the logs to identify any issues or problems in the application. However, if the request is going through a lot of microservices, then it will be difficult for the application to keep the logs, and even if they do keep the logs, it is possible that they will not be able to verify them because the timing…
