WO2018233170A1

WO2018233170A1 - Method, device, computer device, and storage medium for recording a log

Info

Publication number: WO2018233170A1
Application number: PCT/CN2017/108061
Authority: WO
Inventors: 陈杰; 吴海波; 姜云鹏; 凌剑; 马向东; 丁杰
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-06-23
Filing date: 2017-10-27
Publication date: 2018-12-27
Also published as: CN107678908B; CN107678908A

Abstract

A method for recording a log comprises: obtaining function identifiers corresponding to function modules running in a server (202); extracting, according to the function identifiers, a historical log record corresponding to each of the function modules (204); performing calculation, according to the historical log record corresponding to each of the function modules, on historical error information corresponding to each of the function modules (206); determining, according to the historical error information, a log level corresponding to each of the function modules, the log level representing the level of detail of a log record (208); and correspondingly recording a log according to the log level corresponding to each of the function modules (210).

Description

Log recording method, device, computer device and storage medium

This application claims the priority of the Chinese Patent Application filed on June 23, 2017, the Chinese Patent Application No. 2017104889969, entitled "Logging Method, Apparatus, Computer Equipment, and Storage Medium", the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of computer processing, and in particular, to a log recording method, apparatus, computer device, and storage medium.

Background technique

Logging plays an important role both in the development phase and in the testing phase. One of the most important functions is to locate the problem by logging when an exception occurs. The traditional log record uses the same log record granularity regardless of the state of the function modules in the server. The traditional log records are often granular in granularity, resulting in the need to consume a large amount of resources for large log records.

Summary of the invention

According to various embodiments of the present application, a log recording method, apparatus, computer device, and storage medium are provided.

A logging method comprising:

Obtaining the function identifier corresponding to the function module running in the server;

Extracting a history log record corresponding to each function module according to the function identifier;

And collecting historical error information corresponding to each function module according to historical log records corresponding to each function module;

Determining a log level corresponding to each function module according to the historical error information, and the log level reflects the fineness of the log record;

Corresponding log records are performed according to the log level corresponding to each function module.

A logging device comprising:

An identifier obtaining module, configured to acquire a function identifier corresponding to a function module running in the server;

An extraction module, configured to extract, according to the function identifier, a historical log record corresponding to each function module;

a statistics module, configured to collect historical error information corresponding to each function module according to historical log records corresponding to each function module;

a determining module, configured to determine, according to the historical error information, a log level corresponding to each function module, where the log level reflects the fineness of the log record;

The recording module is configured to perform corresponding log records according to the log level corresponding to each function module.

A computer apparatus comprising a memory and a processor, the memory storing computer readable instructions, the computer readable instructions being executed by the processor such that the processor performs the following steps:

One or more non-transitory readable storage mediums storing computer readable instructions, when executed by one or more processors, cause the one or more processors to perform the steps of: acquiring The function identifier corresponding to the function module running in the server;

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features, objects, and advantages of the invention will be apparent from the description and appended claims.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a schematic diagram showing the internal structure of a computer device in an embodiment;

2 is a flow chart of a logging method in an embodiment;

3 is a flow chart of a logging method in another embodiment;

4 is a flow chart of a log recording method in still another embodiment;

FIG. 5 is a flowchart of a method for performing corresponding log recording according to a log level corresponding to each functional module in an embodiment; FIG.

Figure 6 is a block diagram showing the structure of a log recording apparatus in an embodiment;

Figure 7 is a block diagram showing the structure of a log recording apparatus in another embodiment;

Figure 8 is a block diagram showing the structure of a log recording apparatus in still another embodiment.

Detailed ways

In order to make the objects, technical solutions and advantages of the present application more clear, the following The present application will be further described in detail. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

FIG. 1 is a schematic diagram of an internal structure of a computer device in an embodiment, and the computer device may be a server. Referring to Figure 1, the computer device includes a processor, a non-volatile storage medium, an internal memory, and a network interface connected by a system bus. Wherein, the non-volatile storage medium of the computer device can store an operating system and computer readable instructions that, when executed, cause the processor to perform a logging method. The processor of the computer device is used to provide computing and control capabilities to support the operation of the entire computer device. The internal memory can store computer readable instructions that, when executed by the processor, cause the processor to perform a logging method. The network interface of the computer device is used for network communication. It will be understood by those skilled in the art that the structure shown in FIG. 1 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied. The specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.

