WO2022022446A1

WO2022022446A1 - Log printing method, device and system

Info

Publication number: WO2022022446A1
Application number: PCT/CN2021/108370
Authority: WO
Inventors: 喻波; 李艳丽
Original assignee: 华为技术有限公司
Priority date: 2020-07-31
Filing date: 2021-07-26
Publication date: 2022-02-03
Also published as: CN114064384A

Abstract

A log printing method is used for controlling log printing so as to reduce the number of printed logs and avoid the occupation of a large quantity of resources due to log printing. The method comprises: a first service module receiving a first network request, which is used for invoking the first service module; the first service module printing a log on the basis that an operation error occurs in the process of processing the first network request by means of the first service module; and if in the process of processing the first network request, the first service module sends a second network request to invoke a second service module, the first service module printing a log on the basis that an error identifier is carried in a first network response which is received by the first service module from the second service module. The first network response is for the second network request, the first service module and the second service module belong to a target invoke chain, and the error identifier indicates that there is a service module, on which an operation error occurs, in the target invoke chain.

Description

Method, device and system for printing log

This application claims the priority of the Chinese patent application with the application number of 202010762131.9 and the application title of "A method, device and system for printing logs", which was submitted to the State Intellectual Property Office of China on July 31, 2020, the entire contents of which are by reference Incorporated in this application.

technical field

The present application relates to the technical field of call chains, and in particular, to a method, device and system for printing logs.

Background technique

With the development of technology, software has evolved from the original single software system to the current service-oriented software system. Monolithic software system means that a software runs in an operating system, and often has only one process, and all commands of the software are completed in the operating system, such as QQ software. A service-based software system often includes multiple sub-software, which can run in one or more operating systems, and each sub-software constitutes a business module. Multiple business modules with calling relationships form a calling chain, which is used to process a class of network requests from clients.

Since a type of network request needs multiple business modules in a call chain to be processed, and the calling relationship between these multiple business modules may be complicated, when the service-based software system fails, it is necessary to quickly locate the faulty business module. Especially important. At present, the log printed by the business module is mainly used to locate the business module with problems. Specifically, when the service module receives a network request, it prints an entry log; when the service module sends a network response, it prints an exit log. Finally, analyze the business module with problems through the entry log and exit log.

However, due to the large business volume of the service-oriented software system, each call chain in the service-oriented software system will process a large number of network requests, and a large number of entry logs and exit logs need to be printed. Processes are undoubtedly resource-intensive.

SUMMARY OF THE INVENTION

An embodiment of the present application provides a method for printing logs, which is used to control the printing of logs, so as to reduce the number of logs to be printed, so as to avoid taking up a large amount of resources due to the printing of logs.

A first aspect of the embodiments of the present application provides a method for printing logs, the method includes: a first service module receives a first network request, the first network request is used to call the first service module, and the first network request may come from a client, It can also come from other business modules in the target call chain; based on the operation error of the first business module in the process of processing the first network request, or based on the first network response received by the first business module from the second business module that contains Error identification, the first service module prints a log, wherein the first network response is for the second network request, and the second network request is the process of the first service module processing the first network request to call the second service module. In the case of sending, the first service module and the second service module belong to the target call chain, and the error identifier indicates that there is a service module with an operation error in the target call chain. Wherein, there may be various forms of the error identification, for example, it may be the value of the field added in the first response.

First identify the business module that is running wrong in the target call chain, and then print the log, which can control the printing of the log, thereby reducing the number of logs to be printed, so as to avoid printing logs and occupying a lot of resources; Reducing the number of log prints affects the location of the faulty business module.

In an implementation manner, within the preset first cycle, when the first service module has a service module with an operating error in the target call chain, the number of logs printed is less than the first preset number. The first period may be set according to actual needs, for example, one minute; the first preset number may also be set according to actual needs, for example, may be set to 5, 6, 7, and 8.

Control the number of logs printed by the first business module in the first cycle and when there is a business module with an operating error in the target call chain, so as to prevent a business module from running incorrectly due to the same reason in the first cycle, As a result, the first service module prints a large number of logs; therefore, the embodiment of the present application can play a role of controlling the number of logs printed by the first service module without affecting the location of the faulty service module.

In an implementation manner, after the first service module receives the first network request, the method further includes: the first service module saves the data in the first network request to the memory; the first service module sends the first network request for the first network request. The second network response, the second network response indicates the result of calling the first service module. The printing of the log by the first service module includes: the first service module prints the entry log according to the stored data in the first network request; the first service module prints the exit log according to the data in the second network response.

After the first service module receives the first network request, it does not print the log, but saves the data in the first network request to the memory; when the first service module runs incorrectly in the process of processing the first network request, or When the first network response carries an error identifier, the first business module prints the entry log according to the data in the saved first network request, thereby avoiding printing the entry log when it is not determined that there is a business module with an operating error in the target call chain , occupying resources.

In an implementation manner, the first network request comes from a third service module, and the third service module belongs to the target call chain; sending the second network response to the first network request by the first service module includes: running based on the first service module If there is an error or the first network response carries an error identifier, the first service module sends a second network response carrying the error identifier to the first network request to the third service module, so that the third service module prints a log.

In an implementation manner, the method further includes: based on the first network request carrying the error identifier or the operation error of the first service module, the first service module sends the second network request carrying the error identifier to the second service module.

In an implementation manner, the method further includes: the first service module receives a third network request, and the third network request is used to call the first service module, wherein the third network request and the first network request are processed in the target call chain Received during the process of the same type of service request; based on the fact that the first service module does not run an error in the process of processing the third network request, and the received third network response does not contain an error identifier, the first service module does not print log.

In the case that the first business module does not run in error, and the received third network response does not contain an error identifier, the first business module does not print the log, which reduces the number of log prints and does not affect the location of the wrong business module; Moreover, since there is no business module with running error in the target call chain most of the time, the embodiment of the present application can greatly reduce the number of logs to be printed.

In an implementation manner, the method further includes: the first service module receives a third network request, and the third network request is used to invoke the first service module; based on a preset second period, the first service module is processing the third network In the case where there is no operation error during the request process and the received third network response does not contain an error identifier, the number of logs printed by the first service module is less than the second preset number, and the first service module prints the logs.

In the case where there is no business module with an operating error in the target call chain, the first business module prints a log, which belongs to the correct log, so it can be used as a reference for the error log to determine the business module with an operating error; In the second cycle, the number of logs printed by the first business module in the above-mentioned situation is less than the second preset number, so that the number of logs printed can be controlled, preventing too many correct logs from being printed and occupying too many resources.

In an implementation manner, the target call chain belongs to the target service system and is used to process specific types of service requests sent by the client. The target service system further includes a log management module, and the specific type of service requests include the first service request and the second service. request, the target call chain further includes a fourth service module; the first network request is received by the first service module in the process of processing the first service request by the target call chain; wherein, the first network request may be the first network request from the client Service requests can also be network requests from other service modules.

