WO2020010702A1

WO2020010702A1 - Log search method and system, computer device, and storage medium

Info

Publication number: WO2020010702A1
Application number: PCT/CN2018/106687
Authority: WO
Inventors: 杨天鹏; 金龙; 郝振亚; 汪昌帅
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-07-11
Filing date: 2018-09-20
Publication date: 2020-01-16
Also published as: CN109033280A

Abstract

The present application relates to the technical field of log data processing, and in particular to a log search method and system, a computer device, and a storage medium. The log search method comprises: intercepting and obtaining request information at a server back-end; generating a unique identifier by calling a UUID generator preset at the server back-end; and storing the request information and the unique identifier in a log recording MDC tool. A log frame is preset at the server back-end, log information outputted by the log frame is intercepted, and the log information is split and stored. A search interface is preset on a page of a server front-end, and the log information is displayed in the form of a list. A log collection scheme based on an MDC technology in the present application can greatly reduce search problems of logs and improve search efficiency of an error log.

Description

Log search method, system, computer equipment and storage medium

This application claims priority from a Chinese patent application filed with the Chinese Patent Office on July 11, 2018, with an application number of 201810756846.6 and an invention name of "Log Search Method, System, 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 technical field of log data processing, and in particular, to a log search method, system, computer device, and storage medium.

Background technique

The log file is a log event record of network equipment, systems, and service programs that are generated during operation. Each line of the log contains descriptions of related operations such as date, time, user, and action. A variety of log files are designed in various operating systems, such as application logs, security logs, system logs, Scheduler service logs, FTP logs, WWW logs, DNS server logs, and so on. When users perform some operations on the system, these log files usually record some related content of our operations, which are very useful for system security staff. For example, if the user performs an IPC probe on the system, the system will quickly record the IP, time, user name, etc. used by the probe in the security log. After the FTP probe, the IP and time will be recorded in the FTP log. , Username used for detection, etc. The log data in the log file is of great value for network security. Developers can make various judgments and analysis based on the error log in the log data.

However, when a certain project is getting bigger and larger, and the project has more and more cluster nodes, if some unknown problems occur in the entire online system, developers need to find the error log in the log file of each device, and The error log is not continuous. It may be necessary to repeatedly find the error log for a problem, the efficiency of solving the problem is relatively low, and the operation is tedious.

Summary of the invention

In view of this, it is necessary to provide a log search method, a system, a computer device, and a storage medium for the records of the error log that are not continuous and for the same problem to find tedious problems.

A log search method includes the following steps:

The client request is intercepted at the server backend, the request information in the client request is obtained, and a unique identifier corresponding to the client request is generated by calling a unique identifier UUID generator preset on the server backend, and the The request information and the unique identifier are stored in a log record MDC tool;

A log frame is preset in the server backend, the log frame contains configuration information including request time, request information, and unique identifier, and the request information and unique identifier in the MDC tool are assigned to the log The request information and unique identification in the frame;

Intercepting the log information output by the log framework, splitting the log information into request time, request information, unique identification and log content, and calling an application programming interface API to store the split log information;

A search interface is preset on the server front-end page, and a search condition field is set on the search interface. The search condition field contains at least one field information corresponding to the request information. When a search request is received that includes the field information, After that, the stored log information is searched, and the log information corresponding to the field information is displayed in a list form on the search interface.

A log search system includes the following units:

The client request interception unit is configured to intercept the client request at the server backend, obtain the request information in the client request, and generate the client request by calling a unique identification code UUID generator preset on the server backend. The corresponding unique identifier, and storing the request information and the unique identifier in a log record MDC tool;

The preset log frame unit is configured to preset a log frame on the back end of the server, the log frame contains configuration information including a request time, request information, and unique identifier, and the request information in the MDC tool And a unique identifier assigned to the request information and the unique identifier in the log frame;

The storage log information unit is configured to intercept the log information output by the log framework, split the log information into a request time, request information, unique identifier and log content, and call an application programming interface API to split the log information. Log information for storage;

The search unit is configured to preset a search interface on a server front-end page, and a search condition field is set on the search interface, and the search condition field contains at least one piece of field information corresponding to the request information. After the field information search request, the stored log information is searched, and the log information corresponding to the field information is displayed in a list form on the search interface.