As shown in FIG. 2, in one embodiment, a logging method is proposed, the method comprising:

Step 202: Acquire a function identifier corresponding to a function module running in the server.

In this embodiment, a function module refers to a program for implementing a certain functional task. The function module may be abnormal during operation. In order to troubleshoot the cause of the abnormality, it is necessary to log in advance when the function module is running. The log record is used to record the running status of the function module. For example, the record runs. Errors, warnings, etc., to facilitate subsequent troubleshooting based on the log records. A server can often run multiple function modules. Log records correspond to function modules. Each function module corresponds to a corresponding log record program. The function identifier is used to uniquely identify a function module. By obtaining the function identifier corresponding to the function module running in the server, it is convenient to find the corresponding historical log record according to the function identifier.

Step 204: Acquire a historical log record corresponding to each function module according to the function identifier.

In this embodiment, the historical log record refers to the record of the operation of the previous function module, and the log record information includes the error information that has appeared, and the error message can be further classified into a fatal error. Serious errors and common errors, of course, will also include some warning information and general information as well as various configuration information. Each function module corresponds to a log record. In order to facilitate log query, the function identifier of the function module is associated with the corresponding log record in advance, so that the history log record corresponding to the corresponding function module can be obtained according to the function identifier.

Step 206: Record historical error information corresponding to each functional module according to historical log records corresponding to each functional module.

In this embodiment, the history log records the previous operation of the function module, including the error information that has appeared before. The historical error information that occurred before the function module is counted by obtaining the history record corresponding to the function module. The statistical history error information is used to know the pros and cons of the function module, and the pros and cons are used to evaluate the probability of a problem with the function module. In one embodiment, since the historical log record for a long time has little effect on evaluating the pros and cons of the current functional module, it is possible to obtain only the historical log records of the most recent period (for example, nearly three months), that is, You only need to obtain historical log records in the preset time period, and then count the number of error messages in the historical log records during the preset time period. In order to more accurately evaluate the pros and cons of the functional modules based on historical error information, in one embodiment, the errors are first classified according to the severity of the error, and then the number of errors corresponding to each type of error is counted. For example, the types of errors are classified into fatal errors, severe errors, and common errors according to their severity, and then the number of occurrences of each type of error is counted separately.

Step 208: Determine a log level corresponding to each function module according to the historical error information, and the log level reflects the fineness of the log record.

In this embodiment, because the advantages and disadvantages of different functional modules are different, in order to save resource consumption, the corresponding log level may be determined according to the advantages and disadvantages of the functional modules. The log level reflects the fineness of the log record. The higher the level, the finer the corresponding log record, and the more resources are consumed. The lower the level, the coarser the granularity of the corresponding log record, and the less resources are consumed. If the function module is better, it means that the function module has few problems, so only need to record less logs, that is, the corresponding log level can be set to a lower level; if the function module is relatively poor, the function module runs. The probability of the problem is relatively large, and the corresponding need to record more detailed The log, that is, the log level, needs to be used at a higher level to facilitate subsequent problem location. In fact, most of the functional modules in the server are in a stable state, and the probability of failure is small, and only a small amount of log information needs to be recorded. Therefore, resource consumption can be greatly reduced by performing targeted logging according to functional modules.

Specifically, judging the pros and cons of the function module by obtaining the historical error information corresponding to the function module, if the error information appearing in the history log record is relatively small, the performance of the function module is relatively good, and if the error information is relatively large, then the description is The performance of this function module is relatively poor and prone to problems. In an embodiment, the correspondence between the historical error information and the log level may be directly set. The more the historical error information, the higher the corresponding log level. In another embodiment, the goodness of the function module may be first calculated according to the preset calculation rule according to the historical error information, and then the corresponding log level is determined according to the calculated goodness.

Step 210: Perform corresponding log records according to the log level corresponding to each function module.