The method further includes: the log management module obtains the log printed by the business module in the target call chain during the process of processing the first service request by the target call chain; the log printed by the business module in the target call chain does not include the log printed by the fourth business module. log, the log management module obtains the log printed by the fourth service module in the process of processing the second service request by the target call chain, and the log printed by the fourth service module in the process of processing the second service request by the target call chain is used to call the target The process of the chain processing the first service request is analyzed, and it is indicated that there is no service module in the target invocation chain that has an operating error during the process of the target invocation chain processing the second service request.

Use the correct log printed by the fourth service module in the process of processing the second service request by the target call chain to analyze the process of processing the first service request by the target call chain, so as to avoid the process of processing the first service request by the target call chain During the analysis, it is mistakenly believed that the fourth service module runs in error during the process of processing the first service request by the target call chain, thereby improving the accuracy of log analysis.

In an implementation manner, among all the service requests of the specific type of service requests processed by the target call chain, the request time of the second service request is earlier than and closest to the request time of the first service request.

Among all the service requests of the specific type of service requests processed by the target call chain, the request time of the second service request is earlier than and closest to the request time of the first service request, so that the correct log obtained by the log management module is closer to, The fourth business module prints the correct log in the process of processing the first business request by the target call chain, thereby improving the accuracy of analyzing the process of the target call chain processing the first business request, and avoiding the correct log selected by the log management module and the fourth business request. The correct log printed by the module during the process of processing the first service request by the target call chain is quite different, which affects the analysis of the process of the target call chain processing the first service request.

A second aspect of an embodiment of the present application provides an apparatus for printing a log, the apparatus comprising: a receiving unit, configured to receive a first network request; a log printing unit, configured to print a log based on an operating error in the process of processing the first network request, or The log is printed based on the received first network response to the second network request from the second service module that carries the error identifier, and the second network request is sent to call the second service module during the process of processing the first network request. , the second business module belongs to the target call chain, and the error identifier indicates that there is a business module with an operation error in the target call chain.

In an implementation manner, within the preset first cycle, when the first service module has a service module with an operating error in the target call chain, the number of logs printed is less than the first preset number.

In an implementation manner, the apparatus further includes: a saving unit, configured to save the data in the first network request to a memory; a sending unit, configured to send a second network response to the first network request, the second network response indicating The result of calling the first service module; the log printing unit is configured to print the entry log according to the stored data in the first network request, and print the exit log according to the data in the second network response.

In an implementation manner, the first network request comes from a third service module, and the third service module belongs to the target call chain; the device further includes a sending unit for running errors based on the first service module or the first network response carrying Error identification, sending the second network response carrying the error identification to the first network request to the third service module, so that the third service module prints a log.

In an implementation manner, the receiving unit is further configured to receive a third network request, and the third network request is used to call the first service module; the log printing unit is further configured to process the third network request based on the first service module. There is no running error in the process, and the third network response received does not contain an error flag, and no log is printed.

In an implementation manner, the receiving unit is further configured to receive a third network request, and the third network request is used to call the first service module; the log printing unit is further configured to process the third network request based on the first service module. There is no operation error in the process, and the received third network response does not contain an error identifier, and the log is printed; the first business module does not operate in error, the received third network response does not contain an error identifier, and the preset second During the period, the number of logs printed by the first service module is less than the second preset number.

In an implementation manner, the target call chain is used to process a specific type of service request sent by the client, and the specific type of service request includes a first service request; the first network request is that the first service module processes the first service request in the target call chain received during the process.

In an implementation manner, the target call chain belongs to the target business system, the target business system further includes a log management module, the specific type of business request further includes a second business request, and the target call chain further includes a fourth business module;

The log management module includes: a first obtaining unit, configured to obtain the log printed by the business module in the target call chain in the process of processing the first service request by the target call chain;

The second obtaining unit is configured to obtain the log printed by the fourth service module in the process of processing the second service request in the target call chain based on that the log printed by the service module in the target call chain does not include the log printed by the fourth service module, to Analyze the process of the target call chain processing the first service request, the log indication printed by the fourth service module in the process of processing the second service request by the target call chain, and the target call chain in the process of processing the second service request by the target call chain. There are no business modules that are running incorrectly in .

A third aspect of an embodiment of the present application provides a server, including: at least one processor and a memory, where the memory stores computer-executable instructions that can run on the processor, and when the computer-executable instructions are executed by the processor, the The server executes the method for printing a log according to any one of the embodiments of the first aspect.

A fourth aspect of an embodiment of the present application provides a chip or a chip system, the chip or chip system includes at least one processor and a communication interface, the communication interface and the at least one processor are interconnected through a line, and the at least one processor is used for running a computer program or instruction , so as to execute the method for printing a log according to any one of the embodiments of the first aspect.

A fifth aspect of the embodiments of the present application provides a computer storage medium, where the computer storage medium is used for storing computer software instructions used by the above server, and the computer storage medium includes a program for executing a program designed for the server;

The server may be the device for printing a log described in the aforementioned second aspect.

A sixth aspect of the embodiments of the present application provides a computer program product, where the computer program product includes computer software instructions, and the computer software instructions can be loaded by a processor to implement the printing described in any one of the implementation manners of the first aspect above method of logging.

A seventh aspect of the embodiments of the present application provides a business system, including a target invocation chain, where the target invocation chain includes a first business module; the first business module is configured to execute the print log according to any one of the implementations of the first aspect above Methods.

In an implementation manner, the target call chain further includes a fourth service module, and the service system further includes a log management module; the target call chain is used to process a specific type of service request sent by the client, and the specific type of service request includes the first service request and the second service request; the first network request is received by the first service module in the process of processing the first service request by the target call chain.

The log management module is used to obtain the log printed by the business module in the target call chain in the process of processing the first service request by the target call chain; and the log printed by the business module in the target call chain does not include the log printed by the fourth business module. log, to obtain the log printed by the fourth service module in the process of processing the second service request by the target invocation chain, to analyze the process of processing the first service request by the target invocation chain, and the fourth service module in the target invocation chain to process the second service The log printed in the process of the request indicates that there is no service module with an operation error in the target call chain in the process of processing the second service request by the target call chain.

Description of drawings

1 is a schematic diagram of the architecture of a business system in an embodiment of the application;

2 is a schematic diagram of a process of processing a specific type of network request by a call chain in an embodiment of the application;

3(a) is a schematic diagram of an embodiment of a method for printing a log in an embodiment of the present application;

FIG. 3(b) is a schematic diagram of another embodiment of the method for printing a log in an embodiment of the present application;

FIG. 4 is a schematic diagram of an embodiment of processing a first network request by a first service module in an embodiment of the present application;

5 is a schematic diagram of another embodiment of processing a first network request by a first service module in an embodiment of the present application;

6 is a schematic diagram of an embodiment of a first service module integrated with a Tracer unit in an embodiment of the application;

7 is a schematic diagram of an embodiment of an apparatus for printing a log provided by an embodiment of the present application;

8 is a schematic structural diagram of a server in an embodiment of the present application;

FIG. 9 is a schematic diagram of an embodiment of a service system provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings in the embodiments of the present application.

Embodiments of the present application provide a method, device, and system for printing logs, which are used to control the printing of logs, thereby reducing the number of logs to be printed, so as to avoid printing logs and occupying a large amount of resources.

