WO2021129849A1

WO2021129849A1 - Log processing method, apparatus and device, and storage medium

Info

Publication number: WO2021129849A1
Application number: PCT/CN2020/139801
Authority: WO
Inventors: 田琪; 温秋明; 朱玺
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-12-26
Filing date: 2020-12-27
Publication date: 2021-07-01
Also published as: CN113055760A

Abstract

Proposed in embodiments of the present application are a log processing method, apparatus and device, and a storage medium. The method comprises: determining a transaction identification number of a service flow; generating, for an application module that processes the service flow, a message log associated with the transaction identification number; and determining a service fault source according to fault information of the message log.

Description

Log processing method, device, equipment and storage medium

Cross references to related applications

This application is filed based on a Chinese patent application with an application number of 201911364466.9 and an application date of December 26, 2019, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated into this application by way of introduction.

Technical field

This application relates to the field of telecommunication equipment, and in particular to a log processing method, device, system and storage medium.

Background technique

At present, Optical Transport Network (OTN) equipment implements control plane access through the Automatically Switched Opetical (ASON) protocol, so that the equipment is under the automatic control of ASON to ensure that the network is efficient, timely, intelligent and reliable. However, based on the ASON control plane management architecture, from the upstream controller to the downstream board, there are many application modules, and the message log format recorded by each application module is not uniform, and even lacks message logs. In addition, message logs are usually recorded in binary form. After the explosive growth of business data, the message log is parsed through the traditional "number knot" method, which usually fails to reflect the relationship between the business flow and accurately locate the fault location.

Summary of the invention

This application provides a log processing method, device, equipment, and storage medium.

A log processing method provided by an embodiment of the present application includes: determining a transaction identification number of a business flow; generating a message log associated with the transaction identification number for an application module processing the business flow; and according to failure information of the message log Determine the source of business failures.

A log processing device provided by an embodiment of the present application includes: an identification determination module, configured to determine a transaction identification number of a business flow; a log generation module, configured to generate an association with the transaction identification number for an application module processing the business flow The message log; the log analysis module is used to determine the source of the business failure according to the failure information of the message log.

A device provided by an embodiment of the present application includes: one or more processors; a memory for storing one or more programs; when the one or more programs are executed by the one or more processors, all The one or more processors implement the log processing method as described in any of the embodiments of the present application.

An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the program is executed by a processor, the log processing method as described in any of the embodiments of the present application is implemented.

Regarding the above embodiments and other aspects of the application and their implementation manners, more descriptions are provided in the description of the drawings, the specific implementation manners, and the claims.

Description of the drawings

FIG. 1 is a flowchart of the steps of a log processing method provided by an embodiment of the present application;

FIG. 2 is a flowchart of the steps of another log processing method provided by an embodiment of the present application;

FIG. 3 is a flowchart of the steps of another log processing method provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a log processing device provided by an embodiment of the present application;

Fig. 5 is a schematic structural diagram of a device provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. It should be noted that the embodiments in the application and the features in the embodiments can be combined with each other arbitrarily if there is no conflict.

Fig. 1 is a step flow chart of a log processing method provided by an embodiment of the present application. The embodiment of the present application can be applied to the case of processing message logs in optical transport network equipment. The method can be performed by the log processing apparatus in the embodiment of the present application. To execute, the device can be implemented by software and/or hardware. Referring to FIG. 1, the method of the embodiment of the present application includes the following steps:

Step 101: Determine the transaction identification number of the service flow.

Among them, the service stream can be the data stream transmitted in the optical transport network equipment, or the service-related data carried on the optical transport network equipment. The service stream can be processed by the application module in the optical transport network equipment. A service stream can be multiple Each application module is processed. For example, service flow a can be processed by application module A first, and then processed by application module B.

In an example, the transaction identification number can be an identification number used to identify a service flow. The transaction identification number can be globally unique in the optical transmission network device. The transaction identification number corresponding to different service flows can be different, which can be generated for each service flow. The corresponding transaction identification number.

Step 102: Generate a message log associated with the transaction identification number for the application module processing the service flow.

Among them, the application module can be a software module or a hardware module mounted on the optical transport network equipment, and the application module can implement related business functions by processing the business flow; the message log can be a data file that records the business flow processing process, and the message log is stored In the storage space of optical transport network equipment.

In an example, the application module that processes the business flow can generate the message log by calling the public application software interface. The log record in the message log corresponds to the business flow. Multiple business flows can correspond to the same log record. It is understandable that , The message log can be identified by the transaction identification number, and the message log can be stored in the storage space of the device applying the method of this application.