In this embodiment, the log records are classified in advance, and the level of detail of the log records corresponding to different levels is different. The higher the log level, the more detailed the logs to be recorded, and the lower the log level, the coarser the recorded logs. The level of logging is top-down compatible, and high-level logging is compatible with low-level logging. For example, the log level is divided into 10 levels. The first level corresponds to closing all log information; the second level corresponds to only recording fatal error information; the third level corresponds to recording serious errors and fatal error messages; The level corresponds to record common error, severe error and fatal error information; the fifth level corresponds to record warning information, normal error, serious error and fatal error information; and so on, until the 10th level records all information. That is, high-level logging is compatible with all low-level logging, the higher the level, the finer the recording. Specifically, the log level is divided according to the fineness of the record in advance, and the log recording rule corresponding to each level is set. For example, the highest level of the logging rule is to record all the information, and the lowest level of the logging rule is to not record any information. After the log level corresponding to each function module is determined, the corresponding log record can be performed according to the log record rule corresponding to the log level. By determining the corresponding log level according to the advantages and disadvantages of the function module, it is beneficial to save resource consumption, and at the same time, to ensure the subsequent positioning of the problem.

The foregoing log recording method determines the pros and cons of the corresponding function module according to the historical error information appearing in the historical log record corresponding to the function module. If the historical error record corresponding to the historical log record of the function module is less, the function module is relatively good. Low-level log records can be used, which greatly reduces the amount of log records. If there are many historical error messages in the function module, it indicates that the function module is more prone to problems, so high-level log records are required, and high-level log records are Refers to the recording of more detailed log records for subsequent location of the problem. In fact, most of the functional modules in the server are in a good stable state, and the probability of occurrence of problems is very small. Only a small amount of log information needs to be recorded, so the method of hierarchical recording according to the advantages and disadvantages of the functional modules can be greatly reduced. LF.

As shown in FIG. 3, in one embodiment, another logging method is proposed, the method comprising:

Step 302: Acquire a function identifier corresponding to a function module running in the server.

Step 304: Obtain a history log record corresponding to each function module according to the function identifier.

Step 306: Record historical error information corresponding to each functional module according to historical log records corresponding to each functional module.

Step 307: Acquire a running time corresponding to each function module.

Step 308: Determine a log level corresponding to each function module according to historical error information and a running time length corresponding to each function module, and the log level reflects the fineness of the log record. The higher the level, the finer the log record.

Step 310: Perform corresponding log records according to the log level corresponding to each function module.

In this embodiment, in order to better determine the log level corresponding to the function module, in addition to statistical error information to determine the pros and cons of the function module, it is also necessary to obtain the running time of the function module, where the running time refers to The total running time, the longer the running time, the higher the corresponding stability. According to the historical error information and runtime of the function module, the probability of the problem of the function module can be better determined. If the probability of the function module is small, then the log level can be set to a lower level. If there is a problem with the function module. The probability is large, so you can set it to a higher log level. When the general function is just online (that is, the running time is short), you need to refine the log. Set the logging level to the highest level. After the function has stabilized (after a long period of operation), set the log to a lower level, such as logging only fatal error messages.

In this embodiment, the goodness and stability of the functional module are evaluated by acquiring error information and running time in the historical log record corresponding to the function module. If the function module has high degree of goodness and stability, the probability of a problem with the function module is very low. Only a small amount of logs need to be recorded. If the function module has poor performance and stability, then it needs to be recorded. Detailed log. Specifically, the weights corresponding to the goodness and the stability, and the respective corresponding scoring standards may be set in advance, and then the scores of the functional modules corresponding to the function modules are calculated, and the corresponding log ranks are determined according to the scores, and then The determined log level is recorded accordingly. By evaluating the probability of a problem with the function module by double-cribing the function module, the corresponding log level is determined, which can better save resource consumption and not affect the subsequent positioning of the problem.

As shown in FIG. 4, in an embodiment, before the step of acquiring the function identifier corresponding to the function module included in the server, the method further includes:

Step 200: Detect the type of the operating environment in which the server is currently located.