The embodiments of the present application may be applied to a service system including at least one server. At least one business module can be deployed on each server. When multiple business modules need to be deployed on a server, multiple virtual machines can be deployed on the server, each virtual machine is installed with an operating system, the virtual machine can also be called a node, and then on each node Deploy one or more business modules in .

For example, please refer to FIG. 1 , which is a schematic diagram of the architecture of a business system in an embodiment of the present application. The business system in Figure 1 includes three servers, one of which is deployed with a business module A, one server is deployed with business module B and business module C, and the other server is deployed with business module D and business module E; this is Five business modules form a call chain for processing network requests from clients (for example, browsers).

Usually, different call chains are used to process different types of network requests from clients, and network requests from clients can be specifically called service requests, so it can also be understood that each call chain is used to process specific types of services from clients ask. This embodiment of the present application does not specifically limit a specific type of service request, for example, it may be a login request, a payment request, or an account query request, and the like.

The following describes the process of the call chain processing a specific type of service request with reference to FIG. 2 . As shown in Figure 2, the user operates on the client, triggering the client to send a login request to the business system in Figure 1, wherein the login request is received by the business module A; the business module A sends a login authentication request to the business module B; After receiving the login authentication request, the service module B sends an authentication request to the service module C; after receiving the authentication request, the service module C sends a request for obtaining user information to the service module D; the service module D receives the request for obtaining user information. After the request is made, a request for obtaining user information is sent to the service module E.

After the service module E receives the request for obtaining user information, it sends a network response to the request for obtaining user information from the network to the service module D; after the service module D receives the network response from the service module E, it sends the service module C to obtain The network response to the request for user information; after receiving the network response from the service module D, the service module C sends a network response to the authentication request to the service module B; after receiving the network response sent by the service module C, the service module B sends the The service module A sends a network response to the login authentication request; finally, after receiving the network response from the service module B, the service module A sends a network response to the login request to the client.

It can be understood that the call chain shown in FIG. 2 only includes five business modules such as A-E, and the calling relationship between these five business modules is relatively simple. The process in which one service module sends a network request to another service module and receives a network response to the network request from the other service module is called the calling process of the service module. Relationships are called invocation relationships. In practical applications, the number of business modules included in the call chain is large, and the call relationship may be complicated. For example, after receiving the login authentication request from the business module A, the business module B can call other business modules in addition to the business module C. That is, a business module can have a calling relationship with multiple business modules.

Therefore, in order to more accurately locate the business module with problems in the call chain, it is necessary for the business modules to print their own logs during the calling process, and finally locate the problematic business module by analyzing the logs printed by each business module in the call chain. .

The following describes the process of printing the log by the service module. Printing the log means that the service module saves the operation data of the service module recorded in the memory to the memory. The print log includes the print entry log and the print exit log. Specifically, the business module printing the entry log means that the business module saves the data in the received network request to the memory; the business module prints the exit log means that the business module will send the network request. The data in the response is saved to memory.

Wherein, the data in the network request may include the trace identifier TraceId, the time when the network request was received, and the network response identifier, etc.; similarly, the data in the network response may also include the trace identifier TraceId, the time when the network response was received, and the network response identifier. Wait.

The TraceId is globally unique and is used to mark each network request sent by the client, and each network request sent by the client carries a different TraceId. For example, in the call chain shown in FIG. 2 , the service module A receives multiple network requests from the client, and the TraceId contained in each network request is different. In addition, after receiving the network request, business module A will add the TraceId in the network request to the network request sent to business module B, and business module B will also add the TraceId to the network response sent to business module A. .

Therefore, if the client sends a specific type of service request, in the process of processing the specific type of service request in the call chain, the network request sent by each service module in the call chain, the received network request, the sent network response and the received The network response will carry the TraceId used to mark a specific type of service request.

The network response identifier is used to indicate the current status of the network request. For example, if the value of the network response identifier is 200, it indicates that the current status of the network request is successful; if the value of the network response identifier is 404, it indicates that the current status of the network request is successful. The status is no network response.

It is understandable that for a certain call chain, it is often necessary to process a large number of specific types of business requests, so for each specific type of business request, each business module in the call chain prints logs (including entry logs and exit logs), Then the business modules in the call chain will inevitably print a lot of logs, which will occupy a lot of resources such as memory, Input/Output (I/O), and Central Processing Unit (CPU).

To this end, an embodiment of the present application provides a method for printing logs, the method can identify the situation that there is a business module with an operating error in the call chain, and print the log when there is a business module with an operating error in the calling chain In this way, it does not affect the positioning of the business module in which the problem occurs, but also realizes the control of the log printing, thereby reducing the number of log printing and the resource occupation of the log printing.

Specifically, please refer to FIG. 3( a ), which is a schematic diagram of an embodiment of a method for printing a log in an embodiment of the present application. As shown in FIG. 3( a ), an embodiment of the present application provides an embodiment of a method for printing a log, including:

Step 101, the first service module receives a first network request, and the first network request is used to invoke the first service module.

It can be understood that each business module in the call chain will receive a network request when it is called; for example, each business module in the call chain shown in Figure 2 will receive a network request.

As one of the multiple service modules included in the target call chain, the first service module will also receive a first network request during the process of being called. The first network request may come from the client or the target call other business modules in the chain; taking the call chain shown in Figure 2 as an example, when the first business module is business module A, the first network request comes from the client; when the first business module is business module B, The first network request comes from service module A.

Based on the foregoing description, the first network request may include the trace identifier TraceId, the time when the network request was received, the network response identifier, and the like.

Step 102, the first service module prints a log based on an error in the operation of the first service module in the process of processing the first network request, or based on the fact that the first network response from the second service module received by the first service module carries an error identifier .

The first network response is for the second network request, and the second network request is sent by the first service module for invoking the second service module in the process of processing the first network request. The first service module and the second service module It belongs to the target call chain, and the error flag indicates that there is a business module running wrong in the target call chain.

It should be noted that, the process of processing the first network request by the first service module includes two cases, and the two cases are described below with reference to FIG. 4 and FIG. 5 .

Case 1: As shown in Figure 4, the first service module first performs the first internal operation after receiving the first network request. After the first internal operation, the first service module sends the second service module to the second service module. Two network requests, the second network request is used to call the second service module; after that, the first service module will receive the first network response from the second service module, and the first network response indicates the result of calling the second service module. After receiving the first network response, the first service module may perform a second internal operation (for example, may process the first network response), and after the second internal operation, the first service module sends a message to the second service module. A second response to the first network request.

Wherein, if the first service module is one of service module A, service module B, service module C, and service module D in the call chain shown in FIG. 2 , the process of processing the first network request by the first service module belongs to the above-mentioned process. The first case.

In the above-mentioned first case, if the first service module runs incorrectly for the first time or the first network request carries an error identifier, the error identifier at this time specifically represents the service invoked prior to the first service module in the target call chain There is a business module with an error in the module, and the first business module will add an error flag to the second network request; similarly, if the second business module runs wrong for the first time after receiving the first network request, or the second business If the second network request received by the module carries an error identifier, the second service module will also add the error identifier to the network requests sent to other service modules. For example, if the network request from service module A received by service module B carries an error identifier, it means that service module A is running in error; if the network request from service module B received by service module C carries an error identifier, It means that business module B is running incorrectly or business module A is running incorrectly.

