WO2019134226A1

WO2019134226A1 - Log collection method, device, terminal apparatus, and storage medium

Info

Publication number: WO2019134226A1
Application number: PCT/CN2018/077223
Authority: WO
Inventors: 戴开云; 林博
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-01-08
Filing date: 2018-02-26
Publication date: 2019-07-11
Also published as: CN108459939A; CN108459939B

Abstract

The present application discloses a log collection method, a device, an apparatus, and a storage medium. The log collection method comprises: receiving an application request message sent by a user, and generating a unique identifier corresponding thereto; adding the unique identifier to the application request message, and forming a request instruction; delivering, during a response handling process to the request instruction, the unique identifier between application systems or databases involved in the response handling process, and writing the same into log information of the application systems or databases; outputting the log information to a log database; and, if execution of the request instruction fails, extracting, according to the unique identifier contained therein, target log information containing the unique identifier from the log database, and outputting the same in accordance with the temporal order of generation. The technical solution of the present application effectively collects log information distributed among different application systems or databases and facilitates fast fault localization for maintenance and operations staff by means of associated log information, thereby improving efficiency of issue location.

Description

Log collecting method, device, terminal device and storage medium

This patent application is based on the Chinese Patent Application No. 201810014123.9 filed on Jan. 08, 2018, entitled "A Log Collection Method, Apparatus, Terminal Equipment, and Storage Medium", and requires priority.

Technical field

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

Background technique

In the existing multi-system problem location process, it mainly relies on the professional skills of the operation and maintenance personnel and the problem of familiarity with the system, resulting in a long period of problem location and low efficiency of problem location, especially for context-dependent relationships. When the problem is located, because the systems are independent of each other during the problem location process, it takes longer to locate the problem and more manpower is invested.

For example, with the complexity and relevance of web applications, the diversification and interactivity of various website functions provide users with a variety of possible browsing paths, and the operation process of users on the website is increasingly complicated. When an application function module or a server system is operated, a log file is generated in the running process, and a description of related operations such as user, time, and action is described in the log file. When a user sends a request, the request is invoked by multiple application function modules or server systems and returns the corresponding result. When the request returns the result of the call failure, the operation and maintenance personnel usually need to locate the fault by looking at the log that processes the request, but since the log files are distributed in different server systems and different storage paths, there is no special for a large number of log files. In the case of associated information, it is difficult to determine valid log information, thereby affecting the efficiency of problem location.

Summary of the invention

The embodiment of the present invention provides a log collection method, device, terminal device, and storage medium, so as to solve the problem that the problem location efficiency is low in the existing multi-system problem location process.

In a first aspect, an embodiment of the present application provides a log collection method, including:

Receiving an application request message sent by the user, and generating a unique identification code corresponding to the application request message;

Adding the unique identification code to the application request message to form a request instruction;

In the process of responding to the request instruction, transmitting the unique identification code in an application system or database through which the response processing process passes, so that the unique identification code is written into the log information of the application system. Or in the database;

Outputting log information including the unique identification code to a log library;

If the request instruction fails to be executed, extracting target log information including the unique identification code from the log library according to the unique identification code included in the request instruction;

The target log information is output in the order in which the target log information is generated.

In a second aspect, the embodiment of the present application provides a log collecting apparatus, including:

An identifier generating module, configured to receive an application request message sent by a user, and generate a unique identifier code corresponding to the application request message;

An identifier adding module, configured to add the unique identifier to the application request message to form a request instruction;

An identifier delivery module, configured to pass the unique identification code in an application system or database through which the response processing process passes during response processing to the request instruction, such that the unique identification code is written into the In the log information of the application system or in the database;

a log collection module, configured to output log information including the unique identification code to a log library;

a log extraction module, configured to extract target log information including the unique identification code from the log library according to the unique identification code included in the request instruction, if the execution of the request instruction fails;

And a log output module, configured to output the target log information according to a generation time sequence of the target log information.

In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer The following steps are implemented when reading the instruction:

In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores computer readable instructions, and when the computer readable instructions are executed by a processor, the following steps are implemented:

In the log collection method, device, terminal device and storage medium provided by the embodiment of the present application, a unique identification code corresponding to an application request message sent by a user is generated, and the unique identification code is in a response processing process of the request instruction. The passed in the application system or the database, so that the unique identification code is recorded in the log information generated by the entire response process, and the log information is output to the log library to implement log information distributed in different application systems or databases. Forming a valid collection, when the request instruction fails to execute, the target log information generated by the request instruction in the response processing process can be obtained from the log library according to the unique identification code, and the target log information is arranged and outputted in the order of generation time. Forming a log chain, so that the log information generated by the request instruction in the response process is completely concatenated, so that the request invoking process between multiple application systems is clear and transparent, thereby facilitating the relevant operation and maintenance personnel to be able to according to the target log information. Context diagnosis included in the request Instruction execution cause of the failure, for quick and accurate positioning, and effectively improve the efficiency locate the problem.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments of the present application 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 based on these drawings without the inventive labor.

1 is a flowchart of a log collection method provided in Embodiment 1 of the present application;

2 is a flowchart of an implementation of step S3 in the log collection method provided in Embodiment 1 of the present application;

3 is a flowchart of an implementation of step S32 in the log collection method provided in Embodiment 1 of the present application;

4 is a flowchart of implementing output of key log information in the log collection method provided in Embodiment 1 of the present application;

5 is a schematic diagram of a log collection device provided in Embodiment 2 of the present application;

FIG. 6 is a schematic diagram of a terminal device provided in Embodiment 4 of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Example 1

Please refer to FIG. 1. FIG. 1 shows an implementation process of a log collection method provided by an embodiment of the present application. The log collection method is applied to the log collection system of each enterprise, and the log association generated by the request instruction in the process of the application system or the database response process is aggregated to improve the efficiency of problem location. As shown in FIG. 1, the log collection method includes steps S1 to S6, which are detailed as follows:

S1: Receive an application request message sent by the user, and generate a unique identification code corresponding to the application request message.

In the embodiment of the present application, the unique identifier is used to identify the uniqueness of the application request message. Specifically, after the client sends the application request message, the log collection system generates a corresponding unique identifier according to the application request message sent by the user. (Universally Unique Identifiers, UUIDs), that is, different application identification messages whose corresponding unique identification codes are different from each other, for example, a random sequence is used to generate a unique identification code, and the random sequence is unique. Preferably, according to the current date, the application request message The receiving time, the machine device number and the like are combined to generate the random sequence, and specifically, the data such as the Ethernet card address, the nanosecond time, the identification code of the host chip, and the random number may be used, or the user may customize according to the need, so that the The unique identifier is globally unique.

S2: Add a unique identification code to the application request message to form a request instruction.

In the embodiment of the present application, the unique identification code generated in step S1 is added to the application request message according to a preset format to form a request instruction.

It should be noted that the preset format may be a preset field of adding a unique identifier to the header of the request message or adding a unique identifier to the preset field of the message content, which may be set according to the needs of the application. There are no restrictions here.

S3: In the process of responding to the request instruction, the unique identification code is transmitted in the application system or database through which the response process passes, so that the unique identification code is written into the log information of the application system or in the database.

In the embodiment of the present application, in the response processing process of the request instruction formed in step S2, the application function module in multiple different application systems or accessing data in multiple different databases is often invoked according to the needs of the actual application. In the execution process of each application function module or the data processing process of the database, the unique identification code is first extracted from the input message, and the unique identification code is written into the log information generated by the current application system, or stored in the current database. Then, after the processing of the current application system or the current database is completed, the unique identification code is delivered to the next application system or database.

For example, after the request instruction is formed through step S2, the current application system that receives the application request message records the unique identification code and the content of the application request message in the local log, and the request instruction is sent to the next application service system. When processing, the application service system service extracts the unique identification code and the application request message from the request instruction according to a preset format after receiving the incoming request instruction, and is in the process of responding to the application request message. , the unique identification code is recorded into the generated log information.

The unique identification code can be added to each of the log information generated by the response processing request instruction process and each of the passed databases by passing the unique identification code in each application system or each database through which the response process passes.

S4: Output log information including the unique identification code to the log library.

In the embodiment of the present application, according to the unique identification code in the log information, the log information including the unique identification code is output to the specified log library by using the log management tool.

The log library is a log output destination that is set according to the needs of a specific application. Specifically, it may be a specified database or a unified log management server to form an effective collection of log information distributed in different application systems or databases.

Specifically, the log management tool can set the log attributes such as the information contained in the log, the output format of the log, and the destination of the log information delivery.

Preferably, log information collection can be performed by using the log framework Log4j, and the log attribute is set by using the Log4j configuration file. For example, use [%X{uuid1}] in the configuration file to define the log variable uuid1, and configure the output format of the log variable uuid1 to be %X, and output the value of the log variable uuid1 in the output format of %X.

