One of the challenges in microservices architecture is the ability to debug issues.
A simple user action might trigger a chain of downstream microservice calls.
It would be tedious to trace the logs related to a particular user action across microservices.
In addition to that, we might want to track down why a certain microservice call is taking so much time.
We can use Spring Cloud Sleuth to handle these kinds of issues.

Test

Distributed tracing is a key challenge in microservices architectures where a single user action can trigger chains of service calls. Spring Cloud Sleuth automatically adds trace and span IDs to logs, enabling correlation of log entries across services. Traces can be exported to Zipkin for visual inspection of call chains and latency. The guide covers adding the Sleuth starter dependency, understanding TraceID/SpanID patterns in logs, setting up a Zipkin server via executable jar or Docker, and configuring services to export trace data by setting the Zipkin base URL and sampler probability.

MicroServices - Part 6 : Distributed Tracing with Spring Cloud Sleuth and Zipkin

Using Spring Cloud Sleuth for Distributed Tracing