In the above-mentioned first case, the first service module may print a log when there is an operation error, and may also print a log when the received first network response carries an error identifier. Wherein, the operation error of the first service module includes the first internal operation error of the first service module after receiving the first network request, and also includes the second internal operation error after receiving the first network response.

The second case: as shown in Figure 5, the first service module runs internally after receiving the first network request, and after the internal operation, the first service module sends a second response to the first network request, that is, the first service The module did not call the business module in the target call chain.

There are also at least two application scenarios for the second case. One of the application scenarios may be that the first business module is the last business module in the calling chain, so the first business module can complete the processing of the first network request without calling other business modules. For example, the first business module may is the business module E in the call chain shown in FIG. 2 . Another application scenario may be that the first service module has an internal operation error or the first network request carries an error identifier. In this case, the first service module directly sends the second response to the first network request without calling other service modules. In order to indicate that there is a service module with running error in the target call chain of the client or service module that sends the first network request.

Wherein, if the first network request carries an error identifier, it means that there is an error in the data in the first network request, which usually leads to an internal operation error of the first service module. Therefore, in this embodiment of the present application, the first network request carries an error identifier. The situation is a special case of the internal operation error of the first business module.

Based on this, in the second case above, the first service module may print a log when there is an error in operation. The operation error of the first service module includes an internal operation error of the first service module after receiving the first network request.

There may be various forms of the error identification, which are not specifically limited in this embodiment of the present application. For example, a new field can be added to the first response, when this field is used to indicate whether there is a business module with an operation error in the target call chain; specifically, when the value of this field is true, it indicates that the target call chain is in There is a business module with an operating error. When the value of this field is false, it means that there is no business module with an operating error in the target call chain.

In the embodiment of the present application, in the case of identifying a business module with an operating error in the target call chain, printing the log can play a role in controlling the printing of the log, thereby reducing the number of logs to be printed, so as to avoid printing the log and occupying a lot of resources ; It will not affect the location of the faulty business module due to blindly reducing the number of log prints.

It is understandable that if a certain business module in the target call chain runs incorrectly for some reason, the business module may continue to run incorrectly due to this reason for a period of time. The modules will continue to print logs; since the reasons for the errors in the operation of the business modules are the same during this period of time, only a certain amount of logs can be used to locate the business modules with problems and determine the reasons for the errors in the operation of the business modules.

Therefore, the embodiment of the present application controls the number of logs printed by the first service module when there is a service module with an operating error in the target call chain. As an optional method, in the preset first cycle, when the first service module has a service module with an operating error in the target call chain, the number of logs printed is less than the first preset number.

The first period may be set according to actual needs, for example, one minute; the first preset number may also be set according to actual needs, for example, may be set to 5, 6, 7, and 8.

In the embodiment of the present application, the number of logs printed by the first business module in the first cycle and when there is a business module with an operating error in the target call chain is controlled, so as to prevent the first cycle from being caused by the same reason A certain business module runs incorrectly, so that the first business module prints a large number of logs; therefore, the embodiment of the present application can control the number of logs printed by the first business module without affecting the location of the wrong business module. effect.

It should be noted that there are various methods for controlling the number of logs printed by the first service module in the preset first cycle to be less than the first preset number, which is not specifically limited in this embodiment of the present application. Exemplarily, in the target call chain, the number of logs is periodically controlled by a service module that receives a specific type of service request from a client. Specifically, in the current first cycle, the service module that receives the specific type of service request from the client adds the remaining number of error logs to the network request sent to the other service module in the process of calling another service module; when When the other business module needs to call other business modules, it also adds the remaining number of error logs to the network request sent to other business modules, and so on, each business module in the target call chain will receive the remaining number of error logs. Number of error logs.

In the case that there is a business module with an operating error in the target call chain, if the number of remaining error logs is greater than 0, the business module in the target call chain can print the log. Wherein, in the current first cycle, the service module that receives a specific type of service request from the client, every time it receives a specific type of service request from the client, decrements the remaining number of error logs by 1 until it becomes 0. In the case that there is a business module with an operating error in the target call chain, if the number of remaining error logs is equal to 0, the business module in the target call chain does not print the log.

When the next first cycle comes, the service module that receives the specific type of service request from the client will update the remaining number of error logs to the first preset number, thereby realizing periodic control of the number of logs.

Taking the call chain shown in Figure 2 as an example, after receiving the network request from the client, service module A adds the remaining number of error logs to the network request sent to service module B, where the initial value of the remaining number of error logs is is the first preset number, and it is assumed here that the first preset number is 5; correspondingly, the service module B will receive the remaining number of error logs (5), and the service module B can determine whether to print according to the remaining number of error logs log. Specifically, when the service module B runs incorrectly or the service module B receives the network response from the service module C with an error identifier, since the number of remaining error logs is 5, which is greater than 0, the service module B prints the log.

Similarly, when business module B calls business module C, business module B will add the remaining number of error logs (5) to the network request sent to business module C, so that business module C can Quantity determines whether to print the log. The method for the business module C to determine whether to print the log is the same as that for the business module B. For details, please refer to the aforementioned judgment process of the business module B for understanding.

After the service module A receives the network request from the client again, the remaining number of error logs added to the network request sent to the service module B will become 4. As the number of network requests received from the client by the service module A increases, the number of remaining error logs added will decrease sequentially. When the number of remaining error logs is reduced to 0, even if the service module B runs incorrectly or the service module B receives an error identifier in the network response from the service module C, the service module B does not print the log.

The service module A updates the remaining number of error logs to the first preset number every one minute (ie, the period for updating the remaining number of error logs).

Based on the foregoing description, it can be known that the first service module print log includes print entry log and print exit log, and the process of print log will be described below.

As shown in FIG. 3( a ), in another embodiment of the method for printing a log provided by the embodiment of the present application, after the first service module receives the first network request, the method further includes:

Step 103, the first service module saves the data in the first network request to the memory.

Wherein, step 103 is executed after step 101 is executed. If the first service module sends the second network request to the second service module, step 103 is performed before the first service module sends the second network request.

In the embodiment of the present application, after receiving the first network request, the first service module will save the data in the first network request to the memory, so as to prevent the data in the first network request from being cleared.

Before saving the data in the first network request to the memory, the data in the first network request may be sorted first, and the embodiment of the present application does not specifically limit the sorting method of the data in the first network request.

Step 104, the first service module sends a second network response to the first network request, and the second network response indicates the result of calling the first service module.

Wherein, step 104 is executed after step 102 is executed.

Based on the foregoing description, after receiving the first network request, the first service module can process the first network request through internal operation, and send the second network response according to the processing result; the first service module can also perform the first The second internal operation is performed, and then the second network request is sent to the second service module, and the first network response from the second service module is received, and the second internal operation is performed according to the first network response to complete the response to the first network request. processing, and finally sending a second network response according to the processing result.

It can be understood that, if the first network request comes from the client, the first service module sends a second network response to the client; if the first network request comes from other service modules, the first service module sends other services to the client. The module sends a second network response.

Based on the above process step 102, the printing log of the first service module may include:

The first service module prints the entry log according to the stored data in the first network request.

Wherein, printing the entry log includes outputting the saved data in the first network request to the memory.

The first service module prints the exit log according to the data in the second network response.

Wherein, printing the export log includes outputting the saved data in the second network response to the memory.

It should be noted that there is no sequence between printing the entry log and printing the exit log.

In the existing method of printing logs, the business module prints the entry log after receiving the network request, and after printing the entry log, sends a network request to the next business module to call the next business module, after that, the network The data in the request is cleared from memory. In the embodiment of the present application, after receiving the first network request, the first service module does not print the log, but saves the data in the first network request to the memory; if the first service module is processing the first network If there is an error in the operation of the request, or the first network response carries an error identifier, the first service module will print the entry log according to the stored data in the first network request.

Compared with the existing method of printing logs, in this embodiment of the present application, the first service module does not clear the data in the first network request after sending the second network request to the second service module, but prints the entry log and the data in the first network request. After the log is exported, the data in the first network request and the data in the second network response in the memory are cleared.

In the embodiment of the present application, after receiving the first network request, the first service module does not print the log first, but saves the data in the first network request to the memory; when the first service module is processing the first network request When there is an error in the operation of the process, or the first network response carries an error identifier, the first service module prints the entry log according to the data in the saved first network request, so as to avoid the operation error in the undetermined target call chain. In the case of a module, the entry log is printed, resulting in a waste of resources.

Based on the foregoing description, it can be known that the first network request may come from a service module or a client. The following describes the case where the first network request comes from the service module.

In another embodiment of the method for printing a log provided by the embodiment of the present application, the first network request comes from a third service module, and the third service module belongs to the target call chain; the first service module sends the first network request for the first network request. Two network responses include:

Based on the operation error of the first service module or the error identifier carried in the first network response, the first service module sends the second network response carrying the error identifier to the first network request to the third service module, so that the third service module Print log.

It can be understood that the third business module will print a log after receiving the second network response carrying the error identifier, wherein the process of printing the log by the third business module is the same as the process of printing the log by the first business module, so the This will not be repeated.

The process of printing the log by the first service module in the case of an error in the operation of the first service module or the first network response received by the first service module carries an error identifier has been described above. In the case of an operation error and the received network response does not carry an error identifier, the process of printing the log by the first service module will be described.

As shown in FIG. 3( a ), based on the foregoing embodiments, in another embodiment of the method for printing a log provided by the embodiment of the present application, the method further includes:

Step 105, the first service module receives a third network request, and the third network request is used to invoke the first service module.

Wherein, step 105 is executed after step 104 is executed.

It should be noted that the third network request is similar to the first network request, and specifically, the third network request may be understood by referring to the relevant description of the first network request.

Wherein, after receiving the third network request, the first service module will save the data in the third network request to the memory.

Step 106 , based on the fact that the first service module does not have an error in the process of processing the third network request, and the received third network response does not contain an error identifier, the first service module does not print a log.

Since the first business module does not run in error, and the received third network response does not contain an error identifier, it means that there is no business module with an error in the target call chain; in order to control the number of logs printed, in this case, the first A business module does not print logs.

The first service module may clear the stored data in the third network request after determining that it does not run in error and the received third network response does not contain an error identifier.

In the embodiment of the present application, when the first service module does not run in error, and the received third network response does not contain an error identifier, the first service module does not print the log, which reduces the number of log prints and does not affect the Locate service modules that run incorrectly; and because there is no service module that runs incorrectly in the target call chain most of the time, the embodiment of the present application can greatly reduce the number of logs printed, and significantly reduce the resource occupation of printing logs.

It is understandable that in the process of locating the faulty business module, the log printed when there is no faulty business module in the target call chain may be used as a reference, so there is no running fault in the target call chain. In the case of the business module, some logs can also be printed; however, in order to avoid printing a large number of logs and occupying resources, the number of logs to be printed can be controlled.

The following describes the process of printing the log by the first service module when there is no service module with an operating error in the target call chain with reference to FIG. 3(b). Specifically, as an optional implementation manner, the method further includes:

Step 107, the first service module receives a third network request, and the third network request is used to invoke the first service module.

It should be noted that the third network request and the first network request are received during the process of processing the same type of service request by the target call chain. For example, the first network request is a login request with an error The network request is a login request without an error identifier; since the third network request is similar to the first network request, the third network request can be understood by referring to the relevant description of the first network request.

Step 108, based on the preset second period, the first service module has no error in the process of processing the third network request, and the received third network response does not contain an error identifier, the first service module has been When the number of printed logs is less than the second preset number, the first service module prints the logs. It can be understood that, within the preset second period, if there is no error during the processing of the third network request, and the received third network response does not contain an error identifier, if the first service module has When the number of printed logs is equal to the second preset number, the printing of logs will be stopped.

In the embodiment of the present application, in the case where there is no business module with an operating error in the target call chain, the first business module prints the log, but within the preset second cycle, the first business module prints the log in the above situation The number is smaller than the second preset number, so that the printing number of the log can be controlled.

The method of controlling the number of logs printed by the first business module to be less than the second preset number is the same as the method of controlling the number of logs printed by the first business module to be less than the first preset number. The description of the method in which the number of printed logs is less than the first preset number should be understood.

The second period can also be set according to actual needs, for example, it can be one minute; the second preset number can also be set according to actual needs, for example, it can be set to 1.

It should be noted that, in the case where there is no business module with an operating error in the target call chain, the first business module can control the log printing through steps 105 and 106, or can perform log printing through steps 107 and 108. control.

Based on the foregoing description, it can be seen that the target call chain is used to process a specific type of service request sent by the client, and the number of the specific type of service request can be multiple; as an optional method, the target call chain belongs to the target service system, and For processing the specific type of service request sent by the client, the target service system further includes a log management module, the specific type of service request includes a first service request and a second service request, and the target call chain further includes a fourth service module.

The first network request is received by the first service module in the process of processing the first service request by the target call chain; it is understandable that the first network request may be the first service request from the client, or may be from other service modules network request.

It should be understood that the process of processing the first service request by the target call chain is usually analyzed according to the logs printed by each service module in the target call chain in the process of processing the first service request by the target call chain, so as to locate the wrong operation. business module. Before the analysis, it is necessary to obtain the logs printed by each service module in the target call chain during the process of processing the first service request by the target call chain.

Based on the above description, TraceId is globally unique and is used to mark each network request sent by the client, and the logs printed by each business module in the target call chain usually contain TraceId; therefore, it can be obtained according to TraceId and processed in the target call chain During the process of the first service request, the target calls the logs printed by each service module in the chain.

Based on the above description, the method for printing a log in the embodiment of the present application further includes:

The log management module acquires the log printed by the service module in the target call chain during the process of processing the first service request by the target call chain.

It should be noted that the log management module obtains the logs printed by each business module in the target call chain to form a complete log of the target call chain. Therefore, under normal circumstances, the logs printed by the business module obtained by the log management module will include the first log. The log printed by the business module and the log printed by the fourth business module. However, there are at least two reasons that may cause that the log printed by the fourth business module is not included in the log printed by the business module in the target call chain.