Step 103: Determine the source of the service failure according to the failure information in the message log.

Among them, the fault information can be the error information stored in the message log, it can be the failure information generated in the processing of the business flow, or it can be the timeout information generated in the processing of the business flow, etc. The source of the business failure can be the application module that failed to process the business flow, for example A business flow can be processed by application module A, application module B, and application module C. An error occurs when the business flow is processed by application module B. The source of the business failure of the business flow can be application module B.

In the embodiment of the present application, the message log can be analyzed to obtain the fault information, and the business fault source of the fault can be obtained according to the fault information. For example, since the message log in the present application is in a unified format, it can be According to the regular expression matching the fault information in the message log, the fault information can be analyzed to obtain the source of the business fault.

The technical solution of the embodiment of the present application generates a message log for the application module processing the business flow by determining the transaction identification number of the business flow. The message log can be associated with the transaction identification number, and the source of the business failure is determined based on the failure information in the message log. The relationship between the business flows in each application module is reduced, the difficulty of processing the message log is reduced, and the accuracy of locating the source of business faults can be improved.

Fig. 2 is a step flow chart of another log processing method provided by an embodiment of the present application; the embodiment of the present application concretes the method of generating a message log. Referring to Fig. 2, the log processing method provided by the embodiment of the present application includes :

Step 201: Generate a check value according to the current system time through a preset check algorithm.

The preset check algorithm may be a preset check algorithm, and a check value may be generated according to the system time. The preset check algorithm may be, for example, a cyclic redundancy check (CRC) algorithm. The current system time It can be the system time in the device that implements the log processing method of this application. For example, it can be the system time of a smart terminal or an optical transmission device. The check value can be a digit group generated after converting the current system time. The number can be fixed, and the check value can be used to generate the transaction identification number of the business flow.

In an example, the system time of the device that implements the method of the embodiment of the present application can be obtained, and the system time can be processed according to a preset check algorithm to generate a check value.

Step 202: Generate a random number of the service flow, and generate the transaction identification number of the service flow according to the random number and the check value, wherein the transaction identification number is globally unique.

Among them, the random number may be a randomly generated value, and the random number is generated corresponding to the service flow, and the random number generated by different service flows may be different.

In the embodiment of this application, a corresponding random number can be generated for each service flow, the check value generated based on the system time and the random number can be summed, and the sum of the random number and the check value can be regarded as the service flow correspondence It can be understood that the method of generating the transaction identification number corresponding to the service flow based on the random number and the check value is not unique. You can also use the difference, XOR value and AND value of the random number and the check value as The transaction identification number corresponding to the service flow. It is understandable that because the random numbers of different business flows are not the same, when the system time corresponding to the business flow is the same, the transaction identification number corresponding to the business flow can also be different, and the transaction identification number corresponding to the business flow is globally unique and can be combined with other The transaction identification number of the business flow is not repeated.

Step 203: Determine a corresponding message extraction rule according to the message protocol of the application module.

Among them, the message message protocol can be the processing method for the application module to analyze the service flow. The message message protocol can be stored in a unified message model device, for example, which can provide multiple protocol interfaces for the application module, such as UC port. , MIM port, S port, UIL port and U port, etc., the application module can call the unified messaging module device to obtain the corresponding message extraction rules.

In an example, the unified message module device may be called to read the message extraction rules for processing the service flow, and the message extraction rules may include message structure files, common header files, message message types, and so on. In an example, the message type can be stored in association with the message code in the service flow, the message type can be stored as a hash table in the unified messaging module device, and the index can be the message code, and the message code in the service flow can be passed through The corresponding message type is found in the unified messaging model device.

Step 204: Extract the message content of the service flow according to the message extraction rule.

In an example, the content of the message may be the business data in the service flow. Because the message format of the message message that can be processed by the application module is different, the obtained message extraction rules can analyze the message messages in the service flow. , To obtain the message content of the message message in the corresponding service flow.

Step 205: Associate the content of the message with the transaction identification number of the service flow and store it as a message log.

The message log may be a text file composed of log records, and the message log may be stored in the storage space of the device to which the method of the embodiment of the present application is applied.

In the embodiment of this application, the message content processed in the application module can be stored as a message log. In order to identify the message content, the transaction identification number of the service flow and the corresponding message content are stored in the message log as The log record sequence number of the message log. In an example, the message log may also store the processing operation of the application module on the message content and the direction of sending and receiving message messages in the service flow.

Step 206: Obtain log records in the message log to form a message queue.

