CN107347024B

CN107347024B - Method, equipment and system for storing operation log

Info

Publication number: CN107347024B
Application number: CN201710595028.8A
Authority: CN
Inventors: 黄荣华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2017-07-19
Filing date: 2017-07-19
Publication date: 2020-04-28
Anticipated expiration: 2037-07-19
Also published as: CN107347024A

Abstract

The application provides a method and a device for storing an operation log, relates to the IT field, and can solve the problems of long response time of an operation request and low system performance caused by a mode of analyzing and storing the operation log by an operated resource object or a management object. The method comprises the following steps: the method comprises the steps that a first network device receives an operation request sent by user equipment; the first network equipment determines whether the operation request needs to store an operation log; if the first network equipment determines that the operation request needs to store the operation log, the first network equipment sends the operation request to the second network equipment to indicate the second network equipment to store the operation log of the operation request; the first network device sends an operation request to the service processing device. The embodiment of the application is applied to a scene of storing (recording) the operation log.

Description

Method, equipment and system for storing operation log

Technical Field

The present disclosure relates to the field of Information Technology (IT), and in particular, to a method and an apparatus for storing an operation log.

Background

In management software and conventional operation and maintenance software, an operator (e.g., a system administrator, a service administrator, an end User, etc.) may send an operation request to a service system through an operation User Interface (UI), thereby operating a service system resource. All operations can be recorded on case for later review and audit based on system security and traceability, and the records are called operation logs.

Typically, the operation log is stored (logged) by an operated resource object or a management object in the business system. When the operated resource object or the management object receives the operation request, the operation request is firstly analyzed, then the operation log obtained by analysis is stored in a database or a data file, and the operation log can be updated when the operation is finished.

However, such a method of parsing and storing the operation log by the operated resource object or the management object may increase the signaling overhead of the operated resource object or the management object, affect the operation response time, and reduce the system performance. Moreover, the service process can record a safety log and a system operation log based on safety and maintainability, and then record an operation log in an interpenetration manner, so that the service process becomes overstaffed, the service complexity is increased, and the maintenance difficulty is increased. In addition, when the system is deployed in a large scale, the impact of the scattered recording of the operation logs on the service throughput of the operation logs is large. And because the operation resource object or the management object respectively records the operation logs, the recorded formats, styles, detailed degrees and the like of the operation resource object or the management object cannot be unified, the reading and understanding differences of the operation logs are caused, and the later-stage data integration analysis is not facilitated.

Disclosure of Invention

The embodiment of the application provides a method and a device for storing an operation log, which can solve the problems of long response time of operation requests and low system performance caused by the way of analyzing and storing the operation log by an operated resource object or a management object.

In a first aspect, an embodiment of the present application provides a method for storing an operation log, including: the method comprises the steps that a first network device receives an operation request sent by user equipment; the operation request comprises a request head and a request body; the first network equipment determines whether the operation request needs to store an operation log; if the first network equipment determines that the operation request needs to store the operation log, the first network equipment sends the operation request to the second network equipment to indicate the second network equipment to store the operation log of the operation request; the first network device sends an operation request to the service processing device. Compared with the prior art, the method of storing the operation log by the operated resource object or the management object increases the signaling overhead of the operated resource object or the management object, influences the operation response time and reduces the system performance. According to the method and the device, the first network device can determine the operation request for storing the operation log, and then the second network device stores the operation log in a unified mode, so that the operated resource object or the management object can not sense the process of storing the operation log, and the problems of long response time of the operation request and low system performance are solved.

In one possible implementation, the determining, by the first network device, whether the operation request requires storing the operation log includes: if the first network equipment determines that the request head of the operation request comprises the first identifier, the first network equipment determines that the operation request needs to store an operation log; the first identification is used for indicating an operation log of the storage operation request. That is, the first network device may determine that an operation request with the first identifier needs to store an operation log, and an operation request without the first identifier does not need to store an operation log, where the first identifier may be determined by the service processing device. Although the application is not so limited.

In one possible implementation, the determining, by the first network device, whether the operation request requires storing the operation log includes: if the first network device determines that a hypertext Transfer Protocol (HTTP) request method of the operation request includes a preset HTTP request method, the first network device determines that the operation request needs to store an operation log. For example, if the HTTP request method of the operation request is GET (GET), and the preset HTTP request method also includes GET, the operation request needs to store the operation log. Although the application is not so limited.

In a possible implementation manner, a first network device receives a first response message sent by a service processing device, where the first response message is used to indicate an operation result of an operation request; and the first network equipment informs the second network equipment of updating the operation log according to the operation result. In this way, the second network device can update the operation log of the operation request according to the notification of the first network device, and can perfect the stored operation log of the operation request. The operation result may include success, failure, partial success, and the like, and the present application is not limited thereto.

In one possible implementation, the sending, by the first network device, the operation request to the second network device includes: the first network device sends a first operation request to the second network device, or the first network device sends a preset number of operation requests to the second network device. That is, the first network device may immediately send the operation request to the second network device when receiving the operation request sent by the user equipment, or may send the operation request to the second network device in batch after receiving a certain number of operation requests. In addition, a system or device for collecting operation requests may collect operation requests from a first network device and send the operation requests to a second network device in batches.