The first reason is that in the process of processing the first service request by the target call chain, the fourth service module is not called. For example, taking the call chain shown in Figure 2 as an example, if the service module C runs incorrectly, the service module C may directly send a network response to the service module B without sending a network request to the service module D; therefore, the service module D and the service module Module E will not be called, then the logs printed by the business modules in the target call chain obtained by the log management module include the logs printed by business module C, but not the logs printed by business modules D and E.

The second reason is that in the process of processing the first service request by the target call chain, the fourth service module does not run in error and the received network response does not contain an error identifier. For example, taking the call chain shown in FIG. 2 as an example, the service module D does not run in error, and the network response received from the service module E does not contain an error identifier, then the service module D does not print the log; however, the service module C receives After receiving the network response from the service module D, there is an error, then the service module C will print a log. Finally, the log printed by the business module in the target call chain obtained by the log management module is the log printed by the business module C, but does not include the log printed by the business module D.

Based on the fact that the log printed by the business module in the target call chain does not include the log printed by the fourth business module, the log management module obtains the log printed by the fourth business module in the process of processing the second business request by the target call chain, and the fourth business module is in The log printed in the process of processing the second service request by the target call chain indicates that there is no service module with an operating error in the target call chain during the process of processing the second service request by the target call chain, and is used to process the first service on the target call chain The requested process is analyzed.

Based on the foregoing description, it can be seen that there are various reasons that the log printed by the business module in the target call chain does not include the log printed by the fourth business module. Whether it is the first reason above or the second reason above, it is not the fourth reason. The business module caused the wrong business module to appear in the target call chain. If the log printed by the fourth service module when there is a service module with an error in the target call chain is used to analyze the process of the target call chain processing the first service request, it may be mistaken for the target call chain to process the first service During the request process, the fourth service module runs incorrectly.

Therefore, the embodiment of the present application uses the log printed by the fourth service module in the process of processing the second service request by the target call chain to analyze the process of processing the first service request by the target call chain, so as to avoid affecting the processing of the second service request by the target call chain. The analysis result of the process of a business request.

It can be understood that, among all the service requests of the specific type of service requests processed by the target call chain, there are multiple service requests in the process of being processed, and there is no business module that runs in error in the target call chain.

However, in order to improve the target call chain, the business modules in the target call chain are usually adjusted, for example, the functions of the business modules in the target call chain can be improved. Based on this, in the process of processing different business requests in the target call chain, since the business module has changed, even if there is no business module with an error in the target call chain, the logs printed by the business module may be different. Therefore, if the log printed by the business module in the process of processing one service request of the target call chain is used to analyze the process of processing another service request by the target call chain, the analysis result may be affected.

Therefore, in order to avoid as much as possible the obtained log printed by the fourth service module in the process of processing the second service request by the target call chain, and affecting the analysis result of the first service module on the process of processing the first service request by the target call chain, in In another embodiment of the method for printing a log provided by the embodiment of the present application, among all the service requests of the specific type of service requests processed by the target call chain, the request time of the second service request is earlier than and closest to the first service request request time.

Taking the call chain shown in FIG. 2 as an example, it is assumed that the service module A successively receives three service requests from the client, namely service request M, service request N, and service request K; During the process, there is no business module running wrong in the call chain, but in the process of processing the business request K, there is a business module running wrong in the call chain.

If the logs obtained by the log management module that are printed during the process of processing the business request K of the call chain do not include the log printed by the business module D, the log management module will select the log printed by the business module D during the process of processing the business request N of the call chain. The log of the call chain processing service request K is analyzed, and the log printed by the business module D during the process of the call chain processing the service request M is not selected, and the process of the call chain processing the service request K is analyzed.

In this embodiment of the present application, among all service requests of a specific type of service requests processed by the target call chain, the request time of the second service request is earlier than and closest to the request time of the first service request, so that the log management module obtains the The correct log is closer to the correct log printed by the fourth business module in the process of processing the first business request by the target call chain, which makes the analysis of the process of the target call chain processing the first business request more accurate and avoids the selection of the log management module. The difference between the correct log and the correct log printed by the fourth service module in the process of processing the first service request by the target call chain is large, which affects the analysis of the process of processing the first service request by the target call chain.

Based on the foregoing description, the first service module in the embodiment of the present application is different from the existing service module. The first service module in the embodiment of the present application is not only used for processing received network requests, but also for controlling the printing of logs. During the process of controlling the printing of the log, the first service module may perform at least one of the following operations.

For example, the first service module in the embodiment of the present application prints a log when the first network response carries an error identifier or the first service module runs in error. For the specific process, please refer to the relevant descriptions in the foregoing embodiments.

For example, the first service module in the embodiment of the present application is controlled within a preset first period, and in the case that the first service module has a service module with an operating error in the target call chain, the number of logs printed is less than the first preset period. Set quantity. For the specific control process, please refer to the relevant descriptions in the foregoing embodiments.

For example, the first service module in the embodiment of the present application does not print a log when the first network response does not contain an error identifier and the first service module does not run with errors.

For example, the first service module in the embodiment of the present application prints a log when the first network response does not contain an error identifier and the first service module does not run in error, and controls it within a preset second period, and the first When the business module does not have a business module with an operating error in the target call chain, the number of logs printed by the first business module is less than the second preset number. For the specific control process, please refer to the relevant descriptions in the foregoing embodiments.

In order to enable the first service module to perform at least one of the above operations, exemplarily, as shown in FIG. 6 , a tracer unit may be integrated in the first service module shown in FIG. The Tracer unit is integrated in the first service module shown in FIG. 5 ; the Tracer unit is responsible for performing at least one of the above operations, so as to realize the control of log printing.

Similar to the first business module, other business modules in the target call chain are also integrating the above-mentioned Tracer unit, which will not be described in detail.

In order to better understand the method for printing logs provided by the embodiments of the present application, a specific application example of FIG. 3 is provided below. This application example includes two scenarios.

The first scenario:

In the first step, the third service module sends the first network request, and the first service module receives the first network request.

The parameters included in the first network request are as follows: WTraceRemains=4, RTraceRemains=1, WrongFlag=fasle, Times=1577084066659, Response=200, TraceId=eac290b095464ae5b4ebc754266a015a.

Among them, WTraceRemains=4 means that the number of remaining error logs is 4, RTraceRemains=1 means that the number of remaining correct logs is 1, WrongFlag=fasle means that there is no business module with running errors in the call chain, Times=1577084066659 means that business module A receives The time of the network request is 1577084066659, and Response=200 means that the network response identifier value is 200, which specifically indicates that the current status of the network request received by the service module A is successful, and eac290b095464ae5b4ebc754266a015a is the TraceId of the network request received by the service module A.

In the second step, the first service module saves the data in the first network request to the memory, but does not print the entry log first.

Specifically, the first module saves WTraceRemains=4, WrongFlag=fasle, Times=1577084066659, Response=200 and TraceId=eac290b095464ae5b4ebc754266a015a to the memory.

In the third step, the first service module processes the first network request through internal operation.

In the fourth step, after the internal operation, in order to invoke the second service module, the first service module sends a second network request to the second service module.