Among them, the log record can be a component of the message log. The log record can include the operation information of the application module on the service flow, the content of the message processed by the application module, and the message direction of the application module processing the message message. The message queue can be The storage space used for analyzing log records may be, for example, the cache space of a device that implements the method in the embodiment of the present application.

In an example, the log records in the message log may be read to the message queue, where the log records read into the message queue may be log records matching a preset keyword. Exemplarily, a regular expression can be used to select a log record matching a preset keyword in the message log and add it to the message queue.

Step 207: Obtain the fault information in the message queue, and display it in a preset format to determine the source of the service fault.

Among them, the fault information may be information about a fault that occurs when the application module processes the service flow, and the fault information may be stored in the message log.

In the embodiment of the present application, the fault information recorded in the log in the message queue can be extracted. The fault information can be, for example, one or more fields of the log record. The log records in the message queue can be displayed and the fault information can be highlighted. For example, the fault information can be displayed by increasing the font size or bolding the font. The preset format can be a format for highlighting the fault information, and it can also include highlighting or changing the font. The display of fault information helps users find the source of business faults in a timely manner. It is understandable that fault information can also be displayed together with the transaction identification number, which is convenient for sorting out the fault business flow corresponding to the business fault.

In the technical solution of the embodiment of the application, the check value is determined according to the current system time through a preset check algorithm, a random number corresponding to the service flow is generated, and the transaction identification number corresponding to the service flow is determined according to the check value and the random number. The message message protocol determines the corresponding message extraction rules, extracts the message content in the business flow according to the message extraction rules, stores the message content and transaction identification number as a message log, and obtains the log records in the message log to form a message queue, Obtain the fault information in the message queue, and display the fault information in a preset format to determine the source of the business fault, which realizes the rapid determination of the source of the business fault, reduces the difficulty of processing the message log, and enhances the stability of the business.

In one embodiment, storing the message content and the transaction identification number as a message log includes: storing the message content and the transaction identification number as a business message log; reading at least two The business message logs of the application module are merged as the message log.

In the embodiment of the present application, when generating a message log, the content of the message can be stored as a business message log in the storage space of the device. Each application module can store its own business message log, which can be read from each application module. To merge the business message logs, the merged business message log file can be used as the message log.

Fig. 3 is a step flow chart of another log processing method provided by an embodiment of the present application; referring to Fig. 3, the log processing method provided by an embodiment of the present application includes:

Step 301: Generate a check value according to the current system time through a preset check algorithm.

Step 302: Generate a random number of the service flow, and generate the transaction identification number of the service flow according to the random number and the check value, wherein the transaction identification number is globally unique.

Step 303: Determine a corresponding message extraction rule according to the message message protocol of the application module.

Step 304: Extract the message content of the service flow according to the message extraction rule.

Step 305: Associate the content of the message with the transaction identification number of the service flow and store it as a message log.

Step 306: Match the target log record in the message log according to a preset keyword, and store the target log record in the message queue.

Among them, the preset keyword may be the keyword of the target log record of the sort order, for example, it may be the message direction and message type, etc. The target log record may be the log record of the message log that matches the preset keyword, and the target log record Can include preset keywords.

In one example, the log records in the message log can be matched according to preset keywords. When the log records have preset keywords, the log records can be used as target log records. It is understandable that the message logs can be Obtain multiple target log records by matching preset keywords. You can add the acquired target log records to the message queue.

Step 307: Filter the log records in the message queue according to preset filtering keywords.

In the embodiment of the present application, the log records in the message queue can be filtered. When the log records contain preset filtering keywords, the log records can be cleared from the message queue.

Step 308: Sort and display the log records in the message queue according to the order of the transaction identification number.

In an example, in order to facilitate the visual display of the fault information, the log records in the message queue may be sorted in the order of transaction identification numbers, and the sorted message queue may be displayed. In one example, the log records belonging to the same transaction identification number can be displayed in the order of request messages and response messages, and the log records corresponding to the same transaction identification number can also be displayed in sequence according to chronological order.

Step 309: The failure information in the log record is highlighted in red, where the failure information includes at least one of response failure information and timeout failure information.

In an example, the fault information can be marked with information highlighted in red. When the log records in the message queue are displayed in a view, the fault information can be highlighted. In this embodiment of the application, the fault information can include application module processing. Response failure information and timeout failure information during business flow.