In a second aspect, an embodiment of the present application provides a method for storing an operation log, including: the second network equipment receives an operation request sent by the first network equipment; the operation request comprises a request head and a request body; the second network equipment analyzes the operation request to obtain an operation log of the operation request; the second network device stores an operation log. Compared with the prior art, the operation logs are stored by the operated resource objects or the management objects, and the operation logs can be uniformly stored by the second network equipment, so that the operated resource objects or the management objects can not sense the process of storing the operation logs, and the problems of long response time of operation requests and low system performance can be solved.

In one possible implementation, the parsing, by the second network device, the operation request to obtain the operation log of the operation request includes: the second network equipment acquires a first part of the operation log according to the operation request and the first analysis method; the first part is used for indicating summary information of the operation log, and the first analysis method is determined by the second network equipment. That is to say, after receiving the operation request, the second network device may first parse the summary information of the operation request, so that resource overhead of the second network device may be saved, and it may also be ensured that the operation request may be identified when the operation request is updated and the operation request is audited. Of course, the present application is not limited thereto.

In one possible implementation, the summary information includes at least one of an operator identifier, a source Internet Protocol (IP) address of the operation, a target resource identifier, and an operation status. Of course, the present application is not limited thereto.

In one possible implementation, the method further includes: the second network equipment acquires a second part of the operation log according to the operation request and a second analysis method; the second part is used for indicating the detailed information of the operation log, and the second analysis method is determined by the service processing equipment. The second network device may parse the detailed information of the operation log when a user (operator) needs to audit or query the detailed information of the operation request. Compared with the method that the detailed information of the operation request is analyzed after the operation request is received, the resource overhead can be saved.

In one possible implementation, the method further includes: the second network equipment receives a first notification message sent by the first network equipment, wherein the first notification message is used for indicating the second network equipment to update the operation log; and the second network equipment updates the operation log according to the first notification message. In this way, the second network device can update the operation log of the operation request according to the notification message of the first network device to complete the operation log of the operation request. Of course, the present application is not limited to notifying the second network device of updating the operation log through the first notification message.

In a third aspect, an embodiment of the present application provides a first network device, including: the receiving unit is used for receiving an operation request sent by user equipment; the operation request comprises a request head and a request body; the processing unit is used for determining whether the operation request needs to store the operation log; the sending unit is used for sending the operation request to the second network equipment to indicate the second network equipment to store the operation log of the operation request if the processing unit determines that the operation request needs to store the operation log; and the sending unit is also used for sending the operation request to the service processing equipment.

In one possible implementation, the processing unit is configured to: if the request head of the operation request comprises the first identifier, determining that the operation request needs to store an operation log; the first identification is used for indicating an operation log of the storage operation request.

In one possible implementation, the processing unit is configured to: and if the HTTP request method of the operation request comprises the preset HTTP request method, determining that the operation log is required to be stored in the operation request.

In one possible implementation, the receiving unit is further configured to: receiving a first response message sent by the service processing equipment, wherein the first response message is used for indicating an operation result of the operation request; the sending unit is further configured to notify the second network device to update the operation log according to the operation result.

In one possible implementation, the sending unit is configured to: and sending the first operation request to the second network equipment, or sending a preset number of operation requests to the second network equipment.

For technical effects of the third aspect and various possible implementations thereof, reference may be made to the technical effects of the first aspect and various possible implementations thereof, which are not described herein again.

In a fourth aspect, an embodiment of the present application provides a second network device, including: the receiving unit is used for receiving an operation request sent by first network equipment; the operation request comprises a request head and a request body; the processing unit is used for analyzing the operation request to obtain an operation log of the operation request; and the storage unit is used for storing the operation log.

In one possible implementation, the processing unit is configured to: acquiring a first part of an operation log according to the operation request and a first analysis method; the first part is used for indicating summary information of the operation log, and the first analysis method is determined by the second network equipment.

In one possible implementation, the summary information includes at least one of an operator identification, an IP address, a target resource identification, and an operating status.

In one possible implementation, the processing unit is further configured to: acquiring a second part of the operation log according to the operation request and a second analysis method; the second part is used for indicating the detailed information of the operation log, and the second analysis method is determined by the service processing equipment.

In one possible implementation, the receiving unit is further configured to: receiving a first notification message sent by first network equipment, wherein the first notification message is used for indicating second network equipment to update an operation log; the processing unit is further configured to update the operation log according to the first notification message.

For technical effects of the fourth aspect and various possible implementations thereof, reference may be made to the technical effects of the second aspect and various possible implementations thereof, which are not described herein in detail.

The fifth invention provides a system for storing an operation log, which includes a first network device and a second network device; the first network equipment is used for receiving an operation request sent by user equipment; determining whether the operation request needs to store an operation log; if the operation request needs to store the operation log, sending the operation request to the second network equipment; the operation request comprises a request head and a request body; the second network equipment is used for analyzing the operation request to obtain an operation log of the operation request; and storing the operation log.

In a sixth aspect, an embodiment of the present application provides a computer storage medium for storing computer software instructions for the first network device, which includes a program designed to execute the above aspects.

In a seventh aspect, an embodiment of the present application provides a computer storage medium for storing computer software instructions for the second network device, which includes a program designed to execute the above aspects.

In an eighth aspect, a first network device is provided, where the first network device exists in a product form of a chip, and the first network device includes a processor, a memory, and a transceiving component, where the transceiving component includes an input/output circuit, the memory is used to store computer execution instructions, and the processor implements any one of the methods provided in the first aspect by executing the computer execution instructions stored in the memory.

