Request Id Tracing in python Applications
Tracing a request from start to end is critical for diagnosing issues quickly. This becomes difficult in a highly concurrent system because logs are interspersed with each other. It becomes even harder in the microservices architecture where a request may travel through multiple services before being complete.
In order to diagnose issues in such an environment, we need to have a unique identifier to tie up all the logs through different services. Casualty helps you do exactly that.Through Casualty the requests can be stitched together from start to end using multiple services.You will need to integrate casualty with all your microservices.
All the log events for a particular request across different micro-services and async processes(celery, kombu )will be tied to a unique uuid.You can navigate through different log event throughout the lifecycle of a request with just a single uuid.
Your log requests will look something like this.
Thats all :)
You can connect me here .