Exemplarily, the SND controller configures the electrical/optical layer services, and can generate a unique transaction ID for each service flow. The transaction ID can realize the association of the service flow in each application module, and the service module records by calling the unified message interface The message message is used as the message log. The message log can also include the issued message and the configuration result response message. It can read the static message structure XML file and the fixed public header file to obtain the pre-set message message parsing prototype. The message parsing prototype can be stored in a global hash table, the index of the global hash table can be the message code, and the message parsing prototype and the message code can correspond one-to-one. The stored messages can be extracted from the message log. The extraction method can extract the fields matching the keywords through python regular expressions, and the extracted fields can be stored in the message queue. The messages in the message queue can be filtered, and the messages matching the filter conditions can be discarded. The message parsing prototype can be obtained according to the unified message model. The message parsing prototype is only compared with the messages in the message queue, and the occupancy defined by the attribute type in the message parsing prototype is only compared. Length parses the message content. In order to facilitate visual display, the parsed message content can be sorted according to the service ID. The content of the messages belonging to the same service flow can be sorted according to the actual order, and the request and response messages belonging to a service flow are displayed together. The service flow is displayed in sequence according to time. The service configuration response result failure and timeout are highlighted in red. By judging the response result, the boundary area of the service failure can be quickly located.

4 is a schematic structural diagram of a log processing device provided by an embodiment of the present application; the log processing device provided by an embodiment of the present application can execute the log processing method provided by any embodiment of the present application, and has the corresponding functional modules and beneficial effects of the execution method . The device may be implemented by software and/or hardware, and includes, for example, an identification determination module 401, a log generation module 402, and a log analysis module 403.

Wherein, the identification determination module 401 is used to determine the transaction identification number of the service flow.

The log generation module 402 is configured to generate a message log associated with the transaction identification number for the application module processing the service flow.

The log analysis module 403 is configured to determine the source of the business failure according to the failure information of the message log.

In the technical solution of the embodiment of the present application, the transaction identification number of the business flow is determined by the identification determination module, the log generation module generates a message log for the application module processing the business flow, the message log can be associated with the transaction identification number, and the log analysis module is based on the information in the message log The fault information determines the source of business faults, clarifies the relationship between the business flows in each application module, reduces the difficulty of message log processing, and improves the accuracy of business fault source location.

In one embodiment, the identification determination module 401 includes: a check value unit, which is used to generate a check value according to the current system time through a preset check algorithm; and an identification unit, which is used to generate a random number of the service flow, according to The random number and the check value generate the transaction identification number of the service flow, wherein the transaction identification number is globally unique.

In one embodiment, the log generation module 402 includes: a rule determination unit, configured to determine a corresponding message extraction rule according to the message message protocol of the application module; a content extraction unit, configured to extract according to the message extraction rule The message content of the service flow; and a log storage unit for storing the message content in association with the transaction identification number of the service flow as a message log.

In one embodiment, the log storage unit includes: a business log subunit for storing the message content and the transaction identification number as a business message log; and a merge log subunit for reading at least two The business message logs of the application module are merged as the message log.

In one embodiment, the log analysis module 403 includes: a message queue unit for obtaining log records in the message log to form a message queue; and a failure information unit for obtaining failure information in the message queue, and according to Display in a preset format to determine the source of business failures.

In one embodiment, the message queue unit includes: a record reading subunit, configured to match a target log record in the message log according to a preset keyword, and store the target log record in the message queue; and record The filtering subunit is used to filter the log records in the message queue according to preset filtering keywords.

In one embodiment, the fault information unit includes: a message sorting subunit, configured to sort and display log records in the message queue in the order of the transaction identification number; and a highlighting subunit for the log The fault information in the record is highlighted in red, where the fault information includes at least one of response failure information and timeout failure information.

FIG. 5 is a schematic structural diagram of a device provided by an embodiment of the present application. As shown in FIG. 5, the device includes a processor 50, a memory 51, an input device 52, and an output device 53; the number of processors 50 in the device may be one Or more, one processor 50 is taken as an example in FIG. 5; the device processor 50, the memory 51, the input device 52, and the output device 53 may be connected by a bus or other means. In FIG. 5, the connection by a bus is taken as an example.

As a computer-readable storage medium, the memory 51 can be used to store software programs, computer-executable programs, and modules, such as the modules corresponding to the log processing device in the embodiment of the present application (identification determination module 401, log generation module 402, and log analysis module 403). ). The processor 50 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the memory 51, that is, realizes the above-mentioned log processing method.

The memory 51 may mainly include a program storage area and a data storage area. The program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the terminal, and the like. In addition, the memory 51 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the memory 51 may include a memory remotely provided with respect to the processor 50, and these remote memories may be connected to the device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The input device 52 can be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the device. The output device 53 may include a display device such as a display screen.