In a ninth aspect, a second network device is provided, which exists in a product form of a chip, and includes a processor, a memory, and a transceiving component, where the transceiving component includes an input/output circuit, the memory is used for storing computer execution instructions, and the processor implements any one of the methods provided in the second aspect by executing the computer execution instructions stored in the memory.

In a tenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any one of the methods provided by the first aspect.

In an eleventh aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the methods provided by the second aspect.

Compared with the prior art, the method of storing the operation log by the operated resource object or the management object increases the signaling overhead of the operated resource object or the management object, influences the operation response time and reduces the system performance. According to the method and the device, the first network device can determine the operation request for storing the operation log, and then the second network device stores the operation log in a unified mode, so that the operated resource object or the management object can not sense the process of storing the operation log, and the problems of long response time of the operation request and low system performance are solved.

Drawings

FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present disclosure;

fig. 2 is a schematic internal structure diagram of a first network device according to an embodiment of the present disclosure;

fig. 3 is a schematic internal structure diagram of a second network device according to an embodiment of the present disclosure;

fig. 4 is a schematic signal interaction diagram of a method for storing an operation log according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a system architecture for auditing logs of operations according to an embodiment of the present disclosure;

FIG. 6 is a schematic signal interaction diagram illustrating a method for storing an operation log according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a first network device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a first network device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a first network device according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a second network device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a second network device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a second network device according to an embodiment of the present application.

Detailed Description