S5: If the execution of the request instruction fails, the target log information including the unique identification code is extracted from the log library according to the unique identification code included in the request instruction.

In the embodiment of the present application, when the application request message sent by the user returns an abnormal situation in which the call fails, that is, the execution of the request instruction fails, the unique identification code corresponding to the application request message is obtained according to the request instruction, according to the request The unique identification code extracts the target log information containing the unique identification code from the log library, so that the relevant personnel can diagnose the reason for the failure of the execution of the request instruction by the content recorded in the target log information.

Specifically, the grep command can be used to match the parameter of the condition option and the unique identifier to search for the log information that meets the requirements in the log repository of the stored log, and print and output the matched log information. For example, by grep obtaining the command: grep 'uuid2'*.log, the *.log file containing the uuid2 is obtained, and the log information corresponding to the uuid2 request command is outputted in response to the response.

S6: Output the target log information according to the generation time of the target log information.

In the embodiment of the present application, for the target log information acquired in step S5, the target log information is arranged according to the generation time sequence of the target log information, a log chain is formed, and the log chain is output to the interaction interface, so that the request instruction is The log information generated by the response process is completely concatenated, so that the relevant operation and maintenance personnel can analyze the reason for the failure of the request instruction according to the context relationship contained in the complete log information, so as to facilitate the rapid and accurate positioning problem.

In the embodiment corresponding to FIG. 1, the unique identification code corresponding to the application request message sent by the user is generated, and the unique identification code is transmitted in the application system or database through which the response processing process of the request instruction passes, so that the unique The identification code is recorded in the log information generated by the entire response processing process, and the log information is output to the log library, so as to effectively collect the log information distributed in different application systems or databases, when the request instruction fails to execute, The target log information generated by the request instruction in the response processing process is obtained from the log library according to the unique identification code, and the target log information is outputted in the order of generation time to form a log chain, so that the request instruction is responded The log information generated during the process is completely concatenated, so that the request invocation process between multiple application systems is clear and transparent, thereby facilitating the relevant operation and maintenance personnel to diagnose the reason for the failure of the request instruction according to the context relationship included in the target log information. For quick and accurate positioning problems Effectively improve the efficiency of problem location.

Next, on the basis of the embodiment corresponding to FIG. 1, the application of the unique identification code in the response processing process in the response processing process to the request instruction mentioned in step S3 is hereinafter described by a specific embodiment. The specific implementation method of passing in the system or database so that the unique identification code is written into the log information of the application system or in the database is described in detail.

Referring to FIG. 2, FIG. 2 shows a specific implementation process of step S3 provided by the embodiment of the present application, which is described in detail as follows:

S31: When the response processing process passes through different application systems, the unique identification code is added to the interaction message between different application systems, so that the unique identification code is delivered through the interaction message.

Specifically, when the response processing process passes through different application systems, the unique identification code is added to the HTTP head request, and is transmitted through a network transmission protocol, so that the unique identification code is written into the application system through which the response processing process passes. In the log information.

S32: The unique identification code is passed in a single thread or a thread pool when the response process passes inside the application system.

In the embodiment of the present application, when the response processing process passes inside the application system, the processing of the request instruction in the application system may be a single-thread processing manner or a thread pool processing manner, and the unique identification code is transmitted in a single thread or a thread pool. The unique identification code is written into the log information of the single thread or the thread pool inside the application system through which the response process passes.

S33: When the response process calls the data table in the database, the unique identification code is recorded in a preset field of the data table.

Specifically, an idle field is selected as a preset field in each data table of the database. If the data table has no free field, a new field is added to the data table as a preset field, and the preset field is used to record the unique identification code. When the response process accesses the data record involved in the data table of the database, the unique identification code is recorded in the preset field of the data record, so that the relevant operation and maintenance personnel can quickly locate the database according to the unique identification code when the problem is located. Get the relevant data table and the data records involved in the data table.

For example, the specific setting method for adding the preset field in the corresponding table of the database is as follows:

ALTER TABLE employee ADD a varchar(20)NOT NULL Default 0;

The statement refers to adding the field a to the table employee. The type of the field a is varchar, the size of the field a is 20 bytes, and the field a is not empty, and the default value is 0.

It should be noted that attributes such as the type and size of the preset field can be set according to the needs of the actual application, and no limitation is imposed here.

