MDC-based multi-thread link tracking method and device and computer readable storage medium

Abstract

The invention discloses an MDC-based multi-thread link tracking method and device and a computer readable storage medium. The tracking method comprises the following steps of S1, finishing link identifier creation through a preset rule; S2, completing the inheritance of the multi-thread link parameters by adopting a preset rule; S3, completing the recording of the response time according to a preset method; S4, outputting a recording result of the response time to the log file by adopting a preset principle; and S5, completing recording of the unique identifier of the multi-thread link according to a preset criterion. The method has the beneficial effects that the link unique identifier is generated for each http request, each http request can be quickly searched under the action of the unique identifier, the execution time, the entry parameter and the response time of each http request can be distinguished, and meanwhile, all logs in the log file can be screened, so that online problems can be quickly positioned and troubleshot. And thus, the online problem processing capability is effectively improved.

Description

technical field [0001] The present invention relates to the technical field of log tracking systems, in particular to an MDC-based multi-threaded link tracking method, device and computer-readable storage medium. Background technique [0002] After the SpringBoot microservice receives the http request, it will call the custom controller, service, dao, driver and other modules to complete the basic business process. During this process, the controller, service, dao, and driver will respond to multiple http requests concurrently, and the service The log will be written concurrently by multiple http requests. Compared with the log of a service, it will be written alternately to the log file. If an exception occurs in the service, the method of alternately printing the log will make it impossible to accurately and quickly locate the source of the exception through the log. It is impossible to accurately troubleshoot the problem, and at the same time, it is impossible to quickly ...

AI Technical Summary

Problems solved by technology

[0002] After the SpringBoot microservice receives the http request, it will call the custom controller, service, dao, driver and other modules to complete the basic business process. During this process, the controller, service, dao, and driver will respond to multiple http requests concurrently, and the service The log will be written concurrently by multiple http requests. Compared with the log of a service, it will be written alternately to the log file. If an exception occurs in the service, the method of alternately printing the log will make it impossible to accurately and quickly locate the source of the exception through the log. It is impossible to accurately troubleshoot the problem, and at the same time, it is impossible to quickly locate the response time of each http request, and it is impossible to provide a basis for optimizing the system

Images