CN112416876B - Log monitoring method and device for universal interface - Google Patents

Abstract

The present invention discloses a log monitoring method and device of a universal interface, wherein a preset log table template is pre-customized, and the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service. The method includes: upon receiving a log monitoring request for a target system, obtaining log data of the target system in a preset database, wherein the log data includes: basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system through a log monitoring platform; converting the log data into a target preset log table based on the preset log table template; and monitoring the target system based on the target preset log table. In the above process, regardless of the type of monitoring request, the corresponding log data will be converted into a target preset log table, which is reusable and does not require a separate log table to be set.

Description

A log monitoring method and device for a universal interface

Technical Field

The present invention relates to the technical field of enterprise resource planning, and in particular to a log monitoring method and device of a universal interface.

Background Art

Currently, most of the interface logs for external calls in SAP ERP are system-level logs, such as connection information, interruption information, and other purely technical information, which require professional basic environment personnel to understand.

In the implementation of SAP ERP projects, most log records are created for a specific interface, and a separate program is developed for log display or interface retransmission. However, creating different log tables for different interface services will result in too many log tables and make them difficult to maintain and locate. In addition, different log query functions and log tables are customized and difficult to reuse.

Summary of the invention

In view of this, the present invention provides a log monitoring method and device for a universal interface, which is used to solve the problem that in the implementation of SAPERP projects, most log records are created for a specific interface. An interface log table is created and a program is developed separately for log display or interface retransmission. However, creating different log tables for different interface services will result in too many log tables and make it difficult to maintain and locate the analysis, and different log query functions and log tables are customized and developed and difficult to reuse. The specific solution is as follows:

A log monitoring method for a universal interface, pre-customizing a preset log table template, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service, the method includes:

Upon receiving a log monitoring request for a target system, obtaining log data of the target system from a preset database, wherein the log data includes: basic information, technical information, step information, and return parameters/messages of the target system, and the log data is obtained by monitoring the target system through a log monitoring platform;

Converting the log data into a target preset log table based on the preset log table template;

The target system is monitored by monitoring logs based on the target preset log table.

The above method, optionally, obtains the log data of the target system in a preset database, including:

Parsing the log monitoring request to obtain a monitoring identifier in the log monitoring request;

Searching the preset database for log data identical to the monitoring identifier;

The log data identical to the monitoring identifier is used as the log data of the target system.

The above method, optionally, converting the log data into a target preset log table based on the preset log table template includes:

Dividing the log data according to the input parameter, the return parameter/message and the at least one called atomic service to obtain each divided log data;

The divided log data are added to the preset log table template according to their types to obtain a target preset log table.

The above method, optionally, performs monitoring log monitoring on the target system based on the target preset log table, including:

Obtaining the query condition in the log monitoring request;

Searching the target preset log table for a keyword matching the query condition based on the query condition;

Obtain target log data corresponding to the keyword, and display the target log data.

The above method may optionally further include:

When an instruction to cancel the current log data is received, the current log data is cancelled.

A log monitoring device with a universal interface, pre-customizing a preset log table template, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service, the device includes:

An acquisition module, configured to acquire log data of the target system from a preset database upon receiving a log monitoring request for the target system, wherein the log data includes basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system through a log monitoring platform;

A conversion module, used for converting the log data into a target preset log table based on the preset log table template;

A monitoring module is used to monitor the target system's monitoring logs based on the target preset log table.

In the above device, optionally, the acquisition module includes:

An identification acquisition unit, used to parse the log monitoring request and obtain a monitoring identification in the log monitoring request;

A first search unit, configured to search the preset database for log data identical to the monitoring identifier;

The determination unit is used to use the log data identical to the monitoring identifier as the log data of the target system.

In the above device, optionally, the conversion module includes:

A partitioning unit, configured to partition the log data according to the input parameter, the return parameter/message and the at least one called atomic service to obtain respective partitioned log data;

The adding unit is used to add the divided log data to the preset log table template according to its type to obtain a target preset log table.

In the above device, optionally, the monitoring module includes:

A condition acquisition unit, used to acquire the query condition in the log monitoring request;

A first searching unit, configured to search the target preset log table for a keyword matching the query condition based on the query condition;

The acquisition and display unit is used to acquire target log data corresponding to the keyword and display the target log data.

The above device may optionally further include:

The cancellation module is used to cancel the current log data when receiving an instruction to cancel the current log data.

Compared with the prior art, the present invention has the following advantages:

The present invention discloses a log monitoring method and device of a universal interface, wherein a preset log table template is customized in advance, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service, and the method includes: upon receiving a log monitoring request for a target system, obtaining log data of the target system in a preset database, wherein the log data includes: basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system through a log monitoring platform; converting the log data into a target preset log table based on the preset log table template; and monitoring the target system based on the target preset log table. In the above process, regardless of the type of monitoring request, the corresponding log data will be converted into a target preset log table, which is reusable and does not require a separate log table to be set.

Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a flow chart of a log monitoring method for a universal interface disclosed in an embodiment of the present application;

FIG2 is a structural block diagram of a service interface disclosed in an embodiment of the present application;

FIG3 is a structural block diagram of a log monitoring device of a universal interface disclosed in an embodiment of the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

The present invention discloses a log monitoring method and device of a universal interface, which is applied to the monitoring process of the SAP ERP system. For complex business needs, there may be many internal business systems involved, and these systems inevitably need to interact frequently with the ERP system. The results and process monitoring of the interface service operation are extremely important, especially for developers and operation and maintenance personnel to check errors on a daily basis and to count business transaction volumes, which has a multiplier effect. Among them, SAP ERP: ERP software products launched by SAP, including SAP R/3, SAP ECC, SAP S/4HANA, etc. Interface service: The interface service provided to the outside world can be SAP standard BAPI or customer-defined ZBAPI, which is an interface service encapsulated according to certain principles.

In enterprise-level business maintenance and operation scenarios, logs are playing an increasingly important role. Whether a complete log monitoring system is rich in functions and whether the log display is detailed often depends on whether the log records are complete during the execution of the interface service. Log monitoring provides real-time analysis of business log data, visualization of monitoring charts and alarm services. At present, in most SAP implementation projects, there is no unified log monitoring and management platform specifically for the backend service interface. Even if there is, it is too simple and scattered and not well integrated with business data, which is specifically manifested in the following aspects:

(1) Creating different log tables for different interface services will result in too many log tables and make maintenance and location analysis difficult.

(2) Custom development of different log query functions and specific tables that are difficult to reuse

(3) The scope of use is more inclined towards back-end operation and maintenance personnel, so the content of the log focuses on technical information and ignores business data information

(4) Too many transaction codes to maintain and maintenance personnel and business personnel find it difficult to remember, affecting work efficiency

(5) For complex integrated interfaces, it is impossible to accurately track the execution of steps within the call chain

(6) The integrity of the interface transaction is not well considered and exception handling (reversal and compensation) is not possible.

In view of the above problems, a log monitoring method of a universal interface is provided in an embodiment of the present invention to solve the above problems, wherein the universal interface requires developers to encapsulate the interface service in accordance with the unified interface development specification and process when encapsulating the interface, wherein the integrated service framework of the universal interface is in a complete sense, and the core system software hierarchy can be divided into four layers, including the channel layer, the process layer, the integration layer, and the core service layer. Among them, the composite service corresponds to the integration layer, that is, the outermost layer of the product layer, and is the only interface for online transactions with the channel layer.

Furthermore, based on the integrated service interface encapsulation input and output parameter specifications, it is ensured that all integrated service interfaces have unified CONTROL_DATA (public control information) and RETURN (return message).

The internal code hierarchy of the integration service must ensure that all integration services are implemented using SAP ABAP OO object-oriented programming technology. The internal code hierarchy is as follows:

First, an integration service is a SAP Remote Function Module (RFM) in its physical form. Second, the implementation of an integration service is also layered.

(1) Proxy Implementation Layer

The proxy implementation layer implements some common functions, such as serial number judgment and processing, message translation, etc.

(2) Service Implementation Layer

The service implementation layer organizes service adapters to implement functions. In addition, transaction control is implemented in this layer.

(3) Foundation Layer

The integration service framework provides many common programs to implement these functions. These common programs themselves form a layer called the "base layer".

The integration service framework provides a complete set of supporting public programs to simplify and standardize the behavior of the integration service, including: serial number management handle, message handle, exception class and exception message translation handle.

During the development process, these public programs can be directly called. Examples of the public programs are shown in Table 1.

Table 1

In the embodiment of the present invention, the service method implementation of the adapter class is described by taking the method "EXECUTE" as an example. The interface parameters of the method 'EXECUTE' are: in the initial state, there are only CONTROL_DATA and RETURN in the interface. Compare the interface of the integrated service ZCS_DEMO_ADDR_CHG to complete the rest. For example, in this example, the integrated service has 4 internal table interfaces, which can correspond to the internal table transmission interface used to define the adapter class. Implementation of the method 'EXECUTE': Call the atomic BAPI in the forward service implementation method 'EXECUTE' to implement the business function.