A computer device includes a memory and a processor. The memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processor causes the processor to perform the following steps:

Intercept the log information output by the log framework, split the log information into a request time, the request information, the unique identifier and the log content, and call an application programming interface API to perform the split log information storage;

A storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the following steps:

The above log search method, device, computer equipment, and storage medium include intercepting a client request at the server backend, obtaining the request information in the client request, and generating a client request by calling a unique identification code UUID generator preset on the server backend The corresponding unique identifier stores the request information and the unique identifier in the log record MDC tool. The server backend presets a log frame. The log frame contains configuration information including the request time, the request information, and the unique identifier. Request information and unique identifier are assigned to the request information and unique identifier in the logging framework; intercept the log information output by the logging framework, split the log information into request time, request information, unique identifier, and log content, and call the application programming interface API The split log information is stored; a search interface is preset on the server front-end page, and a search condition field is set on the search interface. The search condition field contains at least one piece of field information corresponding to the requested information. After the search request, search the stored day Log information, and display the log information corresponding to the field information in the form of a list on the search interface. This application collects logs based on MDC technology. It collects all logs requested by each client and records the unique identifier. Developers can directly view the logs after searching through the front-end page. This application can greatly reduce log search problems and improve Search efficiency for error logs.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the detailed description of the preferred embodiments below. The drawings are only for the purpose of illustrating preferred embodiments and are not to be considered as limiting the present application.

FIG. 1 is a flowchart of a log search method according to an embodiment of the present application; FIG.

FIG. 2 is a flowchart of step S1 in FIG. 1;

3 is a structural diagram of a log search system according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a module for intercepting a client request unit in FIG. 3.

detailed description

In order to make the purpose, technical solution, and advantages of the present application clearer, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms "a", "an", "the" and "the" may include plural forms. It should be further understood that the word "comprising" used in the specification of the present application refers to the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, elements, components, and / or groups thereof.

FIG. 1 is a flowchart of a log search method according to an embodiment of the present application. As shown in FIG. 1, the log search method includes the following steps:

Step S1, intercepting the client request: intercepting the client request at the server backend, obtaining the request information in the client request, and generating a unique identifier corresponding to the client request by calling a unique identification code UUID generator preset on the server backend, and The request information and unique ID are stored in the logging MDC tool.

The request sent by the client from the browser generally includes URL information, request parameters, request host IP and request information of the client's corresponding project name. The server in this step may be a server of a log processing platform. The above request information is intercepted at the server backend. In order to distinguish client requests, the log processing platform binds a unique identifier to each request. When the unique identifier is generated, a UUID generator preset on the back end of the server is used. UUID is an abbreviation of Universally Unique Identifier. It is a standard for software construction. It is also used by the Open Software Foundation for distributed computing. Part of the environmental field. The purpose is to allow all elements in the distributed system to have unique identification information, without the need to specify the identification information through the central control terminal. In this case, there is no need to consider duplicate names when the database is created problem. Therefore, in this step, a unique identifier corresponding to each client request is generated by the UUID generator to ensure the uniqueness of each request.

The logging MDC tool is a function that is convenient for recording logs in a multi-threaded condition, that is, a multi-threaded method is used to process requests from multiple users. For example, in a web application server, when a user visits a page, the application server creates a new thread to process the request, or reuses an existing thread from the thread pool. During a user's session, there are multiple threads that have processed the user's request. This makes it difficult to distinguish the logs corresponding to different users. It is very troublesome when you need to track the relevant log records of a user in the system. The MDC tool in this step can solve the above problems. The MDC tool can be regarded as a hash table bound to the current thread, and key-value pairs can be added to it. MDC tools contain content that can be accessed by code executing in the same thread. The child thread of the current thread will inherit the contents of the MDC tool in its parent thread. When you need to record logs, you only need to obtain the required information from the MDC tool. The contents of the MDC tool are saved by the program at the appropriate time. For a web application, this data is usually saved at the very beginning of the request being processed. It is ensured that the values stored in the MDC tool between processes under multiple processes have no mutual influence. This step is based on the advantages of the thread log record of the MDC tool. After obtaining the client request, the request information and the unique identifier are stored in the MDC tool for subsequent log frame output log information.