In this embodiment, the running environment of the server is different, and the corresponding log level dividing rules may be different. Therefore, the log level dividing rules corresponding to each environment are separately set according to different operating environments. The operating environment of the server can be divided into a development environment, a test environment, and a production environment. Different environment types have different standards for log level division. Therefore, before obtaining the function identifier corresponding to the function module included in the server, the type of the running environment where the server is currently located is first detected. It is convenient to determine the corresponding log classification rules according to the type of environment. There are various ways to detect the current operating environment of the server. For example, different servers can be pre-configured to be responsible for different tasks. It is assumed that the A server is responsible for the corresponding test, the B server is responsible for the corresponding production, and the C server is responsible for the corresponding development. Then, according to the identifier of the extracted server, the environment type of the server can be directly determined. For example, if the extracted server identifier is the identifier of the A server, the corresponding environment type is the test environment. The server ID is used to uniquely identify a server.

Step 202: Determine a log level division rule corresponding to the running environment type according to the running environment type.

In this embodiment, the rules for dividing the log levels determined by different environment types are different, and the correspondence between the environment types and the log level dividing rules is set in advance. After determining the running environment type of the server, the environment type and the log may be used according to the environment type and the log. The correspondence between the hierarchical rules determines the corresponding log ranking rules. For example, if it is a production environment, it can be divided into 10 levels. If it is a test environment, it can be divided into seven levels of trace|debug|info|warn|error|fatal|none, where the level from trace to none is getting more and more low. None means no record, and trace is a full record log. When the error message appears in the history log record is high, it indicates that the debugging needs to be refined, and it can be recorded as trace or debug. When the error message that appears in the history log record is low, you can set the level to fatal or none.

In this embodiment, the rules for dividing the classification level of the log are different due to different operating environments of the server. Therefore, the correspondence between the environment type and the log classification rule needs to be set in advance, so that the functional modules can be correspondingly targeted. The log records are more conducive to saving resources while ensuring the normal operation of the function modules.

In an embodiment, the step of counting the historical error information corresponding to each function module according to the historical log record corresponding to each function module comprises: counting each error type and corresponding error according to the historical log record corresponding to each function module. The number of information; determining the log level corresponding to each function module according to the error information corresponding to each function module, and the step of the log level reflecting the fineness of the log record includes: according to the type of error information corresponding to each function module and the corresponding error information The quantity calculates the log level corresponding to each function module.

In the present embodiment, the history error information includes the type of error and the corresponding amount of error information. Error types can be classified into fatal errors, serious errors, and normal errors based on severity. Count the number of each error type, calculate the goodness of the function module according to the error type corresponding to the function module and the corresponding error information quantity, you can set the total score in advance, and then set the weight of different error types, according to the weight and the corresponding error information. The product of the quantity is then multiplied by the total score of the set and multiplied by the corresponding weight to obtain the corresponding score of the representative goodness. For example, the total score is set to Z, resulting in The number of occurrences of life errors is X1 times, the number of occurrences of serious errors is X2 times, the number of occurrences of common errors is X3 times, the weight of setting fatal errors is A, the weight of serious errors is B, and the weight of ordinary errors is C, then corresponding The degree of goodness = Z-(A*X1+B*X2+C*X3), where the weight A>B>C. Then, according to the calculated goodness, the corresponding log level is determined, and the correspondence between the goodness and the log level is set in advance, and the higher the degree of goodness, the lower the corresponding log level.

As shown in FIG. 5, in one embodiment, the step of performing corresponding log records according to the log level corresponding to each function module includes:

Step 210A: Determine a log record rule corresponding to each function module according to a correspondence between a preset log level and a log record rule.

Step 210B: Perform corresponding log records according to the log record rule corresponding to each function module.

In this embodiment, the log records are hierarchically divided according to the fineness of the log record, and the log record rules corresponding to each level after the division are set, and the log record rule specifies the granularity of the corresponding log record, for example, If the highest level of logging rule is to record all information, the lowest level of logging rules is to not record any information. After the log level corresponding to each function module is determined, the corresponding log record can be performed according to the log record rule corresponding to the log level. By determining the corresponding log level according to the advantages and disadvantages of the function module, and corresponding log recording, it is beneficial to save resource consumption, and at the same time, can ensure the subsequent positioning of the problem. In one embodiment, the logs of different error types are separately recorded and stored during the log recording, so that the subsequent quick search according to the error type is facilitated.

As shown in FIG. 6, in one embodiment, a logging device is proposed, the device comprising:

The identifier obtaining module 602 is configured to obtain a function identifier corresponding to the function module running in the server;

The extracting module 604 is configured to extract, according to the function identifier, a historical log record corresponding to each function module;

The statistics module 606 is configured to collect statistics according to historical log records corresponding to each function module. Historical error information corresponding to the function modules;

The determining module 608 is configured to determine, according to the historical error information, a log level corresponding to each function module, where the log level reflects the fineness of the log record;

The recording module 610 is configured to perform corresponding log records according to a log level corresponding to each function module.

As shown in FIG. 7, in an embodiment, the foregoing logging device further includes:

The time length obtaining module 607 is configured to obtain a running time corresponding to each function module;

The determining module 608 is further configured to determine a log level corresponding to each function module according to historical error information and a running time length corresponding to each function module, where the log level reflects the fineness of the log record, and the higher the level, the more the log record fine.

As shown in FIG. 8, in one embodiment, the foregoing logging device further includes:

The detecting module 600 is configured to detect a type of the operating environment in which the server is currently located;

The rule determining module 601 is configured to determine a log level dividing rule corresponding to the running environment type according to the running environment type.

In an embodiment, the statistic module 606 is further configured to count each error type and corresponding error information according to the historical log records corresponding to each function module; the determining module 608 is further configured to use each function module. The corresponding error information type and the corresponding number of error information are used to calculate the log level corresponding to each function module. The log level reflects the fineness of the log record. The higher the level, the finer the log record.

In an embodiment, the recording module 610 is further configured to determine a log record rule corresponding to each function module according to a preset correspondence between a log level and a log record rule, and perform a corresponding log according to a log record rule corresponding to each function module. recording.

Each of the above-described logging devices can be implemented in whole or in part by software, hardware, and combinations thereof. The network interface may be an Ethernet card or a wireless network card. The above modules may be embedded in the hardware in the processor or in the memory in the server, or may be stored in the memory in the server, so that the processor calls the corresponding operations of the above modules. The processor can be a central processing unit (CPU,), a microprocessor, a microcontroller, or the like.

The above logging device can be implemented in the form of a computer readable instruction that can be executed on a computer device as shown in FIG.

The embodiment of the present application provides a computer device. The internal structure of the computer device may correspond to the structure shown in FIG. 1. That is, the computer device may be a server or a terminal, and includes a series of computers stored in the memory. The readable instructions, when the computer readable instructions are executed by the processor, may implement the method of logging as set forth in various embodiments of the present application. In one embodiment, a computer device includes a memory, a processor, and computer readable instructions stored on the memory and operative on the processor, the processor implementing the computer readable instructions to implement the following steps Obtaining a function identifier corresponding to the function module running in the server; extracting a history log record corresponding to each function module according to the function identifier; and collecting a history corresponding to each function module according to the historical log record corresponding to each function module The error information is determined according to the historical error information, and the log level corresponding to each function module is determined, and the log level reflects the fineness of the log record; corresponding log records are performed according to the log level corresponding to each function module.

In an embodiment, when the processor executes the computer readable instructions, the method further includes: acquiring a running time corresponding to each functional module; and determining, by the processor, the determining according to the historical error information The log level corresponding to each function module, the step of reflecting the fineness of the log record includes: determining the log level corresponding to each function module according to the historical error information and the running time corresponding to each function module, and the log level is reflected The granularity of the log record, the higher the level, the finer the log record.

In an embodiment, before the acquiring the function identifier corresponding to the function module included in the server, the processor is further configured to: perform: detecting a type of the running environment where the server is currently located; according to the type of the operating environment Determining a log level division rule corresponding to the type of the running environment.

In an embodiment, the step of, according to the history log record corresponding to each function module, the historical error information corresponding to each function module is performed by the processor, including: according to the history log corresponding to each function module Recording each type of error and the corresponding number of error information; determining, by the processor, each function according to error information corresponding to each function module The log level corresponding to the module, the log level reflecting the fineness of the log record includes: calculating the log level corresponding to each function module according to the type of the error information corresponding to each function module and the corresponding number of error information, and the log level reflects The granularity of logging, the higher the level, the finer the logging.