An embodiment of the present application also provides a storage medium containing computer-executable instructions, which are used to execute a log processing method when the computer-executable instructions are executed by a computer processor, and the method includes:

Determine the transaction identification number of the business flow; generate a message log associated with the transaction identification number for the application module processing the business flow; determine the source of the business failure according to the failure information of the message log.

Of course, the storage medium containing computer-executable instructions provided by the embodiments of the present application is not limited to the method operations described above, and can also execute the log processing methods provided in any of the embodiments of the present application. Related operations.

The technical solution of the embodiment of the application generates a transaction identification number for the business flow, generates a message log at each application module according to the transaction identification number, and determines the source of the business failure according to the failure information of the message log. The transaction identification number of the embodiment of the application is Provide message logs in the same format for different business modules, and reflect the relationship of business flows through transaction identification numbers, which reduces the difficulty of message log processing and improves the accuracy of fault source location.

Through the above description of the implementation manners, those skilled in the art can clearly understand that the present invention can be implemented by software and necessary general-purpose hardware, of course, it can also be implemented by hardware, but in many cases the former is a better implementation. . Based on this understanding, the technical solution of this application essentially or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk. , Read-Only Memory (ROM), Random Access Memory (RAM), Flash memory (FLASH), hard disk or optical disk, etc., including several instructions to make a computer device (which can be a personal computer) , A server, or a network device, etc.) execute the method described in the embodiment of the present application.

It is worth noting that in the above embodiment of the log processing device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding function can be realized; in addition, each The specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of this application.

Those skilled in the art should understand that the term user terminal encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser, or a vehicle-mounted mobile station.

In general, the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

The embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code written in any combination of one or more programming languages or Object code.

The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) DVD or CD) etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), programmable logic devices (FGPA) And processors based on multi-core processor architecture.

By way of exemplary and non-limiting examples, a detailed description of the exemplary embodiments of the present application has been provided above. However, considering the accompanying drawings and claims, various modifications and adjustments to the above embodiments are obvious to those skilled in the art, but they do not deviate from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.

Claims

A log processing method, including:

Determine the transaction identification number of the business flow;

Generating a message log associated with the transaction identification number for the application module processing the service flow; and

Determine the source of the service failure according to the failure information of the message log.
The method according to claim 1, wherein said determining the transaction identification number of the service flow comprises:

Generate a check value according to the current system time through a preset check algorithm; and

A random number of the service flow is generated, and the transaction identification number of the service flow is generated according to the random number and the check value, wherein the transaction identification number is globally unique.
The method according to claim 1, wherein the generating a message log associated with the transaction identification number for the application module processing the service flow comprises:

Determine the corresponding message extraction rule according to the message message protocol of the application module;

Extract the message content of the service flow according to the message extraction rule; and

The content of the message and the transaction identification number of the service flow are associated and stored as a message log.
The method according to claim 3, wherein the associating and storing the message content and the transaction identification number as a message log comprises:

Storing the message content and the transaction identification number as a business message log; and

The business message logs of at least two of the application modules are read and combined as the message log.
The method according to claim 1, wherein the determining the source of the service failure according to the failure information of the message log comprises:

Acquiring log records in the message log to form a message queue; and

Obtain the fault information in the message queue and display it in a preset format to determine the source of the business fault.
The method according to claim 5, wherein said obtaining log records in said message log to form a message queue comprises:

Match the target log record in the message log according to a preset keyword, and store the target log record in the message queue; and

Filter the log records in the message queue according to preset filtering keywords.
The method according to claim 5, wherein the obtaining the fault information in the message queue and displaying it in a preset format to determine the source of the service fault comprises:

Sorting and displaying the log records in the message queue according to the order of the transaction identification number; and

The failure information in the log record is highlighted in red, where the failure information includes at least one of response failure information and timeout failure information.
A log processing device includes:

The identification determination module is used to determine the transaction identification number of the business flow;

A log generation module, configured to generate a message log associated with the transaction identification number for the application module processing the service flow; and

The log analysis module is used to determine the source of the business failure according to the failure information of the message log.
A device that includes:

One or more processors; and

Memory, used to store one or more programs;

When the one or more programs are executed by the one or more processors, the one or more processors implement the log processing method according to any one of claims 1-7.
A computer-readable storage medium having a computer program stored thereon, wherein the program is executed by a processor to implement the log processing method according to any one of claims 1-7.