When working with microservices that communicate over the HTTP protocol, you will want to use correlation IDs to track individual requests.

Because requests might flow through many services that are spread across multiple systems, tracking them with correlation IDs will be your only hope of detecting and diagnosing errors that might creep into the middleware systems.

This article discusses what correlation IDs are, why they are useful, and how they can be used in ASP.Net Web API.What are correlation IDs?
Let’s assume you have implemented a microservices architecture.
In an application comprised of microservices, different aspects of incoming requests will be handled by different microservices, all working asynchronously on their specific tasks and ultimately coming together to generate the response. Now, if something goes wrong, how would you determine by looking at the logs exactly where the request failed? Your logs might contain millions upon millions of log messages.
It would be a daunting task to find the relevant log entries among so many messages.To read this article in full or to leave a comment, please click here

Leave a Reply