In an embodiment, the step of performing corresponding log recording according to the log level corresponding to each function module performed by the processor includes: determining, according to a preset correspondence between a log level and a log record rule, a corresponding function module Logging rules; corresponding log records according to the logging rules corresponding to each functional module.

In one embodiment, a computer readable storage medium is provided having stored thereon computer readable instructions that, when executed by a processor, implement the steps of: obtaining a function identifier corresponding to a function module running in a server; The function identifier extracts a history log record corresponding to each function module; and records historical error information corresponding to each function module according to the history log corresponding to each function module; and determines each function module according to the historical error information. Corresponding log level, the log level reflects the fineness of the log record; the corresponding log record is performed according to the log level corresponding to each function module.

In an embodiment, the processor performs a calendar according to each function module. The step of recording, by the history log, the historical error information corresponding to each function module comprises: counting each error type and the corresponding amount of error information according to the historical log record corresponding to each function module; The error information corresponding to each function module determines a log level corresponding to each function module, and the step of the log level reflecting the fineness of the log record includes: calculating according to the type of error information corresponding to each function module and the corresponding number of error information The log level corresponding to each function module, the log level reflects the fineness of the log record. The higher the level, the finer the log record.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the computer program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The foregoing storage medium may be a non-volatile storage medium such as a magnetic disk or an optical disk.

The technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be considered as the scope of this manual.

The above-mentioned embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims

A logging method comprising:

Obtaining the function identifier corresponding to the function module running in the server;

Extracting a history log record corresponding to each function module according to the function identifier;

And collecting historical error information corresponding to each function module according to historical log records corresponding to each function module;

Determining a log level corresponding to each function module according to the historical error information, and the log level reflects the fineness of the log record;

Corresponding log records are performed according to the log level corresponding to each function module.
The method of claim 1 further comprising:

Obtain the running time corresponding to each function module;

Determining, according to the historical error information, a log level corresponding to each function module, where the log level reflects the fineness of the log record, including:

The log level corresponding to each function module is determined according to the historical error information and the running time corresponding to each function module, and the log level reflects the fineness of the log record. The higher the level, the finer the log record.
The method according to claim 1, wherein the obtaining the function identifier corresponding to the function module included in the server further comprises:

Detect the type of operating environment the server is currently in;

Determining a log level division rule corresponding to the running environment type according to the running environment type.
The method according to claim 1, wherein the historical error information corresponding to each function module according to the historical log record corresponding to each function module comprises:

Counting each type of error and the corresponding amount of error information according to historical log records corresponding to each function module;

Determining, according to the error information corresponding to each function module, a log level corresponding to each function module, where the log level reflects the fineness of the log record includes:

The log level corresponding to each function module is calculated according to the type of error information corresponding to each function module and the corresponding number of error information. The log level reflects the fineness of the log record. The higher the level, the finer the log record.
The method according to claim 1, wherein the corresponding log record according to a log level corresponding to each function module comprises:

Determining, according to a preset correspondence between a log level and a log record rule, a log record rule corresponding to each function module;

Corresponding logging is performed according to the logging rules corresponding to each function module.
A logging device comprising:

An identifier obtaining module, configured to acquire a function identifier corresponding to a function module running in the server;

An extraction module, configured to extract, according to the function identifier, a historical log record corresponding to each function module;

a statistics module, configured to collect historical error information corresponding to each function module according to historical log records corresponding to each function module;

a determining module, configured to determine, according to the historical error information, a log level corresponding to each function module, where the log level reflects the fineness of the log record;

The recording module is configured to perform corresponding log records according to the log level corresponding to each function module.
The device according to claim 6, wherein the device further comprises:

The time acquisition module is configured to obtain a running time corresponding to each function module;

The determining module is further configured to determine a log level corresponding to each function module according to historical error information and a running time length corresponding to each function module, where the log level reflects the fineness of the log record, and the higher the level, the finer the log record .
The device according to claim 6, wherein the device further comprises:

a detection module, configured to detect a type of running environment in which the server is currently located;

The rule determining module is configured to determine a log level dividing rule corresponding to the running environment type according to the running environment type.
The device according to claim 6, wherein the statistics module is further configured to count, according to the historical log records corresponding to each function module, each error type and a corresponding amount of error information;