Specifically, since WrongFlag=fasle indicates that the first network request does not contain an error identifier, if the first service module does not run in error, the second network request contains WTraceRemains=4, WrongFlag=fasle, Times=1577084066659, Response=200, TraceId=eac290b095464ae5b4ebc754266a015a; if the first service module runs incorrectly, the second network request contains WTraceRemains=4, WrongFlag=true, Times=1577084066659, Response=200, TraceId=eac290b095464ae5b4ebc754266a015a, where WrongFlag=true indicates that there is an error in the call chain business module.

After receiving the second network request, the second service module processes the second network request, and then sends the first network response to the first service module.

In the fifth step, the first service module receives the first network response from the second service module.

In one case, the first network response includes WTraceRemains=4, WrongFlag=fasle, Times=1577084066659, Response=200, and TraceId=eac290b095464ae5b4ebc754266a015a. In another case, the first network response includes WTraceRemains=4, WrongFlag=true, Times=1577084066659, Response=200, and TraceId=eac290b095464ae5b4ebc754266a015a.

In the sixth step, the first service module processes the first network response through internal operation.

Step 7: Based on the operation error of the first service module in the process of processing the first network request, or based on the fact that the first network response from the second service module received by the first service module carries an error identifier, the first service module prints log.

Specifically, if the first service module has an internal operation error, or the first network response contains the parameter WrongFlag=true, it means that the first service module needs to print the log type as error log. At this time, because WTraceRemains=4, it means that the number of error logs that the first service module can print is 4, so the first service module prints the entry log according to the parameters in the saved first network request, and according to the first network response The parameter prints the exit log. After printing the entry log and the exit log, the first service module will clear the parameters in the first network request and the parameters in the second network request from the memory.

In the eighth step, the first service module sends a second network response to the first network request to the third service module.

Specifically, due to the internal operation error of the first service module or the parameter WrongFlag=true contained in the first network response, the second network response contains WTraceRemains=4, WrongFlag=true, Times=1577084066659, Response=200, TraceId=eac290b095464ae5b4ebc754266a015a .

Second scenario:

In the first step, the third service module sends a third network request, and the first service module receives the third network request.

The parameters in the third network request are the same as the parameters in the first network request in the first scenario.

Similarly, the first service module saves the data in the third network request to the memory, but does not print the entry log first; then the first service module processes the third network request through internal operation. After the internal operation, the first business module calls the second business module, and in the calling process of calling the second business module and subsequent business modules, there is no business module with an operating error. In this case, the first service module will receive a third network response from the second service module, and the third network response does not contain an error identifier.

The above-mentioned process is similar to the process in the first scenario. For details, please refer to the description in the first scenario for understanding.

In the second step, the first service module does not print a log based on the fact that the first service module does not have an error in the process of processing the third network request, and the received third network response does not contain an error identifier.

The third network response includes WTraceRemains=4, WrongFlag=fasle, Times=1577084066659, Response=200, and TraceId=eac290b095464ae5b4ebc754266a015a.

In the third step, the first service module sends a network response to the third network request to the third service module.

Specifically, based on the internal operation of the first service module without errors, and the first network response contains the parameter WrongFlag=fasle, the second network response contains WTraceRemains=4, WrongFlag=fasle, Times=1577084066659, Response=200, TraceId =eac290b095464ae5b4ebc754266a015a. Please refer to FIG. 7 , which is a schematic diagram of an embodiment of an apparatus for printing a log provided by an embodiment of the present application. The apparatus includes:

a receiving unit 301, configured to receive a first network request;

The log printing unit 302 is configured to print a log based on an operation error in the process of processing the first network request, or based on the received first network response to the second network request from the second service module that carries an error identifier. The second network request is sent to call the second service module in the process of processing the first network request. The second service module belongs to the target call chain, and the error flag indicates that there is a service module in the target call chain with an operating error.

In an implementation manner, the apparatus further includes: a saving unit 303, configured to save the data in the first network request to a memory; a sending unit, configured to send a second network response to the first network request, the second network response Indicates the result of calling the first service module; the log printing unit is configured to print the entry log according to the data in the saved first network request, and print the exit log according to the data in the second network response.

In an implementation manner, the first network request comes from a third service module, and the third service module belongs to the target call chain; the apparatus further includes a sending unit 304, which is configured to be based on an operation error of the first service module or a carry in the first network response. If there is an error identifier, the second network response carrying the error identifier to the first network request is sent to the third service module, so that the third service module prints a log.

In an implementation manner, the receiving unit 301 is further configured to receive a third network request, and the third network request is used to invoke the first service module; the log printing unit 302 is further configured to process the third network based on the first service module There is no error during the request process, and the received third network response does not contain an error flag, and no log is printed.

In an implementation manner, the receiving unit 301 is further configured to receive a third network request, and the third network request is used to invoke the first service module; the log printing unit 302 is further configured to process the third network based on the first service module There is no operation error in the process of the request, and the received third network response does not contain an error identifier, and the log is printed; the first business module does not operate with an error, the third network response received does not contain an error identifier, and the preset third network response does not contain an error identifier. Within two cycles, the number of logs printed by the first service module is less than the second preset number.

Please refer to FIG. 8 , which is a schematic structural diagram of a server in an embodiment of the present application.

One embodiment of the server in this embodiment of the present application may include one or more processors 401 , a memory 402 , and a communication interface 403 .

The memory 402 may be ephemeral storage or persistent storage. Further, the processor 401 may be configured to communicate with the memory 402 to execute a series of instruction operations in the memory 402 on the control device.

In this embodiment, the processor 401 may execute the steps of the methods in the foregoing embodiments, and details are not described herein again.

Exemplarily, the processor 401 may perform the following steps:

receiving a first network request, where the first network request is used to invoke the first service module;

Print a log based on an error in the process of processing the first network request by the first business module, or based on the fact that the first network response to the second network request received by the first business module from the second business module carries an error identifier, The second network request is sent by the first service module to call the second service module in the process of processing the first network request. The first service module and the second service module belong to the target call chain, and the error flag indicates that there is a running operation in the target call chain. Wrong business module.

In this embodiment of the present application, the division of specific functional modules in the processor 401 may be similar to the division of the functional modules described in FIG. 7 , which is not repeated here.

The embodiments of the present application further provide a chip or a chip system, the chip or chip system includes at least one processor and a communication interface, the communication interface and the at least one processor are interconnected by a line, and the at least one processor is used to run a computer program or instruction to The steps of the methods in the foregoing embodiments are performed, and details are not described herein again.

Wherein, the communication interface in the chip may be an input/output interface, a pin, a circuit, or the like.

The embodiment of the present application also provides a first implementation manner of a chip or a chip system. The chip or chip system described above in the present application further includes at least one memory, and instructions are stored in the at least one memory. The memory may be a storage unit inside the chip, such as a register, a cache, etc., or a storage unit of the chip (eg, a read-only memory, a random access memory, etc.).

Embodiments of the present application also provide a computer storage medium, where the computer storage medium is used for storing computer software instructions used by the above-mentioned server, which includes a program for executing a program designed for the server.

The server may be the device for printing logs as described in the aforementioned FIG. 7 .

