A microservice link monitoring method, device, equipment and medium

Abstract

The present application discloses a microservice link monitoring method, device, device and medium, the method comprising: creating a target probe and a target monitoring log format; based on the target probe and according to the target monitoring log format, collecting and The log data corresponding to the dubbo call of the target microservice link; obtain the log data from the target probe through the data collector and send the log data to the search server, so that the search server can query the target microservice Links are monitored and analyzed. This application creates a target probe, uses the target probe to collect log data corresponding to the target microservice link according to the target monitoring log format, and then sends the log data to the search server by the data collector, and the search The server monitors and analyzes the target microservice link. In this way, logs can be collected and analyzed automatically, improving the ability to locate system faults and performance bottlenecks.

Description

technical field [0001] The present invention relates to the field of computer technology, and in particular, to a microservice link monitoring method, apparatus, device and medium. Background technique [0002] At present, with the increasing popularity of the microservice application model, there are problems of timely detection and location of system faults in the microservice application scenario. In the prior art, system faults are determined by manually viewing logs, but since an Internet application is usually divided into multiple different modules, the logs generated by the calling process may be distributed among several or even dozens of different machines. Therefore, it may lead to the problem that the online problem cannot be quickly located and effectively solved in a short time. Therefore, it is very limited to locate the fault of the system by manually checking the log. In order to solve the above problems, local faults are handled by writing code in the prio...

AI Technical Summary

Problems solved by technology

In the prior art, system faults are determined by checking the logs manually, but since an Internet application is usually split into multiple different modules, the logs generated during the calling process may be distributed on several or even dozens of different machines Therefore, problems generated online may not be quickly located and effectively resolved in a short period of time. Therefore, manually checking logs to locate system faults has great limitations.

In order to solve the above problems, in the prior art, local faults are handled by writing codes, but since microservices are a distributed system, developers need to select and implement a message-based or remote procedure call protocol (ie, Remote Procedure Call Protocol, RPC) The inter-process communication mechanism makes the whole complex, and in the micro-service mode, modules need to call each other, and a request often needs to involve multiple services, thus reducing the universality of system fault location by writing code and speed

Images