Step S2, presetting the log frame: The log frame is preset on the server backend. The log frame contains configuration information including request time, request information, and unique identifier. The request information and unique identifier in the MDC tool are assigned to the log frame. Request information and unique identification.

The log framework preset in the server includes log frameworks such as log4j or log4j2. Log4j and log4j2 are both open source projects of Apache. By using Log4j or log4j2, you can control the destination of log information delivery, as well as the output format of each log. By defining the level of each log message, you can control the log generation process in more detail. The input destination, output format, level, etc. are all flexibly configured through a configuration file without modifying the application code. Log4j uses the log4j.properties file as the main configuration file, and log4j2 uses log4j2.xml or log4j2.yml or log4j2.json as the main configuration file.

In this step, on the basis of the configuration information of the original log framework, configuration information including the request information and unique identification is added to the configuration file. So far, all output log information requested by the client will be carried with the configuration information in the configuration file. The above attributes, that is, the log information output by the log framework includes request information and a unique identifier.

Step S3: Store log information: intercept the log information output by the log framework, split the log information into request time, request information, unique identifier, and log content, and call the application programming interface API to store the split log information.

In this step, when the preset log framework of the server backend outputs log information, the output log information is intercepted and intercepted and split. The log information is divided into the request time, request information, unique identifier, and log content, and the corresponding call is called. API for storage. If the database is used to store logs, the logs are inserted into the database through SQL scripts. If the search engine Elasticsearch is used for storage, the storage method of Elasticsearch is called for storage, and Elasticsearch storage engine is preferably used for storage, so that subsequent search log information is faster.

Step S4: Search and display log information: a search interface is preset on the server front-end page, and a search condition field is set on the search interface. The search condition field contains at least one field information corresponding to the requested information. After the request, search the stored log information, and display the log information corresponding to the field information in the form of a list on the search interface.

Outputting appropriate log messages in the right place is only the first step in using logs properly. The real role of log records is to help developers quickly locate problems when problems occur. This step provides developers with a search function for log information through a preset search interface. The search interface searches through field information corresponding to at least one request message, so that developers can quickly query all the log information of the request and quickly locate whether there is a problem with the request and where the problem lies. The specific search condition fields include URL address, request time interval, request parameters, request host IP, project name, and unique identifier. The URL address is required and the other search criteria fields are optional.

When searching the stored log information through the search condition field, the search method is selected according to the storage method of step S3. If the database is used to store logs, this step uses a SQL script query to search the database. If the search engine Elasticsearch is used for storage, the query is performed by using Elasticsearch's query expression QueryDSL. Due to the large amount of data in the log information, the query speed stored in the database is slow, which is not conducive to searching. Therefore, the preferred log information is stored in the Elasticsearch search engine, which can quickly search the log data.

When the log information is displayed in the form of a list on the search interface, the specific content is shown in Table 1 below:

Table 1

In this embodiment, the client request is intercepted, the request information and the unique identifier are stored in the MDC tool, the unified log output format is configured, the request information collected in the MDC tool is output, and the output log information is formatted and stored in the log. In storage, the front end provides a search interface, which searches for log information through the search condition field and displays it to developers. The entire log storage and search process can improve the efficiency of developers in handling online errors, reduce the developer's frequent search for logs, and frequent connection lines. On the device.

In one embodiment, as shown in FIG. 2 when intercepting a client request in step S1, the following steps are adopted:

Step S101: intercept and obtain the request information: when the server backend intercepts the client request, it intercepts the client request by calling the filter method of the preset spring program, and obtains the client request including the URL address, the request parameters, and requests the host IP and Request information for the project name corresponding to the client.

The spring program is an open-source design-level framework that solves the problem of loose coupling between the business logic layer and other layers. Spring program is a lightweight Java development framework, that is, Spring program is a layered JavaSE / EE full-stack (one-stop) lightweight open source framework. In this step, a spring program is set in the server backend in advance, and by calling the filter method of the spring program, all URL requests are intercepted and the request information is obtained through the chain processing of the filter.

Step S102, generating a unique identifier: calling a UUID generator to generate a unique identifier.