Implement the relevant methods in the self-agent implementation class 'ZCL_DEMO_IN_PI_ADDR_CHG' as needed. The relevant methods are shown in Table 2.

Table 2

In the embodiment of the present invention, the 'EXECUTE' method in the class 'ZCL_DEMO_IN_SI_ADDR_CHG' is implemented as needed, and specific business implementation is implemented in this method. In the initial state, the implementation in this method is empty, and the 'EXECUTE' method of the adapter class is directly called in this method. If an integrated service involves calling multiple steps, it can also be called sequentially in the service implementation class

Each step adapter class can record the input parameters of each step before calling. After the call, call the handle class ZCL_FND_TRANSACTION_CONTROL->RECORD_WORK() method to record the call stack of the step. This stack is used when calling the ROLLBACK_WORK() method when problems occur in the execution of subsequent steps. At the same time, call the ZCL_FND_TRANSACTION_CONTROL->COMMIT_WORK() method to commit and save data.

Based on the above-mentioned universal interface, an embodiment of the present invention provides a log monitoring method of a universal interface, pre-customizing a preset log table template, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service. The execution flow of the monitoring method is shown in FIG1, including the steps of:

S101. Upon receiving a log monitoring request for a target system, obtaining log data of the target system from a preset database, wherein the log data includes basic information, technical information, step information, and return parameters/messages of the target system, and the log data is obtained by monitoring the target system through a log monitoring platform;

In the embodiment of the present invention, the log data includes: basic information, technical information, step information and return parameters/messages of the target system, wherein the basic information includes: flow, date, time, service name, operating user, execution result, etc., the technical information includes: interface technology name, caller system, interface external input and return parameters, business initiator, user and affiliated organization, etc., the step information includes: execution step atomic service name, input and return parameters, execution result and other information, the return parameter/message includes: error or success message, etc. The log data is obtained by monitoring the target system by the log monitoring platform, and the log monitoring platform user monitors the target system, wherein the target system can be a specific application or a system composed of multiple applications. In the embodiment of the present invention, the target system is not specifically limited. In the case of receiving a log monitoring request for a target system, the log data of the target system is obtained in a preset database, and the acquisition process is as follows: parsing the log monitoring request, obtaining the monitoring identifier in the log monitoring request; wherein the monitoring identifier is used to distinguish log data of different systems, and in the embodiment of the present invention, the specific existence form of the monitoring identifier is not limited, searching the preset database for log data identical to the monitoring identifier; and using the log data identical to the monitoring identifier as the log data of the target system. wherein the database table names included in the preset database are shown in Table 3.

Table 3

S102, converting the log data into a target preset log table based on the preset log table template;

In an embodiment of the present invention, since the existence forms of different system log data may be different, in order to realize the reuse of different system monitoring processes, a log table template is pre-established in an embodiment of the present invention. The log table template can meet the log monitoring of different systems. The process of converting the log data into a target preset log table based on the preset log table template is as follows: the log data is divided according to the input parameters, the return parameters/messages and the at least one calling atomic service to obtain each divided log data; each divided log data is added to the preset log table template according to its type to obtain the target preset log table.

S103: Perform monitoring log monitoring on the target system based on the target preset log table.

In an embodiment of the present invention, the target system is monitored for logs based on the target preset log table, and query conditions in the log monitoring request are obtained, wherein the query conditions include: date, time, operating user, status, service name, status, etc. Keywords matching the query conditions are searched in the target preset log table based on the query conditions; target log data corresponding to the keywords are obtained, and the target log data are displayed.

The present invention discloses a log monitoring method of a universal interface, pre-customizing a preset log table template, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service, and the method includes: in the case of receiving a log monitoring request for a target system, obtaining the log data of the target system in a preset database, wherein the log data includes: basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system by a log monitoring platform; converting the log data into a target preset log table based on the preset log table template; and monitoring the target system based on the target preset log table. In the above process, regardless of the type of monitoring request, the corresponding log data will be converted into a target preset log table, which is reusable and does not require a separate log table to be set.