The embodiment of the application is applied to a scene of storing (recording) the operation log. As shown in fig. 1, the architecture of the embodiment of the present application includes a User Equipment (UE), a first network device, an operation log system, and a service system (including a service system 1, a service system 2, and a. Optionally, a load balancer may be further included, for connecting the user equipment and the first network device. The network devices in the architecture may also be connected by a cloud network. When the user equipment receives an operation event from a user, the user equipment can generate an operation request and send the operation request to the load balancer, and the load balancer can send the operation request to the first network equipment. Optionally, the user equipment may also directly send the operation request to the first network device. The first network device may distribute the operation request to the operation log system and the service system after performing corresponding processing on the operation request. The operation log system and the service system can correspondingly process the received operation request.

The user equipment may be a mobile phone (mobile phone), a smart phone, a portable device, a tablet computer, or the like. The user equipment may also be referred to as a terminal or terminal equipment or the like. The user equipment may communicate with the load balancer or the first network device through wired or wireless technology. The user equipment may be used to send requests or commands. The first network device may be a Gateway (Gateway), a router, a switch, a network (Web) server, or the like. The first network device may also be a virtual device such as a virtual gateway, a virtual router, a virtual switch, or a virtual machine. The first network device may be configured to receive and forward the request or command, and may also perform corresponding processing on the received request or command. The oplog system can include at least one second network device. The second network device may be a Web server, an application server, or an HTTP server, among others. The second network device may also be a virtual device such as a virtual Web server, a virtual application server, or a virtual HTTP server. The second network device may be configured to receive requests or commands and may process and store the requests and commands. When the oplog system includes two or more second network devices, the oplog system may be considered a distributed system or cluster. Similarly, a business system may include at least one business processing device. The service processing device may be a service server. The service processing device may also be a virtual device such as a virtual service server. The service processing device can be used for receiving the request and the command, processing the request and the command, and feeding back a processing result. When the business system includes two or more business processing devices, the business system can be considered as a distributed system or cluster.

In one possible design, the oplog system supports logging oplogs through different system/subsystem interfaces, which may be implemented through a gateway, a Web server, or other third-party systems. When the subsequent service is expanded, other types of gateways and Web servers are added, and the added gateways and Web servers can also be directly connected with the operation log system, for example, requests and commands can be directly sent to the operation log system.

In one possible design, the architecture shown in fig. 1 may further include a log-gathering system (not shown in fig. 1) that may actively gather requests or commands received by the first network device and send them in bulk to the second network device. The log-gathering system can include at least one log-gathering device. The log collection device can be a gateway, a router, a switch, a Web server or the like, and can also be a virtual device such as a virtual gateway, a virtual router, a virtual switch, a virtual machine or the like. When the oplogging system includes two or more log-gathering devices, the oplogging system can be considered a distributed system or cluster.

As shown in fig. 2, the first network device may include a processing module 201, a storage module (or memory chip) 202, a monitoring and debugging module 203, and a network connection module 204. The processing module 201 may ensure the utility and scalability of the first network device. The processing module 201 may be used to process received requests and commands. The storage module 202 may ensure that the first network device is capable of supporting multitasking. For example, the storage module 202 may support the gateway to store multiple operation requests or commands simultaneously. The monitoring and debugging module 203 may be configured to implement real-time monitoring on the program stored in the storage module 202, and may also support an online debugging function. The network connection module 204 may be used for data reception, address filtering, and data forwarding, and may be used to implement data exchange between multiple network systems.

As shown in fig. 3, the second network device may include a processing module 301, a communication module 302, a storage module 303, a display module 304, and an input module 305. The processing module 301 is used for controlling hardware devices and application software of each part of the terminal. The communication module 302 is configured to receive an instruction sent by another device using a communication method such as cellular, ethernet, Wireless Fidelity (WiFi), bluetooth, infrared, and the like, and also send data of the terminal to the cloud or another device. The storage module 303 is used for storing a software program, storing data, operating software, and the like of the second network device. The display module 304 may receive and display data of the processing module 202, for example, may be used to display an operation interface and operation results of an operator (e.g., an auditor). The input module 305 may be used to receive an input operation request or command, etc.

The embodiment of the application provides a method for storing an operation log, which comprises the following basic processes: the method comprises the steps that a first network device receives an operation request sent by user equipment; determining whether the operation request needs to store an operation log; and if the operation request is determined to be needed, sending the operation request to the second network equipment. The second network device parses the operation request to obtain an operation log of the operation request, and stores the operation log. In addition, the first network device sends an operation request to the service processing device, so that the service processing device performs corresponding processing according to the operation request. Therefore, compared with the prior art that the operation log is analyzed and recorded by the operated resource object or the management object (in the service processing device), the embodiment of the application can analyze and record the operation log by the second network device, and can solve the problems of long response time of the operation request and low system performance caused by the way of analyzing and storing the operation log by the operated resource object or the management object.

An embodiment of the present application provides a method for storing an operation log, as shown in fig. 4, including:

401. the first network equipment receives an operation request sent by user equipment.

The operation request comprises a request head and a request body. The message header or body may include: the operation time (start time, end time, etc.), the user Identifier (ID), the IP of the operation, the destination IP of the operation, the target resource identifier, the protocol type, and operation related parameters (for example, when the operation request is used to establish a Virtual machine, the operation related parameters may include the number of Virtual Central Processing Units (VCPUs), the memory size, the related data storage address, etc.).

Specifically, the first network device may receive an operation request sent by a transceiver of the user equipment, where the operation request may be generated by a processor of the user equipment according to a user operation detected by the sensor. The user operation is, for example and without limitation, a user clicking or sliding on a preset area of a browser interface or a client interface of a service. The operation request may also be generated by the processor of the user device according to a predetermined program, such as, but not limited to, a program set by the user at the setting interface and started at a predetermined time. Optionally, the first network device may receive an operation request forwarded by the load balancer.

Step 401 may be performed by the network connection module 404 in fig. 2, for example, the network connection module 404 may be configured to receive an operation request sent by the user equipment.

402. The first network device determines whether the operation request requires storing an operation log.

The operation request may correspond to a corresponding operation log, and the operation log may include summary information and detailed information. The summary information includes at least one of an operator identification, an operating IP address, a target resource identification, and an operating status. The detailed information of the operation log has uncertainty, and varies according to the service. For example, if the operation request is for requesting to download a video, the detailed information of the operation log may include a URL of the relevant video, a size of a memory occupied by the relevant video, a format of the relevant video, and the like. If the operation request is used to establish a virtual machine, the detailed information of the operation log may include the number of virtual CPUs, the memory size, the storage address of the relevant data, and the like.

In one possible design, the request header of the operation request may include a first identifier indicating an operation log storing the operation request. If the first network device determines that the request header of the operation request includes the first identifier, the first network device determines that the operation request needs to store the operation log.

In another possible design, if the first network device determines that the HTTP request method of the operation request includes a preset HTTP request method, the first network device determines that the operation request needs to store the operation log. HTTP request methods include selection (OPTIONS), GET, Header (HEAD), transfer (POST), PUT (PUT), DELETE (DELETE), TRACE (TRACE), and CONNECT (CONNECT) requests.

Wherein, OPTIONS: the HTTP request methods supported by the return server for a particular resource may also be used to test the functionality of the server by sending a' request to the web server.

GET: a request is made to a particular resource of the server.

HEAD: a response consistent with the GET request is requested from the server, but the response body will not be returned.

POST: data is submitted to a specified resource for processing requests (e.g., submitting forms or uploading files). The data is contained in the request body. The POST request may result in the creation of a new resource and/or the modification of an existing resource.

PUT: upload its up-to-date content to the specified resource location.

DELETE: the requesting server deletes the resource identified by the requesting Uniform Resource Locator (URL).

TRACE: the requests received by the server are displayed back (e.g., the batch commands being executed and the results of the execution are displayed) and are used primarily for testing or diagnostics.

CONNECT: reserved for proxy servers that can change the connection to a pipe-like manner.

In addition, the HTTP request method may also be customized according to different servers, which is not limited in this application.

Generally, the preset HTTP request methods may include POST, PUT, and DELETE. For example, if the operation request is used to DELETE part of the content of the setting information, that is, the HTTP request method of the operation request is DELETE, the operation log of the operation request needs to be stored.

Step 402 may be performed by processing module 401 in fig. 2, for example, processing module 401 may be configured to determine whether the operation request requires storing an operation log.

403. And if the first network equipment determines that the operation request needs to store the operation log, the first network equipment sends the operation request to the second network equipment.

That is, when the first network device determines that the first operation request requires storing of the operation log, the first network device sends the first operation request to the second network device.

Step 403 may be performed by the network connection module 404 in fig. 2, for example, the network connection module 404 may be configured to send an operation request to the second network device.

404. The second network device obtains a first portion of the operation log according to the operation request and the first parsing method.

The first parsing method may be determined by the second network device. The first part is used for indicating summary information of the operation log. The summary information may be used to audit or update the oplogs in subsequent processes.

Step 404 may be performed by processing module 301 in fig. 3. For example, the processing module 301 may be configured to obtain a first portion of an operation log according to the operation request and the first parsing method.

405. The second network device stores the first portion and the request body of the operation request in a database or memory.

When the operation log of the operation request needs to be audited or updated, the second network device may obtain the request body of the operation request according to the summary information, and perform corresponding processing.

In a possible design, if the request header of the operation request includes the first identifier or part of the summary information, the second network device may store the operation request directly in the database or the memory without parsing the operation request. In a subsequent step, the oplog may be audited or updated based on the first identification or the portion of the summary information in the request header.

Step 405 may be performed by the storage module 303 in fig. 3, for example, the storage module 303 may be configured to store the first part and a request body of the operation request.

406. The first network device sends an operation request to the service processing device.

It should be noted that, the first network device may execute the step 406 immediately after executing the step 401, or may execute the step 406 after executing the step 401 and the step 405, and the execution timing of the step 406 is not limited in this embodiment of the application.

It should be noted that, regardless of whether the operation log needs to be stored in the operation request, the first network device may send the operation request to the service processing device, so that the service processing device performs relevant processing on the operation request. The related processing is determined according to the specific content of the operation request, and the details are not repeated in the embodiments of the present application.

Step 406 may be performed by network connection module 404 in fig. 2. For example, the network connection module 404 may be configured to send an operation request to a service processing device.

407. The first network device receives a first response message sent by the service processing device, wherein the first response message is used for indicating an operation result of the operation request.

The operation result of the operation request includes success, failure, partial success, in-process, and the like.

Step 407 may be performed by network connection module 404 in fig. 2. For example, the network connection module 404 may be configured to receive a first response message sent by the service processing device.

408. And the first network equipment informs the second network equipment of updating the operation log according to the operation result.

In one possible design, the first network device may send a first notification message to the second network device, the first notification message instructing the second network device to update the operation log. The second network device may update the operation log when receiving the first notification message sent by the first network device.

Step 408 may be performed by network connection module 404 in fig. 2. For example, the network connection module 404 may be configured to notify the second network device to update the oplog.

Steps 401 to 408 specifically describe the method for storing and updating the operation log, and may further include step 409 and step 411 when auditing (querying/viewing) the operation log of the operation request.

409. And the second network equipment receives the inquiry message sent by the user equipment.

Wherein the query message may include an operation log identification. The operation log identifier may be the first identifier or the summary information. The second network device may obtain the request body of the operation request and/or the summary information of the operation log according to the operation log identifier.

Step 409 may be performed by network connection module 404 in fig. 2. For example, the network connection module 404 may be configured to receive a query message sent by a user device.

In one possible design, the second network device may receive a query operation input by an operator (including a user) through the input module 306 of the second network device, for example, the query operation may include a specific operation gesture or a specific operation command, and the like. The second network device may obtain summary information of the operation log according to the query operation, and may display the summary information through the display module 304.

It should be noted that, if the detailed information of the operation log needs to be queried, step 410 may be executed.

410. The second network device obtains a second portion of the oplog according to the operation request and the second parsing method.

Wherein the second part is used for indicating the detailed information of the operation log. The second parsing method is determined by the service processing device because the detailed information of the oplog has uncertainty, which varies from service to service.

As shown in fig. 5, the user may send a query request to the second network device through the user device, and after receiving the query request, the second network device may feed back a query result to the user device, so that the user device displays the query result. Specifically, the second network device may start a post-resolution thread (resolution process) according to a specific policy (e.g., system idle), and invoke a corresponding service system resolver (e.g., service system a resolver, service system B resolver.. service system N resolver) by a resolver (parser) to resolve the operation request to obtain detailed information of the operation log, and store the detailed information in the memory. Optionally, the second network device may invoke a corresponding service system parser to parse the operation request to obtain the detailed information of the operation log when receiving the query message for querying the detailed information. A parser may be understood as a program or interface that is generally used to receive instructions or commands.

Optionally, the i18n process may be performed during parsing. The i18n can provide a support mechanism for multi-national languages on a system library, and an application program using the i18n can return contents after language localization (such as directly returning Chinese) without needing to hang a local language platform.

Step 410 may be performed by processing module 301 in fig. 3. For example, the processing module 301 may be configured to obtain a second portion of the oplog according to the operation request and the second parsing method.

411. And the user equipment displays the query result fed back by the second network equipment.

The query result comprises summary information and/or detailed information of the operation log.

Therefore, after the first network device determines that the operation request needs to record the operation log, the first network device can asynchronously send the operation request to the second network device, and the second network device analyzes and records the operation log. Compared with the prior art, the operation log is analyzed and recorded through the operated resource object or the management object, so that the response time of the operation request is long and the system performance is low. According to the embodiment of the application, the second network device can uniformly analyze and record the operation log, so that the process of analyzing and recording the operation log by the operated resource object or the management object in the service flow is omitted, the response time of the operation request can be shortened, and the system performance can be improved. Particularly, for a system with high concurrency and response requirements, the time consumption of system requests can be greatly reduced, the query requirements of the system are met, and the system performance is improved.

Yet another embodiment of the present application provides a method of storing an operation log, as shown in fig. 6, including:

601. the first network equipment receives an operation request sent by user equipment.

The specific process may refer to step 401.

602. The first network device determines whether the operation request requires storing an operation log.

The specific process may refer to step 402.

603. If the first network device determines that the operation request needs to store the operation log, the first network device sends a preset number of operation requests to the second network device.

The first network device may send a preset number of operation requests to the second network device after determining that the preset number of operation requests require storing of operation logs. The preset number may be determined by the first network device. For example, the preset number may be 100, that is, the first network device may send 100 operation requests to the second network device after determining that the 100 operation requests need to store the operation log. Optionally, the first network device may send an operation request, which needs to store an operation log, to the second network device every time the operation request is received at a preset time interval. For example, the preset time interval is 5 min.

Step 603 may be performed by the processing module 201 and the network connection module 204 in fig. 2, for example, the processing module 201 may be configured to determine whether the operation request requires storing an operation log. The network connection module 204 may be configured to send a preset number of operation requests to the second network device.

In one possible design, the log-gathering system may actively gather operation requests received by a first network device that require an operation log to be stored and send the operation requests in bulk to a second network device.

604. The second network device parses the operation request to obtain an operation log of the operation request.

The second network equipment acquires a first part of the operation log according to the operation request and the first analysis method; the first part is used for indicating summary information of the operation log, and the first parsing method is determined by the second network equipment. The second network equipment acquires a second part of the operation log according to the operation request and a second analysis method; the second part is used for indicating the detailed information of the operation log, and the second analysis method is determined by the service processing equipment.

That is, when receiving the operation request, the second network device may, as in the embodiment shown in fig. 4, parse the summary portion of the operation log first, and then parse the detailed portion of the operation log in the subsequent step; the second network device may also directly parse the summary portion and the detailed portion of the operation log when receiving the operation request, as in the embodiment of the present application.

Step 604 may be performed by processing module 301 in fig. 3. For example, the processing module 301 may be configured to parse the operation request to obtain an operation log of the operation request.

605. The second network device stores an operation log.

That is, the second network device stores the parsed operation log in a database or a corresponding memory.

Step 605 may be performed by the storage module 303 in fig. 3, for example, the storage module 303 may be used to store an operation log.

606. The first network device sends an operation request to the service processing device.

The embodiment of the present application does not limit the execution timing of step 606. And no matter whether the first network device determines whether the operation request needs to store the operation log or not and whether the operation request reaches the preset number or not, the first network device can send the operation request to the service processing device so that the service processing device can perform relevant processing on the operation request.

Step 606 may be performed by network connection module 204 in fig. 2. For example, the network connection module 204 may be configured to send an operation request to a service processing device.

607. The first network device receives a first response message sent by the service processing device, wherein the first response message is used for indicating an operation result of the operation request.

The operation result of the operation request includes success, failure, partial success, in-progress, and the like.

Step 607 may be performed by network connection module 204 in fig. 2. For example, the network connection module 204 may be configured to receive a first response message sent by the service processing device.

608. And the first network equipment informs the second network equipment of updating the operation log according to the operation result.

The specific process may refer to step 408.

Step 609 and 611 may also be included when auditing the operation log of the operation request.

609. And the second network equipment receives the inquiry message sent by the user equipment.

Wherein the query message may include an operation log identification. The second network device may obtain the detailed information of the operation log according to the operation log identifier. The operation log identifier may be the first identifier or the summary information.

Step 609 may be performed by network connection module 204 in fig. 2. For example, the network connection module 204 may be configured to receive a query message sent by a user equipment.

610. And the second network equipment sends the query result of the operation request to the user equipment.

Step 610 may be performed by network connection module 204 in fig. 2. For example, the network connection module 204 may be configured to send the query result of the operation request to the user device.

611. And the user equipment displays the query result fed back by the second network equipment.

Therefore, after the first network device determines that the operation request needs to record the operation log, the first network device can send the operation request to the second network device in batches, and the second network device analyzes and records the operation log. Compared with the prior art, the operation log is analyzed and recorded through the operated resource object or the management object, so that the response time of the operation request is long and the system performance is low. According to the embodiment of the application, the second network device can uniformly analyze and record the operation log, so that the process of analyzing and recording the operation log by the operated resource object or the management object in the service flow is omitted, the response time of the operation request can be shortened, and the system performance can be improved. Moreover, the second network equipment uniformly records the operation logs, and the recorded formats, styles, detailed degrees and the like can be uniform, so that the later-stage data integration and analysis are facilitated.

The above description mainly introduces the solutions provided in the embodiments of the present application from the perspective of the first network device and the second network device. It is understood that the first network device and the second network device contain corresponding hardware structures and/or software modules for performing the respective functions in order to realize the functions. Those skilled in the art will readily appreciate that the algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the first network device and the second network device may be divided into function modules according to the above method example, for example, each function module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

In the case of dividing the functional modules according to the respective functions, fig. 7 shows a schematic diagram of a possible structure of the first network device 7 according to the foregoing embodiment, where the first network device includes: a receiving unit 701, a processing unit 702 and a transmitting unit 703. The receiving unit 701 is configured to receive an operation request sent by a user equipment; the operation request comprises a request head and a request body. The processing unit 702 is configured to determine whether the operation request requires storing an operation log. The sending unit 703 is configured to send, if it is determined by the processing unit that the operation request needs to store the operation log, the operation request to the second network device to indicate the second network device to store the operation log of the operation request; and is also used for sending an operation request to the service processing equipment.

For example, the receiving unit 701 is configured to support the first network device to perform processes 401 and 407 in fig. 3, and processes 601 and 607 in fig. 6. Processing unit 702 is configured to support the first network device to perform process 402 in fig. 4, process 602 in fig. 6. The sending unit 703 is configured to support the first network device to perform processes 403, 406, and 408 in fig. 4, and processes 603, 606, and 608 in fig. 6. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Fig. 8 shows a schematic diagram of a possible structure of the first network device involved in the above-described embodiment, in the case of an integrated unit. The first network device 8 includes: a processing module 801 and a communication module 802. Processing module 801 is configured to control and manage actions of the first network device, for example, processing module 801 is configured to support the first network device to execute process 402 in fig. 4 and process 602 in fig. 6. The communication module 802 is used to support communication between the first network device and other network entities, such as communication with a server, downloading an installation package of an application from the server, and the like. The first network device may further include a storage module 803 for storing program codes and data of the first network device, for example, for storing operation requests in the embodiments of the present application.

When the processing module 801 is a processor, the communication module 802 is a communication interface, and the storage module 803 is a memory, the first network device may be implemented by the computer device (or system) in fig. 9.

Fig. 9 is a schematic diagram of a computer device provided in an embodiment of the present application. The computer device 900 includes at least one processor 901, a communication bus 902, memory 903, and at least one communication interface 904.

The processor 901 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

Communication bus 902 may include a path that transfers information between the aforementioned components.

Communication interface 904 may be implemented using any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 903 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 903 is used for storing application program codes for executing the scheme of the application, and the processor 901 controls the execution. The processor 901 is configured to execute application program code stored in the memory 903 to implement the functions of the method of the present patent.

In particular implementations, processor 901 may include one or more CPUs such as CPU0 and CPU1 in fig. 9 as an example.

In particular implementations, computer device 900 may include multiple processors, such as processor 901 and processor 907 of FIG. 9, for one embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In particular implementations, computer device 900 may also include an output device 905 and an input device 906, as one embodiment. An output device 905, which is in communication with the processor 901, may display information in a variety of ways. For example, the output device 905 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 906, which is in communication with the processor 901, may accept input from a user in a variety of ways. For example, the input device 906 may be a mouse, keyboard, touch screen device, or sensing device, among others.

The computer device 900 described above may be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device 900 may be a desktop computer, a laptop computer, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or a device with a similar structure as in fig. 9. The embodiments of the present application do not limit the type of computer device 900.

In the case of dividing the functional modules by corresponding functions, fig. 10 shows a schematic diagram of a possible structure of the second network device 10 according to the foregoing embodiment, where the second network device includes: a receiving unit 1001, a processing unit 1002 and a storage unit 1003. The receiving unit 1001 is configured to receive an operation request sent by a first network device; the operation request comprises a request head and a request body; the processing unit 1002 is configured to parse the operation request to obtain an operation log of the operation request; the storage unit 1003 is configured to store an operation log.

For example, the receiving unit 1001 is configured to support the second network device to perform the process 403 in fig. 4, the process 603 in fig. 6; processing unit 1002 is configured to support a second network device to perform process 404 of fig. 4, process 604 of fig. 6; storage unit 1003 is configured to support the second network device to execute process 405 in fig. 4, process 605 in fig. 6. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Fig. 11 shows a schematic diagram of a possible structure of the second network device involved in the above-described embodiment, in the case of an integrated unit. The second network device 11 includes: a processing module 1101 and a communication module 1102. The processing module 1101 is configured to control and manage actions of the second network device, for example, the processing module 1101 is configured to support the second network device to execute the process 404 in fig. 4, the process 604 in fig. 6, and the communication module 1102 is configured to support communication between the second network device and other network entities, for example, communication with a server, downloading an installation package of an application from the server, and the like. The second network device may further include a storage module 1103, configured to store program codes and data of the second network device, for example, to store an operation request in this embodiment of the present application.

The second network device may be implemented by the computer device (or system) in fig. 12 when the processing module 801 is a processor, the communication module 802 is a communication interface, and the storage module 803 is a memory.

Fig. 12 is a schematic diagram of a computer device according to an embodiment of the present invention. The computer device 1200 includes at least one processor 1201, a communication bus 1202, a memory 1203, and at least one communication interface 1204.

The processor 1201 may be a CPU, microprocessor, ASIC, or one or more integrated circuits configured to control the execution of programs in accordance with the inventive arrangements.

The communication bus 1202 may include a path for communicating information between the aforementioned components.

The communication interface 1204 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as ethernet, RAN, WLAN, etc.

The memory 1203 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 1203 is used for storing application program codes for implementing the present invention, and the processor 1201 controls the execution of the application program codes. The processor 1201 is configured to execute application program code stored in the memory 1203 to implement the functions of the method of the present patent.

In particular implementations, processor 1201 may include one or more CPUs such as CPU0 and CPU1 in fig. 12, for example, as an example.

In particular implementations, computer device 1200 may include multiple processors, such as processor 1201 and processor 1207 in FIG. 12, for example, as an example. Each of these processors may be a single core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In particular implementations, computer device 1200 may also include an output device 1205 and an input device 1206, as one embodiment. An output device 1205, in communication with the processor 1201, may display information in a variety of ways. For example, the output device 1205 may be an LCD, LED display device, CRT display device, or projector, among others. The input device 1206 is in communication with the processor 1201 and may accept user input in a variety of ways. For example, the input device 1206 may be a mouse, keyboard, touch screen device, or sensing device, among others.

The computer device 1200 described above may be a general purpose computer device or a special purpose computer device. In particular implementations, the computer device 1200 may be a desktop, laptop, web server, PDA, mobile phone, tablet, wireless terminal device, communication device, embedded device, or device with similar structure as in fig. 12. Embodiments of the invention are not limited by the type of computer device 1200.

The above-mentioned embodiments, objects, technical solutions and advantages of the present application are further described in detail, it should be understood that the above-mentioned embodiments are only examples of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present application should be included in the scope of the present application.

Claims

1. A method of storing an oplog, comprising:

the method comprises the steps that a first network device receives an operation request sent by user equipment; wherein the operation request comprises a request head and a request body;

the first network equipment determines whether the operation request needs to store an operation log;

if the first network device determines that the operation request needs to store an operation log, the first network device sends the operation request to a second network device to indicate the second network device to store the operation log of the operation request;

and the first network equipment sends the operation request to service processing equipment.

2. The method of claim 1, wherein determining, by the first network device, whether the operation request requires storing an operation log comprises:

if the first network device determines that the request header of the operation request comprises a first identifier, the first network device determines that the operation request needs to store an operation log; wherein the first identifier is used for indicating an operation log for storing the operation request.

3. The method of claim 1, wherein determining, by the first network device, whether the operation request requires storing an operation log comprises:

if the first network device determines that the hypertext transfer protocol (HTTP) request method of the operation request comprises a preset HTTP request method, the first network device determines that the operation request needs to store an operation log.

4. The method according to any one of claims 1-3, further comprising:

the first network equipment receives a first response message sent by the service processing equipment, wherein the first response message is used for indicating an operation result of the operation request;

and the first network equipment informs the second network equipment of updating the operation log according to the operation result.

5. The method of any of claims 1-3, wherein sending the operation request from the first network device to the second network device comprises:

the first network device sends a first operation request to the second network device, or the first network device sends a preset number of operation requests to the second network device.

6. A method of storing an oplog, comprising:

the second network equipment receives an operation request sent by the first network equipment; the operation request is received by the first network equipment from user equipment and needs to be sent to service processing equipment, and the operation request comprises a request header and a request body;

the second network equipment analyzes the operation request to obtain an operation log of the operation request;

the second network device stores the operation log.

7. The method of claim 6, wherein parsing, by the second network device, the operation request to obtain an operation log of the operation request comprises:

the second network equipment acquires a first part of the operation log according to the operation request and a first analysis method; wherein the first portion is used to indicate summary information of the operation log, and the first parsing method is determined by the second network device.

8. The method of claim 7, wherein the summary information comprises at least one of operator identification, operating Internet Protocol (IP) address, target resource identification, and operating status.

9. The method according to claim 7 or 8, characterized in that the method further comprises:

the second network equipment acquires a second part of the operation log according to the operation request and a second analysis method; the second part is used for indicating detailed information of the operation log, and the second analysis method is determined by the service processing equipment.

10. The method according to any one of claims 6-8, further comprising:

the second network device receives a first notification message sent by the first network device, wherein the first notification message is used for indicating the second network device to update the operation log;

and the second network equipment updates the operation log according to the first notification message.

11. A first network device, comprising:

the receiving unit is used for receiving an operation request sent by user equipment; wherein the operation request comprises a request head and a request body;

the processing unit is used for determining whether the operation request needs to store an operation log;

a sending unit, configured to send the operation request to a second network device to instruct the second network device to store an operation log of the operation request if it is determined by the processing unit that the operation request needs to store the operation log;

the sending unit is further configured to send the operation request to a service processing device.

12. The first network device of claim 11, wherein the processing unit is configured to:

if the request head of the operation request comprises the first identifier, determining that the operation request needs to store an operation log; wherein the first identifier is used for indicating an operation log for storing the operation request.

13. The first network device of claim 11, wherein the processing unit is configured to:

and if the hypertext transfer protocol (HTTP) request method of the operation request comprises a preset HTTP request method, determining that the operation request needs to store an operation log.

14. The first network device of any of claims 11-13, wherein the receiving unit is further configured to:

receiving a first response message sent by the service processing equipment, wherein the first response message is used for indicating an operation result of the operation request;

the sending unit is further configured to notify the second network device to update the operation log according to the operation result.

15. The first network device according to any of claims 11-13, wherein the sending unit is configured to:

and sending a first operation request to the second network equipment, or sending a preset number of operation requests to the second network equipment.

16. A second network device, comprising:

the receiving unit is used for receiving an operation request sent by first network equipment; the operation request is received by the first network equipment from user equipment and needs to be sent to service processing equipment, and the operation request comprises a request header and a request body;

the processing unit is used for analyzing the operation request to obtain an operation log of the operation request;

and the storage unit is used for storing the operation log.

17. The second network device of claim 16, wherein the processing unit is configured to:

acquiring a first part of the operation log according to the operation request and a first analysis method; wherein the first portion is used to indicate summary information of the operation log, and the first parsing method is determined by the second network device.

18. The second network device of claim 17, wherein the summary information includes at least one of an operator identification, an operating internet protocol, IP, address, a target resource identification, and an operating status.

19. The second network device of claim 17 or 18, wherein the processing unit is further configured to:

acquiring a second part of the operation log according to the operation request and a second analysis method; the second part is used for indicating detailed information of the operation log, and the second analysis method is determined by the service processing equipment.

20. The second network device according to any of claims 16-18, wherein the receiving unit is further configured to:

receiving a first notification message sent by the first network device, where the first notification message is used to instruct the second network device to update the operation log;

the processing unit is further configured to update the operation log according to the first notification message.

21. A system for storing an operation log, comprising a first network device and a second network device; wherein the content of the first and second substances,

the first network equipment is used for receiving an operation request sent by user equipment; determining whether the operation request needs to store an operation log; if the operation request needs to store the operation log, sending the operation request to second network equipment; wherein the operation request comprises a request head and a request body;

the second network equipment is used for analyzing the operation request to obtain an operation log of the operation request; storing the operation log;