In order to distinguish each client request, this step uses a UUID generator to generate a unique identifier for each request to distinguish each client request.

In step S103, the request information and the unique identifier are stored: the request information and the unique identifier are stored in the MDC tool by using the MDC.put method.

The MDC tool is set in advance on the server back end, and the unique identifier generated and the obtained request information are stored in the MDC tool. The specific storage method is as follows:

MDC.put ("REQUEST_URL", "URL address");

MDC.put ("REQUEST_UUID", "Unique ID");

MDC.put ("REQUEST_IP", "Request host IP");

MDC.put ("REQUEST_PARAMS", "request parameter");

MDC.put ("APPKEY", "Project name").

In this embodiment, all URL requests are intercepted and the request information is obtained by calling the filter method of the spring program, and a unique identifier is generated for each request by the UUID generator to distinguish each client request, and the request information and The unique identifier is stored for the purpose of obtaining and storing all logs of each client request.

In one embodiment, when the log framework outputs the log information, after the log framework obtains the request information and the unique identifier in the MDC tool according to the configuration information, the log framework outputs the log information including the request time, the request information, and the unique identifier.

When configuring the configuration file of the logging framework, add the following configuration information:

% D {yyyy-MM-dd HH: mm: ss.SSS}-[% thread]%-5level% logger {36}-% msg% n

-% X {REQUEST_UUID}-% X {REQUEST_URL}-% X {REQUEST_IP}-% X {REQUEST_PARA MS}-% X {APPKEY}

The REQUEST_UUID, REQUEST_URL, REQUEST_IP, REQUEST_PARAMS, and APPKEY in the configuration information added in this embodiment are the request information and the unique identifier stored in the MDC tool. All the output log information for each request will bring the above-mentioned types. Attributes.

In one embodiment, intercepting the log information output by the log framework, and splitting the log information into request time, request information, unique identifier and log content includes: intercepting the logs output by the log framework by calling the preset aop method of the spring program Information; the log information is split into request time, request information, unique identifier, and log content by calling the split method of the preset spring program.

The aop method is an important content in a spring program. It defines an entry point for an existing program, and then cuts in different execution contents before and after it. Based on the aop method, it does not destroy the original program logic, so it can be very good for business. Each part of the logic is isolated, so that the coupling between the parts of the business logic is reduced, the program is reusable, and the development efficiency is improved. In this step, the log information output by the logging framework is intercepted by calling the aop method.

What the split method can do is split a string into substrings and return the result as an array of strings. In the configuration file of the logging framework, you can use the "-" interval to separate each attribute in the log information when you configure the rule. Therefore, after the log information is intercepted, the log information can be split directly by calling the split method, and then split into the request time, request information, unique identifier, and log content.

In this embodiment, the log information is intercepted and split by calling the aop method and the split method in the spring program, and the split content is provided for subsequent display of the log information.

In one embodiment, when the application programming interface API is called to store the split log information, the following steps are taken: setting a logging table in the database, setting a split field in the logging table, and the split field including the request Time field, request information field, unique identification field, and log content field. Call the API to execute the SQL script, insert the split log information into the split fields in turn, and complete the storage of the log information.

SQL is the abbreviation of Structured Query Language, which is a database query and programming language. It is used to access data and query, update, and manage relational database systems. It is also the extension of database script files. SQL does not require the user to specify the method of storing data, nor does the user need to know the specific data storage method. Therefore, different database systems with completely different underlying structures can use the same structured query language as the interface for data input and management. The query language statement can be nested, which makes it extremely flexible and powerful. In this embodiment, log information is stored by executing a SQL script.

When this embodiment is applied to a database to store logs, a log record table established is shown in Table 2 below:

Table 2

In one embodiment, when the application programming interface API is called to store the split log information, the following steps are used: The API uses the search engine Elasticsearch, calls Elasticsearch, and stores the split log information in Elasticsearch.

ElasticSearch is a Lucene-based search server. Elasticsearch provides a full-text search engine with distributed multi-user capabilities, based on a RESTful web interface. Elasticsearch is developed in Java and released as an open source under the Apache license. It is a popular enterprise search engine that can achieve real-time search, is stable, reliable, fast, and easy to install and use.