In the embodiment of the present application, there is no necessary sequential execution order between step S31, step S32 and step S33, which may be a parallel execution relationship.

In the corresponding embodiment of FIG. 2, the unique identification code is transmitted between different application systems by adding the unique identification code to the interaction message between different application systems, by using the unique identification code in a single thread or a thread pool. Passing, realizing the transfer of the unique identification code inside the application system, and recording the unique identification code in the preset field of the data table of the database, realizing the transfer of the unique identification code in the database, thereby realizing the unique identification code in the request instruction Fully and complete delivery in the application system or database through which the processing process passes, so that when the execution of the request instruction fails, the complete log chain generated by the response instruction in the response process can be obtained from the log library according to the unique identification code. Therefore, the relevant operation and maintenance personnel can perform fast and accurate problem location according to the complete log chain, thereby effectively improving the problem location efficiency.

On the basis of the corresponding embodiment of FIG. 2, the specific identification code is mentioned in step S32, and the specific identification code is transmitted in the single thread or the thread pool when the response processing process passes inside the application system. The implementation method is described in detail.

Referring to FIG. 3, FIG. 3 shows a specific implementation process of step S32 provided by the embodiment of the present application, which is described in detail as follows:

S321: If the response processing process is a single-thread processing manner when passing through the application system, the unique identification code is transmitted to the single thread, and the unique identification code is delivered during the execution of the single thread.

In the embodiment of the present application, if the response processing process is a single-thread processing manner when passing through the application system, the unique identification code is operated by the MDC.put() operation according to the incoming unique identification code when the single thread starts executing. Write to a preset log variable that is pre-set in the log configuration file so that the unique identification code is passed during the execution of the single thread.

For example, the unique identification code uuid2 is written into the log variable mdc_trade_id using MDC.put ("mdc_trade_id", uuid2), where the MDC (Mapped Diagnostic Context) can create a log storage space for each thread.

S322: If the response processing process is the thread pool processing mode inside the application system, obtain the content of the log storage space of each thread before creating the thread pool, and perform a push operation during the process of creating the thread pool, so that the unique The identification code is passed in the thread pool, wherein the push operation is used to add the content of the log storage space of each thread, and the content of the log storage space contains a unique identification code.

In the embodiment of the present application, if the response processing process is the thread pool processing mode when the application system is internal, the content of the log storage space record of each thread is obtained by using the MDC.getContext().clone operation before creating the thread pool. The recorded content includes the value of the unique identifier and other preset log variables, and the MDC.push() operation is performed during the creation of the thread pool, and the value of the log variable of each thread's log storage space record is added to the creation. The execution code of the thread pool is such that the unique identifier is passed during the execution of each thread in the thread pool.

It should be noted that the MDC.getContext() operation is used to obtain the content of the storage space of each thread. In the thread pool, if multiple threads access the same resource at the same time, the thread will compete for resources. Therefore, for the MDC. .getContext() does a clone operation to avoid thread resource contention causing execution errors.

In the embodiment corresponding to FIG. 3, for the single-thread processing mode, the unique identification code is written into the preset log variable by the MDC.put() operation, so that the unique identification code is transmitted in a single thread, and the thread pool is processed. In this way, use the MDC.getContext().clone operation to get the contents of the log storage space of each thread before creating the thread pool, and perform the MDC.push() operation during the process of creating the thread pool, and store the log of each thread. The content of the space is added to the log storage space of the thread pool, and the delivery of the unique identification code in the thread pool is realized, and the delivery of the unique identification code in the single thread and the thread pool provides conditions for obtaining a complete log chain.

On the basis of the embodiment corresponding to FIG. 1, after the log information including the unique identification code is output to the log library in step S4, the log information in the log library may be further managed, as shown in FIG. 4, the log collection is performed. The method also includes:

If the history log information of the log generation time earlier than the preset time exists, the history log information is deleted.

Specifically, because the log collection in the log library is large and the memory space is large, the log files in the log library can be periodically deleted. The log generation time in the log library is determined to be earlier than the preset. The historical log information of the time, if it exists, delete the historical log information.

It should be noted that the preset time can be dynamically adjusted according to the current log file size. When the log file is large, the preset time can be close to the current time, that is, the deleted history log information is relatively increased. When the log file is small, The preset time can be far away from the current time, that is, the deleted history log information is relatively reduced.