In the embodiment of the present invention, the general interface is taken as a service interface as an example to illustrate the above process. The service interface structure diagram is shown in Figure 2. The log monitoring platform monitors the basic information, technical information, step information and parameters/messages of the system in real time, and stores the data in the database after data extraction. First, a set of general log storage tables are designed at the database level, and which log types need to be recorded and stored is configurable. During the called operation process, the interface stores the relevant log information in the corresponding library table according to the configuration to complete the unified management of data of various types of logs. Considering that with the increase in business volume in the future, 12 backup tables are designed for each type of log table according to the month to prepare for subsequent backup data. When the monitoring platform is running, data is extracted from various types of log tables in real time for filtering, processing, analysis and statistics, and then visualized. Integrated service monitoring platform function transaction code: ZCSMON, users can run this function on the portal website or SAP background according to their operating permissions. Enter the query conditions, and you can query the interface execution records by date, time, operation user, status, service name, status and other search conditions alone or in combination. Click the "Start Query" button, and the system will load basic information, step information and return information data from the business flow information table, interface step information table, MESSAGE and other related tables in real time, and use the SAPALV list function to display and store related log information. The monitoring platform integrates an exception handling button. When the user selects a successful flow to offset (offsetting is correction, which is equivalent to the "regret" function provided by SAP, such as a bank transfer, the amount is returned to the remitter's account after correction), the system finds the input and output parameters of this interface according to the forward flow number, and performs dynamic offset according to the pre-configured offset service. Similarly, when performing subsequent compensation business for the service, the interface is re-simulated and executed according to the historical parameter data recorded in the log.

The main improvements of this interface monitoring log method over other traditional log management platforms are:

The enrichment and improvement of the monitoring platform functions are closely linked to the interface encapsulation specifications, which facilitates enterprises to follow the unified service interface development management and constrain development guidelines. A universal interface operation monitoring platform is developed based on the unified specifications during interface encapsulation, which can achieve the following main functions:

Support querying interface execution records by date, time, operation user, status, service name and other search conditions;

Display of organizational structure information: business initiator, user and affiliated unit;

Technical information display: including: service name, calling system, interface input parameters, interface output information, and supports information export function (XML);

Display of execution step information within the interface: For complex integrated interface services, which may integrate multiple ERP systems or non-ERP system atomic services, it can support recording the input and output information and execution results of each step in the order of calling.

Monitoring platform records support automatic refresh;

Error message display: message log-LOG;

Message translation: Because the business meaning of some standard BAPI messages in ERP is not very clear, it supports mapping the original messages into custom converted messages;

The integrated service interface under standardized encapsulation has the following advantages:

Unified external calling method;

Unified flow status control and flow log recording;

Unified transaction control, message processing, and exception handling;

Unified reversal mechanism;

The function of the monitoring platform is not only reflected in "monitoring", it can also be used as a main tool for business personnel to conduct business statistics and operation and maintenance personnel to conduct daily troubleshooting and exception handling.

Based on the above-mentioned log monitoring method of a universal interface, an embodiment of the present invention provides a universal interface log monitoring device, pre-customizing a preset log table template, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service. The structural block diagram of the monitoring device is shown in FIG3, including:

Acquisition module 201 , conversion module 202 and monitoring module 203 .

in,

The acquisition module 201 is used to acquire the log data of the target system from a preset database when receiving a log monitoring request for the target system, wherein the log data includes: basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system by the log monitoring platform;

The conversion module 202 is used to convert the log data into a target preset log table based on the preset log table template;

The monitoring module 203 is used to monitor the target system's monitoring logs based on the target preset log table.

The present invention discloses a log monitoring device with a universal interface, which pre-customizes a preset log table template, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service, and the method includes: upon receiving a log monitoring request for a target system, obtaining log data of the target system in a preset database, wherein the log data includes: basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system through a log monitoring platform; converting the log data into a target preset log table based on the preset log table template; and monitoring the target system based on the target preset log table. In the above process, regardless of the type of monitoring request, the corresponding log data will be converted into a target preset log table, which is reusable and does not require a separate log table to be set.

In the embodiment of the present invention, the acquisition module 201 includes:

An identification obtaining unit 204 , a first searching unit 205 and a determining unit 206 .

in,

The identification acquisition unit 204 is used to parse the log monitoring request and obtain the monitoring identification in the log monitoring request;

The first search unit 205 is used to search the preset database for log data identical to the monitoring identifier;

The determining unit 206 is configured to use the log data identical to the monitoring identifier as the log data of the target system.

In the embodiment of the present invention, the conversion module 202 includes:

A dividing unit 207 and an adding unit 208 .

in,

The division unit 207 is used to divide the log data according to the input parameter, the return parameter/message and the at least one called atomic service to obtain each divided log data;

The adding unit 208 is used to add each of the divided log data to the preset log table template according to its type to obtain a target preset log table.

In the embodiment of the present invention, the monitoring module 203 includes:

A condition acquisition unit 209 , a first search unit 210 and an acquisition and display unit 211 .

in,

The condition acquisition unit 209 is used to acquire the query condition in the log monitoring request;

The first search unit 210 is used to search the target preset log table for keywords matching the query condition based on the query condition;

The acquisition and display unit 211 is used to acquire target log data corresponding to the keyword and display the target log data.

In the embodiment of the present invention, the monitoring device further includes: a cancellation module 212 .

in,

The cancellation module 212 is used to cancel the current log data when receiving an instruction to cancel the current log data.

It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

For the convenience of description, the above device is described as being divided into various units according to their functions. Of course, when implementing the present invention, the functions of each unit can be implemented in the same or multiple software and/or hardware.

It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a storage medium such as ROM/RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present invention or certain parts of the embodiments.

The above is a detailed introduction to the log monitoring method and device of a universal interface provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims (8)

1. A log monitoring method for a universal interface, characterized in that a preset log table template is pre-customized, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service, and the method is implemented based on the universal interface, and the method includes: In the case of receiving a log monitoring request for a target system, obtaining log data of the target system in a preset database, wherein the log data includes: basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system by a log monitoring platform; the log data of the target system includes different types of log data; the step information includes: execution step atomic service name, input and return parameters, and execution result; The log data is converted into a target preset log table based on the preset log table template; the preset log table template satisfies log monitoring of different systems, and the log data is converted into a target preset log table based on the preset log table template, including: dividing the log data according to the input parameter, the return parameter/message and the at least one atomic service call to obtain each divided log data; adding each divided log data to the preset log table template according to its type to obtain the target preset log table; The target system is monitored by monitoring logs based on the target preset log table. 2. The method according to claim 1, characterized in that obtaining the log data of the target system in a preset database comprises: Parsing the log monitoring request to obtain a monitoring identifier in the log monitoring request; Searching the preset database for log data identical to the monitoring identifier; The log data identical to the monitoring identifier is used as the log data of the target system. 3. The method according to claim 1, characterized in that the monitoring log of the target system is monitored based on the target preset log table, comprising: Obtaining the query condition in the log monitoring request; Searching the target preset log table for a keyword matching the query condition based on the query condition; Obtain target log data corresponding to the keyword, and display the target log data. 4. The method according to claim 1, further comprising: When an instruction to cancel the current log data is received, the current log data is cancelled. 5. A log monitoring device of a universal interface, characterized in that a preset log table template is pre-customized, wherein the preset log table template includes: input parameters, return parameters/messages and at least one calling atomic service, and the device is implemented based on the universal interface, and the device includes: The acquisition module is used to acquire the log data of the target system in a preset database when receiving a log monitoring request for the target system, wherein the log data includes: basic information, technical information, step information and return parameters/messages of the target system, and the log data is obtained by monitoring the target system by the log monitoring platform; the log data of the target system includes different types of log data; the step information includes: execution step atomic service name, input and return parameters, and execution result; A conversion module is used to convert the log data into a target preset log table based on the preset log table template; the preset log table template meets the log monitoring of different systems, and the conversion module includes: a division unit, used to divide the log data according to the input parameters, the return parameters/messages and the at least one called atomic service to obtain each divided log data; an adding unit, used to add each divided log data to the preset log table template according to its type to obtain a target preset log table; a monitoring module, used to monitor the target system based on the target preset log table. 6. The device according to claim 5, characterized in that the acquisition module comprises: An identification acquisition unit, used to parse the log monitoring request and obtain a monitoring identification in the log monitoring request; A first search unit, configured to search the preset database for log data identical to the monitoring identifier; The determination unit is used to use the log data identical to the monitoring identifier as the log data of the target system. 7. The device according to claim 5, characterized in that the monitoring module comprises: A condition acquisition unit, used to acquire the query condition in the log monitoring request; A first searching unit, configured to search the target preset log table for a keyword matching the query condition based on the query condition; The acquisition and display unit is used to acquire target log data corresponding to the keyword and display the target log data. 8. The device according to claim 5, further comprising: The cancellation module is used to cancel the current log data when receiving an instruction to cancel the current log data.