Due to the large amount of log information, the query speed stored in the database is slow, which is not conducive to subsequent searches. This application preferably uses the search engine Elasticsearch to store log information to achieve fast storage and subsequent search functions.

In one embodiment, a log search system is proposed, as shown in FIG. 3, and includes the following units:

The client request interception unit is configured to intercept the client request on the server backend, obtain the request information in the client request, and generate a unique identifier corresponding to the client request by calling the unique identifier UUID generator preset on the server backend. Request information and unique identification are stored in the log record MDC tool;

The preset log frame unit is set to preset a log frame on the server backend. The log frame contains configuration information including request time, request information, and unique identifier. The request information and unique identifier in the MDC tool are assigned to the log frame. Request information and unique identification;

The storage log information unit is configured to intercept the log information output by the log framework, split the log information into request time, request information, unique identifier, and log content, and call the application programming interface API to store the split log information;

The search unit is set to preset a search interface on a server front-end page, and a search condition field is set on the search interface. The search condition field contains at least one field information corresponding to the request information. When a search request containing field information is received, the search is performed. Store the log information, and display the log information corresponding to the field information in the form of a list on the search interface.

In one embodiment, as shown in FIG. 4, the intercepting client request unit includes:

The interception module is configured to intercept the client request by calling the filter method of a preset spring program, and obtain the request information including the URL address, the request parameter, the request host IP and the corresponding project name of the client in the client request;

Generate unique identification module, set to call UUID generator to generate unique identification;

The storage module is configured to store the request information and the unique identifier into the MDC tool by using the MDC.put method.

In one embodiment, the log information unit is further configured to log information obtained from the MDC tool according to the configuration information and the unique identification, and the log frame outputs log information including the request time, the request information and the unique identification.

In one embodiment, the log information storage unit includes: an interception log information module configured to intercept the log information output by the log framework by calling the aop method of a preset spring program; a split log information module configured to call The split method of the spring program is used to split the log information into request time, request information, unique identifier, and log content.

In one embodiment, the log information storage unit further includes: a log record table module configured to set a log record table in a database, and a split field in the log record table. The split field includes a request time field and request information. Field, unique identification field, and log content field; insert the log information module, set to call the API to execute the SQL script, and insert the split log information into the split fields in turn to complete the storage of the log information.

In one embodiment, the log information storage unit further includes a search engine module, and the API is set to use the search engine Elasticsearch, call Elasticsearch, and store the split log information in Elasticsearch.

In one embodiment, a computer device is provided, which includes a memory and a processor. The memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processor is caused to execute the log search method in the foregoing embodiments. Steps.

In one embodiment, a storage medium storing computer-readable instructions is provided. When the computer-readable instructions are executed by one or more processors, the one or more processors are caused to execute the log search method in the foregoing embodiments. Steps. The storage medium may be a non-volatile storage medium.

A person of ordinary skill in the art may understand that all or part of the steps in the various methods of the foregoing embodiments may be implemented by a program instructing related hardware. The program may be stored in a computer-readable storage medium. The storage medium may include: Read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks, etc.

The technical features of the embodiments described above can be arbitrarily combined. In order to simplify the description, all possible combinations of the technical features in the above embodiments have not been described. However, as long as there is no contradiction in the combination of these technical features, It should be considered as the scope described in this specification.

The above-mentioned embodiments only express some exemplary embodiments of the present application, and their descriptions are more specific and detailed, but cannot be understood as a limitation on the scope of the patent of the present application. It should be noted that, for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of this application patent shall be subject to the appended claims.

Claims

A log search method includes:

The client request is intercepted at the server backend, the request information in the client request is obtained, and a unique identifier corresponding to the client request is generated by calling a unique identifier UUID generator preset on the server backend, and the The request information and the unique identifier are stored in a log record MDC tool;

A log frame is preset in the server backend, the log frame contains configuration information including request time, request information, and unique identifier, and the request information and unique identifier in the MDC tool are assigned to the log The request information and unique identification in the frame;

Intercept the log information output by the log framework, split the log information into a request time, the request information, the unique identifier and the log content, and call an application programming interface API to perform the split log information storage;

