A microservices-based application might have several services running and communicating amongst themselves. Things get complicated when one or more services fail, and you need to know which one failed and why. It’s also essential that you’re able to comprehend the whole request flow — which services were invoked, how many times and in what order
API-gateway is the start point for all requests so this microservice should have to initialize logging context, logging context is a set of identifiers and labels that help us to track each request in different services
UUID besides the service name could be the minimum logging context to track users' logs in different microservices
A microservices-based application might have several services running and communicating amongst themselves. Things get complicated when one or more services fail, and you need to know which one failed and why. It’s also essential that you’re able to comprehend the whole request flow — which services were invoked, how many times and in what order
API-gateway is the start point for all requests so this microservice should have to initialize logging context, logging context is a set of identifiers and labels that help us to track each request in different services
UUID besides the service name could be the minimum logging context to track users' logs in different microservices