The determining module is further configured to calculate a log level corresponding to each function module according to the type of the error information corresponding to each function module and the corresponding number of error information, and the log level reflects the fineness of the log record, and the higher the level, the more the log record fine.
The device according to claim 6, wherein the recording module is further configured to determine, according to a preset correspondence between a log level and a log record rule, a log record rule corresponding to each function module, corresponding to each function module. The logging rules are logged accordingly.
A computer apparatus comprising a memory and a processor, the memory storing computer readable instructions, the computer readable instructions being executed by the processor such that the processor performs the following steps:

Obtaining the function identifier corresponding to the function module running in the server;

Extracting a history log record corresponding to each function module according to the function identifier;

And collecting historical error information corresponding to each function module according to historical log records corresponding to each function module;

Determining a log level corresponding to each function module according to the historical error information, and the log level reflects the fineness of the log record;

Corresponding log records are performed according to the log level corresponding to each function module.
The computer device according to claim 11, wherein the processor is further configured to perform the following steps:

Obtain the running time corresponding to each function module;

Determining, according to the historical error information, a log level corresponding to each function module, where the log level reflects the fineness of the log record, including:

Determining a log level corresponding to each function module according to the historical error information and the running time corresponding to each function module, and the log level reflects the fineness of the log record, and the higher the level, the log record The more detailed the record.
The computer device according to claim 11, wherein the processor is further configured to perform the following steps before performing the function identifier corresponding to the function module included in the acquiring server:

Detect the type of operating environment the server is currently in;

Determining a log level division rule corresponding to the running environment type according to the running environment type.
The computer device according to claim 11, wherein the historical error information corresponding to each function module according to the history log record corresponding to each function module comprises:

Counting each type of error and the corresponding amount of error information according to historical log records corresponding to each function module;

Determining, according to the error information corresponding to each function module, a log level corresponding to each function module, where the log level reflects the fineness of the log record includes:

The log level corresponding to each function module is calculated according to the type of error information corresponding to each function module and the corresponding number of error information. The log level reflects the fineness of the log record. The higher the level, the finer the log record.
The computer device according to claim 11, wherein the corresponding log record according to a log level corresponding to each function module comprises:

Determining, according to a preset correspondence between a log level and a log record rule, a log record rule corresponding to each function module;

Corresponding logging is performed according to the logging rules corresponding to each function module.
One or more non-transitory readable storage mediums storing computer readable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:

Obtaining the function identifier corresponding to the function module running in the server;

Extracting a history log record corresponding to each function module according to the function identifier;

And collecting historical error information corresponding to each function module according to historical log records corresponding to each function module;

Determining a log level corresponding to each function module according to the historical error information, and the log level reflects the fineness of the log record;

Corresponding log records are performed according to the log level corresponding to each function module.
The storage medium according to claim 16, wherein the processor is further configured to perform the following steps:

Obtain the running time corresponding to each function module;

Determining, according to the historical error information, a log level corresponding to each function module, where the log level reflects the fineness of the log record, including:

The log level corresponding to each function module is determined according to the historical error information and the running time corresponding to each function module, and the log level reflects the fineness of the log record. The higher the level, the finer the log record.
The storage medium according to claim 16, wherein the processor further comprises: before executing the function identifier corresponding to the function module included in the acquiring server:

Detect the type of operating environment the server is currently in;

Determining a log level division rule corresponding to the running environment type according to the running environment type.
The storage medium according to claim 16, wherein the historical error information corresponding to each function module according to the history log record corresponding to each function module comprises:

Counting each type of error and the corresponding amount of error information according to historical log records corresponding to each function module;

Determining, according to the error information corresponding to each function module, a log level corresponding to each function module, where the log level reflects the fineness of the log record includes:

Calculate the log level corresponding to each function module according to the type of error information corresponding to each function module and the corresponding number of error information. The log level reflects the fineness of the log record, and the higher the level, The finer the logging.
The storage medium according to claim 16, wherein the performing the corresponding log record according to the log level corresponding to each function module comprises:

Determining, according to a preset correspondence between a log level and a log record rule, a log record rule corresponding to each function module;

Corresponding logging is performed according to the logging rules corresponding to each function module.