Preferably, the log is periodically cleared by setting a timed task, such as using the Crontab command, which is used to set instructions that are periodically executed. The specific setting method includes the following steps (1) to (3), which are specifically described as follows:

(1) Execute the "crontab-e" command;

(2) Write ***/1**/usr/bin/rm/openFalcon/apache-tomcat-7.0.57/bin/*.log-f>/dev/null2>&1 into the corresponding configuration file;

Among them, "***/1**/usr/bin/rm/openFalcon/apache-tomcat-7.0.57/bin/*.log-f>/dev/null2>&1" means to clean up /usr/ every day. Bin/rm/openFalcon/apache-tomcat

a file ending in .log in the -7.0.57/bin/ directory;

(3) Save the configuration file.

In the implementation of the present application, the log data of the log library is generated by periodically deleting the log, and the memory of the log library is released to avoid the memory being occupied by the transition, thereby effectively improving the performance of each application system.

On the basis of the above embodiment, after the target log information is output in the order of the generation of the target log information in step S6, the target log information may be analyzed. As shown in FIG. 4, the log collection method further includes:

S71: Analyze the target log information according to the preset keyword, and confirm the key log information.

In the embodiment of the present application, the target log information obtained in step S6 is analyzed according to a preset keyword, specifically, the preset keyword is searched in the target log information, and the log containing the preset keyword is included. The information is confirmed as critical log information.

The default keyword may be error, warn, not exit, failed, etc., and may be time, IP address, etc., but is not limited thereto, and may be set according to actual application requirements, and is not limited herein.

Further, the key log information obtained according to the keyword includes, but is not limited to, important log content, server IP address, and running time. The important log content contains the user's operation information, current running status, and error information. The operation and maintenance personnel can quickly locate the problem based on the important log content, and timely maintain the abnormal server IP address. At the same time, in the face of complex problems. You can quickly find the corresponding context in the log chain through the running time of key log information to locate the problem.

S72: Output key log information.

Specifically, the output mode of the key log information may be directly marking the key log information in the log chain, and the labeling may be performed by changing the font or color of the key log information, so as to distinguish it from the common log information, so as to achieve Eye-catching effect. The output of the key log information may also be that the key log information is separately output to the interactive interface, or the key log information is sent to the information receiving address of the preset operation and maintenance personnel. The specific information receiving address may be a mailbox or an instant messaging tool. Etc., there is no restriction here, so that the relevant operation and maintenance personnel can deal with the problems in time to avoid causing greater losses.

It should be noted that the network transmission protocol for transmitting key log information may specifically be HyperText Transfer Protocol (HTTP), File Transfer Protocol (FTP), or Simple Mail Transfer Protocol (SMTP). ) and other methods.

In the embodiment corresponding to FIG. 4, the target log information is analyzed by a preset keyword, the key log information is confirmed, and the key log information is output in time, so that the operation and maintenance personnel can perform timely problems according to the key log information. Positioning, so that the abnormal problems can be quickly solved, avoiding greater losses, improving problem location and system maintenance efficiency.

It should be understood that the size of the sequence of the steps in the above embodiments does not mean that the order of execution is performed. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Example 2

Corresponding to the data method in the first embodiment, FIG. 5 is a schematic block diagram of the log collecting device corresponding to the log collecting method shown in the first embodiment. For the convenience of description, only the related to the embodiment of the present application is shown. section.

As shown in FIG. 5, the log collection device includes an identifier generation module 50, an identifier addition module 51, an identifier delivery module 52, a log collection module 53, a log extraction module 54, and a log output module 55. Each function module is described in detail as follows:

The identifier generating module 50 is configured to receive an application request message sent by the user, and generate a unique identifier code corresponding to the application request message.

An identifier adding module 51, configured to add a unique identifier to the application request message to form a request instruction;

The identifier delivery module 52 is configured to pass the unique identification code in the application system or database through which the response processing process passes during the response processing to the request instruction, so that the unique identification code is written into the log information of the application system. Or in the database;

The log collection module 53 is configured to output log information including the unique identification code to the log library.

The log extraction module 54 is configured to: if the request instruction fails to be executed, extract the target log information including the unique identification code from the log library according to the unique identification code included in the request instruction;

The log output module 55 is configured to output target log information according to a generation time sequence of the target log information.

Further, the identity delivery module 52 includes:

The first delivery unit 520 is configured to add a unique identification code to an interaction message between different application systems when the response processing process passes through different application systems, so that the unique identification code is transmitted through the interaction message;

a second delivery unit 521, configured to: when the response processing process passes inside the application system, pass the unique identification code in a single thread or a thread pool;

The third transmitting unit 522 is configured to record the unique identification code in a preset field of the data table when the data table in the database is invoked in response to the processing procedure.

Further, the second delivery unit 521 includes:

The single-threaded delivery sub-unit 5210 is configured to: when the response processing process passes through the application system, is a single-thread processing manner, then pass the unique identification code to the single thread, and deliver the unique identification code in the single-thread execution process;

The thread pool delivery sub-unit 5211 is configured to obtain the content of the log storage space of each thread before the thread pool is created, and the thread pool processing process is performed during the process of processing the thread pool. The push operation causes the unique identification code to be passed in the thread pool, wherein the push operation is used to add the contents of the log storage space of each thread, and the content of the log storage space contains the unique identification code.

Further, the log collection device further includes:

The log deletion module 56 is configured to delete the historical log information if there is historical log information in the log library that is earlier than the preset time.

Further, the log collection device further includes:

The log analysis module 57 is configured to analyze the target log information according to the preset keyword, and confirm the key log information;

The key log output module 58 is configured to output key log information.

The process of implementing the respective functions of each module in the log collection device provided in this embodiment is specifically described in the foregoing method, and is not described here.

Example 3

The embodiment provides a computer readable storage medium, where the computer readable storage medium is stored with the computer readable instructions, and the computer readable instructions are executed by the processor to implement the log collection method in Embodiment 1. Let me repeat. Alternatively, when the computer readable instructions are executed by the processor, the functions of the modules/units in the log collection device in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.

It will be understood that the computer readable storage medium may include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard drive, a magnetic disk, an optical disk, a computer memory, a read only memory ( ROM, Read-Only Memory), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.

Example 4

FIG. 6 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 6, the terminal device 6 of this embodiment includes a processor 60, a memory 61, and computer readable instructions 62 stored in the memory 61 and operable on the processor 60. The processor 60, when executing the computer readable instructions 62, implements the steps in the various log collection method embodiments described above, such as steps S1 through S6 shown in FIG. Alternatively, processor 60, when executing computer readable instructions 62, implements the functions of the various modules/units of the various apparatus embodiments described above, such as the functions of modules 50 through 55 of FIG.

Illustratively, computer readable instructions 62 may be partitioned into one or more modules/units, one or more modules/units being stored in memory 61 and executed by processor 60 to complete the application. The one or more modules/units may be a series of computer readable instruction segments capable of performing a particular function for describing the execution of computer readable instructions 62 in the terminal device 6. For example, the computer readable instructions 62 may be divided into an identifier generation module, an identifier addition module, an identifier delivery module, a log collection module, a log extraction module, and a log output module. The specific functions of each module are as shown in Embodiment 2, in order to avoid duplication. , no longer repeat them here.

The terminal device 6 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The terminal device may include, but is not limited to, the processor 60, the memory 61. It will be understood by those skilled in the art that FIG. 6 is only an example of the terminal device 6, and does not constitute a limitation of the terminal device 6, and may include more or less components than those illustrated, or combine some components or different components. For example, the terminal device may further include an input/output device, a network access device, a bus, and the like.

The so-called processor 60 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or a memory of the terminal device 6. The memory 61 may also be an external storage device of the terminal device 6, such as a plug-in hard disk provided on the terminal device 6, a smart memory card (SMC), a Secure Digital (SD) card, and a flash memory card (Flash). Card) and so on. Further, the memory 61 may also include both an internal storage unit of the terminal device 6 and an external storage device. The memory 61 is used to store computer readable instructions as well as other readable instructions and data required by the terminal device. The memory 61 can also be used to temporarily store data that has been output or is about to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims

A log collection method, the log collection method includes:

Receiving an application request message sent by the user, and generating a unique identification code corresponding to the application request message;

Adding the unique identification code to the application request message to form a request instruction;

In the process of responding to the request instruction, transmitting the unique identification code in an application system or database through which the response processing process passes, so that the unique identification code is written into the log information of the application system. Or in the database;

Outputting log information including the unique identification code to a log library;

If the request instruction fails to be executed, extracting target log information including the unique identification code from the log library according to the unique identification code included in the request instruction;

The target log information is output in the order in which the target log information is generated.
The log collection method according to claim 1, wherein in the response processing to the request instruction, the unique identification code is transmitted in an application system or a database through which the response processing process passes, Having the unique identification code written in the log information of the application system or the database includes:

When the response processing process passes through different application systems, adding the unique identification code to the interaction message between the different application systems, so that the unique identification code is delivered by the interaction message;

Transmitting the unique identification code in a single thread or a thread pool when the response processing process passes inside the application system;

When the response processing procedure calls the data table in the database, the unique identification code is recorded in a preset field of the data table.
The method of claim 2, wherein the transmitting the unique identification code in a single thread or a thread pool when the response processing process passes inside the application system comprises:

And if the response processing process is a single-thread processing manner when the application system is internal, the unique identifier code is transmitted to the single thread, and the unique identifier code is delivered during execution of the single thread;

If the response processing process is internal to the application system, the thread pool processing mode is obtained, and the content of the log storage space of each thread is obtained before the thread pool is created, and a push operation is performed during the processing of the thread pool, so that The unique identification code is passed in the thread pool, wherein the push operation is used to add content of a log storage space of each thread, and the content of the log storage space includes the unique identification code.
The method for collecting logs according to claim 1, wherein after the outputting the target log information including the unique identification code to the log repository, the log collecting method further includes:

If the log log has historical log information whose log generation time is earlier than the preset time, the historical log information is deleted.
The log collection method according to any one of claims 1 to 4, wherein after the outputting the target log information in the order of the generation of the target log information, the log collection method further includes:

The target log information is analyzed according to a preset keyword to confirm key log information;

The key log information is output.
A log collecting device, wherein the log collecting device comprises:

An identifier generating module, configured to receive an application request message sent by a user, and generate a unique identifier code corresponding to the application request message;

An identifier adding module, configured to add the unique identifier to the application request message to form a request instruction;

An identifier delivery module, configured to pass the unique identification code in an application system or database through which the response processing process passes during response processing to the request instruction, such that the unique identification code is written into the In the log information of the application system or in the database;

a log collection module, configured to output log information including the unique identification code to a log library;

a log extraction module, configured to extract target log information including the unique identification code from the log library according to the unique identification code included in the request instruction, if the execution of the request instruction fails;

And a log output module, configured to output the target log information according to a generation time sequence of the target log information.
The log collection device of claim 6, wherein the identification delivery module comprises:

a first delivery unit, configured to add the unique identification code to an interaction message between the different application systems when the response processing process passes through different application systems, so that the unique identification code passes through the Transmitting an interactive message;

a second delivery unit, configured to: when the response processing process passes inside the application system, pass the unique identification code in a single thread or a thread pool;

a third delivery unit, configured to record the unique identification code in a preset field of the data table when the response processing procedure invokes a data table in the database;

The second delivery unit includes:

a single thread transfer subunit, configured to pass the unique identification code to the single thread and execute the single thread in the single thread processing mode if the response processing process passes through the internal application system Passing the unique identification code;

The thread pool transfer subunit is configured to: if the response processing process passes through the application system, the thread pool processing mode, obtain the content of the log storage space of each thread before creating the thread pool, and process the thread pool Pushing in the process, so that the unique identification code is passed in the thread pool, wherein the push operation is used to add content of the log storage space of each thread, and the content of the log storage space includes The unique identification code.
The log collection device of claim 7, wherein the second delivery unit comprises:

a single thread transfer subunit, configured to pass the unique identification code to the single thread and execute the single thread in the single thread processing mode if the response processing process passes through the internal application system Passing the unique identification code;

The thread pool transfer subunit is configured to: if the response processing process passes through the application system, the thread pool processing mode, obtain the content of the log storage space of each thread before creating the thread pool, and process the thread pool Pushing in the process, so that the unique identification code is passed in the thread pool, wherein the push operation is used to add content of the log storage space of each thread, and the content of the log storage space includes The unique identification code.
The log collection device of claim 6, wherein the log collection device further comprises:

The log deletion module is configured to delete historical log information if there is historical log information in the log library that is generated earlier than the preset time.
The log collecting device according to any one of claims 6 to 9, wherein the log collecting device further comprises:

a log deletion module, configured to delete the historical log information if a history log information of a log generation time earlier than a preset time exists in the log repository;

a log analysis module, configured to analyze the target log information according to a preset keyword, and confirm the key log information;

A key log output module for outputting the key log information.
A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, wherein the processor executes the computer readable instructions as follows step:

Receiving an application request message sent by the user, and generating a unique identification code corresponding to the application request message;

Adding the unique identification code to the application request message to form a request instruction;

In the process of responding to the request instruction, transmitting the unique identification code in an application system or database through which the response processing process passes, so that the unique identification code is written into the log information of the application system. Or in the database;

Outputting log information including the unique identification code to a log library;

If the request instruction fails to be executed, extracting target log information including the unique identification code from the log library according to the unique identification code included in the request instruction;

The target log information is output in the order in which the target log information is generated.
The terminal device according to claim 11, wherein in the response processing to the request instruction, the unique identification code is transferred in an application system or a database through which the response processing process passes, so that The unique identification code is written into the log information of the application system or the database includes:

When the response processing process passes through different application systems, adding the unique identification code to the interaction message between the different application systems, so that the unique identification code is delivered by the interaction message;

Transmitting the unique identification code in a single thread or a thread pool when the response processing process passes inside the application system;

When the response processing procedure calls the data table in the database, the unique identification code is recorded in a preset field of the data table.
The terminal device according to claim 12, wherein the transmitting the unique identification code in a single thread or a thread pool when the response processing process passes inside the application system comprises:

And if the response processing process is a single-thread processing manner when the application system is internal, the unique identifier code is transmitted to the single thread, and the unique identifier code is delivered during execution of the single thread;

If the response processing process is internal to the application system, the thread pool processing mode is obtained, and the content of the log storage space of each thread is obtained before the thread pool is created, and a push operation is performed during the processing of the thread pool, so that The unique identification code is passed in the thread pool, wherein the push operation is used to add content of a log storage space of each thread, and the content of the log storage space includes the unique identification code.
The terminal device according to claim 11, wherein after the outputting the target log information including the unique identification code to the log library, the processor further implements the following steps when the computer readable instructions are executed :

If the log log has historical log information whose log generation time is earlier than the preset time, the historical log information is deleted.
The terminal device according to any one of claims 11 to 14, wherein after the outputting the target log information in the order of generation of the target log information, the processor executes the computer readable The instructions also implement the following steps:

The target log information is analyzed according to a preset keyword to confirm key log information;

The key log information is output.
A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by a processor, implement the following steps:

Receiving an application request message sent by the user, and generating a unique identification code corresponding to the application request message;

Adding the unique identification code to the application request message to form a request instruction;

In the process of responding to the request instruction, transmitting the unique identification code in an application system or database through which the response processing process passes, so that the unique identification code is written into the log information of the application system. Or in the database;

Outputting log information including the unique identification code to a log library;

If the request instruction fails to be executed, extracting target log information including the unique identification code from the log library according to the unique identification code included in the request instruction;

The target log information is output in the order in which the target log information is generated.
The computer readable storage medium according to claim 16, wherein said unique identification code is in an application system or database through which said response processing process passes in response processing to said request instruction Passing, such that the unique identification code is written into the log information of the application system or the database includes:

When the response processing process passes through different application systems, adding the unique identification code to the interaction message between the different application systems, so that the unique identification code is delivered by the interaction message;

Transmitting the unique identification code in a single thread or a thread pool when the response processing process passes inside the application system;

When the response processing procedure calls the data table in the database, the unique identification code is recorded in a preset field of the data table.
The computer readable storage medium of claim 17, wherein the transferring the unique identification code in a single thread or a thread pool when the response processing process passes inside the application system comprises:

And if the response processing process is a single-thread processing manner when the application system is internal, the unique identifier code is transmitted to the single thread, and the unique identifier code is delivered during execution of the single thread;

If the response processing process is internal to the application system, the thread pool processing mode is obtained, and the content of the log storage space of each thread is obtained before the thread pool is created, and a push operation is performed during the processing of the thread pool, so that The unique identification code is passed in the thread pool, wherein the push operation is used to add content of a log storage space of each thread, and the content of the log storage space includes the unique identification code.
A computer readable storage medium according to claim 16, wherein said computer readable instructions are further executed by said processor after said target log information including said unique identification code is output to a log library The following steps:

If the log log has historical log information whose log generation time is earlier than the preset time, the historical log information is deleted.
The computer readable storage medium according to any one of claims 16 to 19, wherein said computer readable instruction is after said outputting said target log information in order of generation of said target log information The processor also implements the following steps when executed:

The target log information is analyzed according to a preset keyword to confirm key log information;

The key log information is output.