Explain spring cloud distributed log link tracking in detail
First of all, why use link tracking@ H_ 403_ 1@
When we call between micro services, there may be errors, but we don't know which service is the problem. At this time, we can track and find which service is wrong through the log link@ H_ 403_ 1@
It has another advantage: when we are in the enterprise, everyone may be responsible for a service. We can check that the service we are responsible for will not make an error through the log. When an error occurs when calling other services, we can determine that it is not our own service that has made an error, so we can also find that the responsibility is not our own@ H_ 403_ 1@
Based on the call between microservices, if you don't understand, please refer to my previous blog: the call between microservices in spring cloud and Eureka's self-protection mechanism @ H_ 403_ 1@