Embodiments of the present application also provide a computer program product, where the computer program product includes computer software instructions, and the computer software instructions can be loaded by a processor to implement the processes in the methods shown in the foregoing embodiments.

Please refer to FIG. 9 , which is a schematic diagram of an embodiment of a service system provided by an embodiment of the present application. As shown in FIG. 9 , an embodiment of the present application provides a business system, including a target call chain, and the target call chain includes a first business module 100; the first business module 100 is used to execute the print log in the foregoing embodiments Methods.

In an implementation manner, the target call chain further includes a fourth business module 200, and the business system further includes a log management module 300; the target call chain is used to process a specific type of service request sent by the client, and the specific type of service request includes the first The service request and the second service request; the first network request is received by the first service module 100 in the process of processing the first service request by the target call chain.

The log management module 300 is used to obtain the log printed by the business module in the target call chain in the process of processing the first service request by the target call chain; and the log printed based on the business module in the target call chain does not include the fourth business module 200 The log printed, obtains the log printed by the fourth service module 200 in the process of processing the second service request by the target call chain, so as to analyze the process of processing the first service request by the target call chain, and the fourth service module 200 is in the target call chain. The log printed in the process of processing the second service request indicates that there is no service module with an operating error in the target call chain in the process of processing the second service request by the target call chain.

It should be noted that the function and specific implementation of the log management module 300 can be understood by referring to the relevant description of the log management module 300 in the foregoing embodiments.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Claims

A method for printing a log, the method comprising:

The first service module receives a first network request, and the first network request is used to invoke the first service module;

Based on the operation error of the first service module in the process of processing the first network request, or based on the fact that the first network response received by the first service module from the second service module carries an error identifier, the first network response A service module prints a log, wherein the first network response is to a second network request, and the second network request is a process of invoking a second service in the process of processing the first network request by the first service module The first service module and the second service module belong to the target call chain, and the error identifier indicates that there is a service module with an operation error in the target call chain.
The method according to claim 1, wherein, in a preset first period, the first service module prints less logs than the first service module when there is a service module with an operation error in the target call chain. Preset quantity.
The method according to claim 1 or 2, wherein after the first service module receives the first network request, the method further comprises:

The first service module saves the data in the first network request to the memory;

sending, by the first service module, a second network response to the first network request, the second network response indicating a result of calling the first service module;

The first business module print log includes:

The first service module prints an entry log according to the stored data in the first network request;

The first service module prints an exit log according to the data in the second network response.
The method according to claim 3, wherein the first network request comes from a third service module, and the third service module belongs to the target call chain;

The second network response sent by the first service module to the first network request includes:

Based on an error in the operation of the first service module or the error identifier is carried in the first network response, the first service module sends to the third service module a request for the first network that carries the error identifier. The second network response of the error identification causes the third service module to print a log.
The method according to any one of claims 1 to 4, wherein the method further comprises:

the first service module receives a third network request, where the third network request is used to invoke the first service module;

Based on the fact that the first service module does not have an error in the process of processing the third network request, and the received third network response does not contain the error identifier, the first service module does not print a log.
The method according to any one of claims 1 to 4, wherein the method further comprises:

the first service module receives a third network request, where the third network request is used to invoke the first service module;

Based on the fact that within the preset second period, the first service module does not have an error in processing the third network request, and the received third network response does not contain the error identifier, the The number of logs printed by the first business module is less than the second preset number, and the first business module prints the logs.
The method according to any one of claims 1 to 6, wherein the target call chain belongs to a target service system and is used to process a specific type of service request sent by a client, and the target service system further includes a log a management module, the specific type of service request includes a first service request and a second service request, and the target call chain further includes a fourth service module;

The first network request is received by the first service module in the process of processing the first service request by the target call chain;

The method for requesting a specific type of service further includes:

The log management module acquires the log printed by the service module in the target call chain in the process of processing the first service request by the target call chain;

Based on the fact that the log printed by the business module in the target call chain does not include the log printed by the fourth business module, the log management module obtains that the fourth business module processes the second business request in the target call chain The log printed in the process of processing the first service request by the target call chain is to analyze the process of processing the first service request by the target call chain, and the log printed by the fourth service module in the process of processing the second service request by the target call chain indicates that In the process of processing the second service request by the target invocation chain, there is no service module in the target invocation chain that runs in error.
The method according to claim 7, wherein among all the service requests of the specific type of service requests processed by the target call chain, the request time of the second service request is earlier than and closest to the The request time of the first service request.
A device for printing logs, characterized in that the device comprises:

a receiving unit, configured to receive the first network request;

A log printing unit, configured to print based on an operation error in the process of processing the first network request, or based on the received first network response to the second network request from the second service module that carries an error identifier, printing log, the second network request is sent to call the second service module in the process of processing the first network request, the second service module belongs to the target call chain, and the error flag indicates the target call chain There is a business module that is running incorrectly in .
The device according to claim 9, wherein, in a preset first period, in the case that there is a business module with an operation error in the target call chain, the number of logs printed by the first service module is less than the number of logs printed by the first service module. Preset quantity.
The device according to claim 9 or 10, wherein the device further comprises:

a saving unit, configured to save the data in the first network request to a memory;

a sending unit, configured to send a second network response to the first network request, where the second network response indicates a result of calling the first service module;

The log printing unit is configured to print an entry log according to the stored data in the first network request, and print an exit log according to the data in the second network response.
The apparatus according to claim 11, wherein the first network request comes from a third service module, and the third service module belongs to the target call chain;

The sending unit is further configured to send, to the third service module, based on the operation error of the first service module or an error identifier carried in the first network response, for the first network request carrying the The second network response of the erroneous identification causes the third service module to print a log.
A server, characterized in that it includes: at least one processor and a memory, the memory stores computer-executable instructions that can be executed on the processor, and when the computer-executable instructions are executed by the processor, the server executes an instruction such as The method of any of the preceding claims 1-8.
A computer-readable storage medium storing one or more computer-executable instructions, characterized in that, when the computer-executable instructions are executed by a processor, the processor executes the method described in any one of the preceding claims 1-8. method described.
A business system, characterized in that it includes a target invocation chain, and the target invocation chain includes a first business module;

The first service module is configured to execute the method according to any one of the preceding claims 1-8.
The business system according to claim 15, wherein the target call chain further includes a fourth business module, and the business system further includes a log management module;

The target call chain is used to process a specific type of service request sent by the client, and the specific type of service request includes a first service request and a second service request;

The first network request is received by the first service module in the process of processing the first service request by the target call chain;

The log management module is configured to acquire the log printed by the service module in the target call chain in the process of processing the first service request by the target call chain;

And based on that the log printed by the business module in the target call chain does not include the log printed by the fourth business module, obtain the log printed by the fourth business module in the process of processing the second business request in the target call chain , to analyze the process of processing the first service request by the target call chain, and the log indication printed by the fourth service module in the process of processing the second service request by the target call chain is processed in the target call chain. During the process of the second service request, there is no service module with an operating error in the target call chain.
The service system according to claim 15, wherein among all service requests of the specific type of service requests processed by the target call chain, the request time of the second service request is earlier than and closest to all service requests. Describe the request time of the first service request.