A search interface is preset on the server front-end page, and a search condition field is set on the search interface, and the search condition field contains at least one field information corresponding to the request information. After that, the stored log information is searched, and the log information corresponding to the field information is displayed in a list form on the search interface.
The log search method according to claim 1, wherein the server intercepts a client request at the server backend, obtains the request information in the client request, and generates by calling a unique identification code UUID preset on the server backend And generating a unique identifier corresponding to the client request, and storing the request information and the unique identifier in a log record MDC tool, including:

Intercepting a client request by calling a filter method of a preset spring program, obtaining request information including a URL address, request parameters, a request host IP, and a project name corresponding to the client in the client request;

Calling the UUID generator to generate the unique identifier;

The request information and the unique identifier are stored in an MDC tool using an MDC.put method.
The log search method according to claim 1, wherein the log framework outputs log information, comprising:

After the log framework obtains the request information and the unique identifier in the MDC tool according to the configuration information, the log framework outputs log information including a request time, the request information, and the unique identifier.
The log search method according to claim 1, wherein the intercepting the log information output by the log framework, and splitting the log information into a request time, the request information, the unique identifier, and a log content comprises: :

Intercept the log information output by the logging framework by calling the aop method of a preset spring program;

The log information is split into a request time, request information, unique identifier, and log content by calling a preset split method of the spring program.
The log search method according to claim 1, wherein said calling an application programming interface API to store said split log information comprises:

Setting a log record table in a database, and setting a split field in the log record table, the split field including a request time field, a request information field, a unique identification field, and a log content field;

Call the API to execute the SQL script, insert the split log information into the split fields in turn, and complete the storage of the log information.
The log search method according to claim 1, wherein said calling an application programming interface API to store said split log information comprises:

The API uses a search engine Elasticsearch, calls the Elasticsearch, and stores the split log information in the Elasticsearch.
A log search system includes:

The client request interception unit is configured to intercept the client request at the server backend, obtain the request information in the client request, and generate the client request by calling a unique identification code UUID generator preset on the server backend. The corresponding unique identifier, and storing the request information and the unique identifier in a log record MDC tool;

The preset log frame unit is configured to preset a log frame on the back end of the server, the log frame contains configuration information including a request time, request information, and unique identifier, and the request information in the MDC tool And a unique identifier assigned to the request information and the unique identifier in the log frame;

The storage log information unit is configured to intercept the log information output by the log framework, split the log information into a request time, request information, unique identifier and log content, and call an application programming interface API to split the log information. Log information for storage;

The search unit is configured to preset a search interface on a server front-end page, and a search condition field is set on the search interface, and the search condition field contains at least one piece of field information corresponding to the request information. After the field information search request, the stored log information is searched, and the log information corresponding to the field information is displayed in a list form on the search interface.
The log search system according to claim 7, wherein the intercepting client request unit comprises:

The intercepting module is configured to intercept a client request by calling a filter method of a preset spring program, and obtain request information including a URL address, a request parameter, a request host IP and a project name corresponding to the client in the client request;

Generating a unique identification module, configured to call the UUID generator to generate the unique identification;

The storage module is configured to store the request information and the unique identifier into an MDC tool using an MDC.put method.
The log search system according to claim 7, wherein the storage log information unit is further configured to obtain, after the log framework obtains the request information and the unique identifier in the MDC tool according to the configuration information, the The log frame output includes request time, the request information, and the uniquely identified log information.
The log search system according to claim 7, wherein the stored log information unit comprises:

The interception log information module is configured to intercept the log information output by the log framework by invoking the preset aop method of the spring program;

The split log information module is configured to split the log information into a request time, request information, unique identifier, and log content by calling a preset split method of the spring program.
The log search system according to claim 7, wherein the stored log information unit further comprises:

Setting a logging table module, configured to set a logging table in a database, and setting a split field in the log table, the split field includes a request time field, a request information field, a unique identification field, and a log content field;

The log information module is configured to call the API to execute a SQL script, and insert the split log information into the split fields in order to complete the storage of the log information.
The log search system according to claim 7, wherein the storage log information unit further comprises a search engine module configured to use the search engine Elasticsearch for the API, call the Elasticsearch, and split the log information Stored in the Elasticsearch.
A computer device includes a memory and a processor. The memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processor causes the processor to perform the following steps:

The client request is intercepted at the server backend, the request information in the client request is obtained, and a unique identifier corresponding to the client request is generated by calling a unique identifier UUID generator preset on the server backend, and the The request information and the unique identifier are stored in a log record MDC tool;

A log frame is preset in the server backend, the log frame contains configuration information including request time, request information, and unique identifier, and the request information and unique identifier in the MDC tool are assigned to the log The request information and unique identification in the frame;

Intercept the log information output by the log framework, split the log information into a request time, the request information, the unique identifier and the log content, and call an application programming interface API to perform the split log information storage;

A search interface is preset on the server front-end page, and a search condition field is set on the search interface. The search condition field contains at least one field information corresponding to the request information. When a search request is received that includes the field information, After that, the stored log information is searched, and the log information corresponding to the field information is displayed in a list form on the search interface.
The computer device according to claim 13, wherein the server intercepts a client request at the server backend, obtains the request information in the client request, and calls a unique identification code UUID generator preset at the server backend Generating a unique identifier corresponding to the client request, and storing the request information and the unique identifier in a logging MDC tool, so that the processor performs the following steps:

Intercepting a client request by calling a filter method of a preset spring program, obtaining request information including a URL address, request parameters in the client request, requesting a host IP and a project name corresponding to the client;

Calling the UUID generator to generate the unique identifier;

The request information and the unique identifier are stored in an MDC tool using an MDC.put method.
The computer device according to claim 13, wherein when the log framework outputs log information, the processor is caused to perform the following steps:

After the log framework obtains the request information and the unique identifier in the MDC tool according to the configuration information, the log framework outputs log information including a request time, the request information, and the unique identifier.
The computer device according to claim 13, wherein when intercepting the log information output by the log framework, splitting the log information into a request time, the request information, the unique identifier, and a log content, such that The processor performs the following steps:

Intercept the log information output by the logging framework by calling the aop method of a preset spring program;

The log information is split into a request time, request information, unique identifier, and log content by calling a preset split method of the spring program.
A storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the following steps:

The client request is intercepted at the server backend, the request information in the client request is obtained, and a unique identifier corresponding to the client request is generated by calling a unique identifier UUID generator preset on the server backend, and the The request information and the unique identifier are stored in a log record MDC tool;

A log frame is preset in the server backend, the log frame contains configuration information including request time, request information, and unique identifier, and the request information and unique identifier in the MDC tool are assigned to the log The request information and unique identification in the frame;

Intercept the log information output by the log framework, split the log information into a request time, the request information, the unique identifier and the log content, and call an application programming interface API to perform the split log information storage;

A search interface is preset on the server front-end page, and a search condition field is set on the search interface. The search condition field contains at least one field information corresponding to the request information. When a search request is received that includes the field information, After that, the stored log information is searched, and the log information corresponding to the field information is displayed in a list form on the search interface.
The storage medium according to claim 17, wherein the server intercepts a client request at the server backend, obtains the request information in the client request, and calls a unique identification code UUID generator preset on the server backend Generating a unique identifier corresponding to the client request, and storing the request information and the unique identifier in a logging MDC tool, so that one or more of the processors perform the following steps:

Intercepting a client request by calling a filter method of a preset spring program, obtaining request information including a URL address, request parameters, a request host IP, and a project name corresponding to the client in the client request;

Calling the UUID generator to generate the unique identifier;

The request information and the unique identifier are stored in an MDC tool using an MDC.put method.
The storage medium according to claim 17, wherein when the log framework outputs log information, one or more of the processors are caused to perform the following steps:

After the log framework obtains the request information and the unique identifier in the MDC tool according to the configuration information, the log framework outputs log information including a request time, the request information, and the unique identifier.
The storage medium according to claim 17, wherein when the log information output by the log framework is intercepted, the log information is split into a request time, the request information, the unique identifier, and a log content such that One or more of the processors perform the following steps:

Intercept the log information output by the logging framework by calling the aop method of a preset spring program;

The log information is split into a request time, request information, unique identifier, and log content by calling a preset split method of the spring program.