TW202209099A - Exception log processing method, electronic device,terminal device, cloud server and system - Google Patents

Abstract

An exception log processing method is applied to a terminal device. The exception log processing method includes collecting an exception log of the terminal device and comparing the exception log with log data on a cloud server, and determining whether there are log data matching the exception log, the log data includes an exception log description and a solution uploaded to the cloud server by one or more terminal devices. If there is log data matching the exception log, and the matching log data is obtained. An electronic device and a terminal device and a cloud server and a system are also disclosed.

Description

Exception log processing method, device, terminal device, cloud server and system

The present invention relates to the technical field of log processing, and in particular, to an abnormal log processing method, device, terminal device, cloud server and system.

Such as Internet service providers, enterprise platforms, research institutions, etc. all require a lot of computing requirements, and the operation platform that carries the requirements of storage, computing and network is called a data center. Data centers usually deploy a large number of devices, and the devices (software devices, hardware devices) in the data center will output logs. The logs are time-stamped footprints, record behaviors, conditions, and events. an important part of maintenance work. Faced with the generation of a large number of logs, manual auditing obviously greatly reduces the efficiency. Based on the limitations of manual auditing, many log analysis tools are derived. Existing log analysis tools only collect system event logs, trigger warning messages when problems occur, and do not provide solutions.

In view of this, it is necessary to provide an abnormal log processing method, device, terminal device, cloud server and system, which can provide a corresponding solution when a log problem occurs.

An embodiment of the present application provides an exception log processing method, which is applied to a terminal device , the exception log processing method includes:

collecting abnormal logs of the terminal device;

Compare the exception log with the log data on the cloud server and determine whether it is Whether there is log data matching the abnormal log, wherein the log data includes the description of the abnormal log and the solution method uploaded by one or more terminal devices to the cloud server; and

If there is log data matching the exception log, obtain the number of matching logs according to.

In some embodiments of the present application, the exception log is stored on the cloud server Compare the log data of the abnormal log and determine whether there is any log data matching the abnormal log, including:

obtain the keyword of the exception log; and

Compare the keyword of the exception log with the exception log description to determine Whether there is an exception log description that matches the exception log.

In some embodiments of the present application, the if there is a date matching the exception log log data, and obtaining the matching log data includes:

If there is an exception log description matching the exception log, obtain the matching exception log The solution description and/or the corresponding solution script corresponding to the constant log description.

In some embodiments of the present application, if there is an abnormal day matching the abnormal log log description, after obtaining the solution description and/or the corresponding solution script corresponding to the matching exception log description, it also includes;

When acquiring the solution script, detect whether there is an execution instruction;

The solution script is executed when the execution instruction is detected.

In some embodiments of the present application, the exception log processing method further includes:

Receive exception log descriptions and resolutions; and

When an upload instruction is detected, upload the abnormal log description and solution to the Cloud server, wherein the cloud server is a private cloud server or a public cloud server.

In some embodiments of the present application, the collection of abnormal log packets of the terminal device include:

get keyword text;

Scan the log to be tested and detect the latest event information of the log to be tested; wherein, the log to be tested The test log includes the system log of Windows operating system or Linux operating system;

The exception log is filtered out according to the keyword text, wherein the exception log The event information is the latest current event information;

The exception log is stored.

An embodiment of the present application provides an exception log processing device, including: a collection module , a comparison module and a matching module, the collection module is used to collect the abnormal log of the terminal device; the comparison module is used to compare the abnormal log with the log data on the cloud server to determine whether there is Log data matching the abnormal log, wherein the log data includes the abnormal log description and solution method uploaded to the cloud server by one or more terminal devices; and the matching module is used to When the log data matching the exception log is obtained, the matching log data is obtained.

An embodiment of the present application provides a terminal device, including: one or more processors;

When one or more programs are executed by the one or more processors such that the one or multiple processors implement the exception log processing method described in any one of the above.

An embodiment of the present application provides an exception log processing method, including:

Obtain service access requests sent by terminal devices; and,

In response to the service access request, a connection is established with the terminal device, so that the The terminal device writes the abnormal log description and solution method and/or the terminal device reads the abnormal log description and solution method.

An embodiment of the present application provides a cloud server, including an acquisition module and a response module group; the acquisition module is used to acquire the service access request sent by the terminal device; and the response module is used to respond to the service access request and establish a connection with the terminal device, so that the terminal device writes Exception log description and solution and/or the terminal device reads the exception log description and solution.

An embodiment of the present application provides an exception log processing system, including a communication network, One or more of the above-mentioned terminal equipment and the above-mentioned cloud server, the terminal equipment is connected with the cloud server through the communication network.

An exception log processing method provided by the embodiment of the present application, according to the preset log Set rules to collect exception logs, compare the exception logs with the log data on the cloud server to determine whether there is log data matching the exception log, wherein the log data includes one or more terminal devices uploaded to In the abnormal log description and solution method of the cloud server, when there is log data matching the abnormal log, the matching log data is obtained. The abnormal log processing experience is collected through the cloud server, and the corresponding abnormal log processing experience can be obtained by accessing the cloud server. In this way, the exception log processing method, device, terminal device, cloud server, and system provided by the embodiments of the present application can save manpower and reduce debugging time.

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described and explained in detail below with reference to the accompanying drawings and embodiments. The following example illustrates the application environment of the exception log processing method.

Please refer to FIG. 1. FIG. 1 shows a schematic diagram of an exception log processing system provided by an embodiment of the present application. Schematic diagram of the application environment. As shown in FIG. 1 , the application environment includes an exception log processing system 100 and a user 200 . The exception log processing system 100 includes the cloud server 10, the communication network and one or more of the terminal devices 30. The user 200 can operate the terminal devices 30, and the terminal devices 30 pass the The communication network accesses the cloud server 10 .

The terminal device 30 may be of any type for establishing with the cloud server 10 Smart devices connected by communication, such as mobile phones, tablet computers, servers, etc. The terminal device 30 may be equipped with one or more different user interaction devices for collecting instructions from the user 200 or displaying and feeding back information to the user 200 . These interactive devices include, but are not limited to: buttons, displays, touch screens, speakers, and remote control joysticks. In the embodiment of the present application, the terminal device 30 may be a server of a data center, where a plurality of server cabinets are deployed in the data center, and each server cabinet is deployed with a plurality of servers, and the servers are connected to The communication network can communicate with the cloud server 10 through the communication network, so as to execute the exception log processing method of the embodiment of the present application.

Referring to FIG. 2, the terminal device 30 includes a memory 301, one or more processors 302. A first exception log processing device 303 stored in the memory 301 and running on the processor 302. The first exception log processing device 303 may be implemented as a first exception log processing routine. The daily log processing routine is executed by the one or more processors 302, so that the one or more processors 302 implement the steps in the exception log processing method embodiment executed by the terminal device 30, or, When the processor 302 executes the first exception log processing routine, the functions of the modules in FIG. 3 are implemented. The one or more modules may be a series of computer program instruction segments capable of accomplishing specific functions, and the instruction segments are used to describe the execution process of the first exception log processing routine in the first exception log processing device 303 . Those skilled in the art can understand that the schematic diagram is only an illustration of the terminal device 30 For example, it does not constitute a limitation on the terminal device 30, and may include more or less components than shown, or combine some components, or different components. For example, the terminal device 30 may also include an input display device , communication modules, bus bars, etc.

The processor 302 may be a central processing unit (Central Processing Unit, CPU), Other general-purpose processors 302, digital signal processors (DSPs) 302, application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor 302 can be a microprocessor 302 or the processor 302 can also be any conventional processor 302, etc. The processor 302 can use various interfaces and bus bars to connect various parts of the terminal device 30.

The memory 301 can be used to store the first exception log processing routine. Run or execute the computer program stored in the memory, and call the data stored in the memory to realize various functions of the terminal device 30 . Memory may include high-speed random access memory, and may also include non-volatile memory such as hard drives, internal memory, plug-in hard drives, Smart Media Cards (SMC), Secure Digital , SD) card, flash memory card (Flash Card), at least one disk memory device, flash memory device, or other volatile solid state memory device.

In the embodiment of the present application, the input display device is a user interaction device, A user interface is provided through the input display device. The user 200 can write data to the terminal device 30 through the user interface, and the terminal device 30 can output the read data of the cloud server 10 to the user 200 through the user interface .

Please refer to FIG. 3. FIG. 3 is the function of the preferred embodiment of the first exception log processing device of the present application. Energy module diagram.

As shown in FIG. 3 , the first abnormal log processing apparatus 303 may include a collection module 31. Comparing module 32 and matching module 33. In one embodiment, the above modules may be programmable software instructions stored in the memory 301 and invoked by the processor 302 to execute. It can be understood that, in other embodiments, the above-mentioned module can also be a program instruction or firmware (firmware) solidified in the processor 302, that is, the first exception log processing device 303 can also be stored in the processor 302.

The collection module 31 is used to collect abnormal days of the terminal device according to the preset log collection rules. Chi. In an embodiment of the present application, the preset log collection rules are rules set by the user 200 according to their needs, so as to collect abnormal logs that meet the conditions preset by the user 200 through the log collection rules. The collection module 31 collects a log that conforms to the preset log collection rule according to the preset log collection rule, and determines the log as an abnormal log. In an embodiment of the present application, the collection module 31 scans the system log of the terminal device 30 and detects the latest event information, wherein the system log includes a system event log, an application log and a security record file, Events generated by the baseboard management controller 11 (BMC) of the terminal device 30 are recorded in the system event log.

The comparison module 32 is used to compare the abnormal log with the log on the cloud server 10 The data are compared to determine whether there is log data matching the abnormal log, wherein the log data includes one or more abnormal log descriptions and solutions uploaded by the terminal device 30 to the cloud server 10 . In an embodiment of the present application, the comparison module compares the exception log with the log description on the cloud server 10 to determine whether there is an exception corresponding to the exception log in the cloud server 10 log description.

The matching module 33 is used to obtain log data matching the abnormal log when there is The matching log data. In an embodiment of the present application, when there is an abnormal log description corresponding to the abnormal log, the matching module 33 reads the solution description and the corresponding abnormal log description from the cloud server 10. / or the corresponding solution script.

The communication network may be based on any type of data transmission principle for establishing two The wireless communication network of the data transmission channel between the nodes, such as a Bluetooth network, a WiFi network, a wireless cellular network or a combination thereof located in different signal frequency bands.

The cloud server 10 can be any type of the cloud server in the network connection. server 10, such as: the cloud server 10 on the Internet, etc., after the cloud server 10 is connected to the terminal device 30 for communication, the cloud server 10 can provide the terminal device 30 with corresponding business services. The cloud server 10 may be a private cloud server or a public cloud server. In this embodiment of the present application, the cloud server 10 is a hardware device or hardware element for providing computing services. When the cloud server 10 is a public cloud server, the terminal device 30 may be a terminal device 30 of a different company or organization, and the corresponding user 200 is a user of a different company or organization. User 200. When the cloud server 10 is a private cloud server, the terminal device 30 is the terminal device 30 of the same company or organization, and the corresponding user 200 is also used by the same company or organization. 200.

Please refer to FIG. 4 , the cloud server 10 includes a controller 11 and is connected to the controller 11 The storage server 12 and the second exception log processing device 13 stored on the controller 11, the storage server 12 is used to provide data access for the terminal device 30, that is, the storage server 12 can be understood as The memory 301 with the function of storing data, for example, the storage server 12 stores the log descriptions and solutions uploaded by each of the terminal devices 30 , and then can access the storage server 12 to obtain the uploaded data from each of the terminal devices 30 . Log description and solution. Specifically, the controller 11 has logic processing capability, and is mainly used to provide computer services for the storage server 12 , that is, the controller 11 can be understood as the processor 302 of the cloud server 10 . The second exception log processing device 13 may be expressed as a second exception log processing routine, and the processor 302 implements the functions of each module in FIG. 5 when the processor 302 executes the second exception log processing routine. Alternatively, when the controller 11 can execute the second exception log processing routine, it implements the steps in the embodiment of the exception log processing method executed by the cloud server 10 .

In an embodiment of the present application, the second exception log processing routine may be divided into One or more modules, which are stored in the memory 301 and executed by the processor 302 . The one or more modules may be a series of computer program instruction segments capable of accomplishing specific functions, and the instruction segments are used to describe the execution process of the exception log processing routine in the cloud server 10 .

Please refer to FIG. 5. FIG. 5 is the location of the second exception log in this implementation manner of the embodiment of the present application. The functional module diagram of the management device. As shown in FIG. 5 , the second abnormal log processing apparatus 13 includes an acquisition module 101 and a response module 102 .

The obtaining module 101 is configured to obtain the service access request sent by the terminal device 30 . exist In the embodiment of the present application, the terminal device 30 sends a service access request to the cloud server 10 , and the obtaining module 101 of the cloud server 10 obtains the service access request sent by the terminal device 30 .

The response module 102 is used to respond to the service access request, and is configured with the terminal device 30 The connection is established, so that the terminal device 30 writes the abnormal log description and the solution method and/or the terminal device 30 reads the abnormal log description and the solution method. In the embodiment of the present application, when the cloud server 10 succeeds in the verification according to the server access request, the cloud server 10 allows the terminal device 30 to use the cloud service to establish a connection with the terminal device 30, The terminal device 30 can write the abnormal log description and solution method and/or read the abnormal log description and solution method from the cloud server 10 .

The working principle of the exception log processing system 100 in the application environment is briefly described below. Please refer to FIG. 6 , for example, the cloud server 10 is a public cloud server.

In the embodiment of the present application, the servers of different enterprises, different organizations or individuals are detecting When the abnormal log is reached, the user 200 is alerted, and the user 200 inputs the description of the abnormal log, the solution idea of the user 200 to the abnormal log, or the user 200 to the terminal device 30 through the user interaction device. The script written for processing the abnormal log is then uploaded by the terminal device 30 to the cloud server 10 through the communication network. Each user 200 can upload the log data to the cloud server 10 through the corresponding terminal device 30 , so as to collect the abnormal log information of each enterprise or each organization or individual through the cloud server 10 and Exception log handling experience.

As shown in FIG. 6 , in the exception log processing system, the terminal device 30 may include The terminal device A of the user of the organization A, the terminal device B of the user of the company B, and the terminal device C of the individual C, the terminal device 30 sends a service access request to the cloud server 10. In FIG. 4, the cloud After the controller 11 of the server 10 successfully authenticates the service access request, it establishes the connection between the cloud server 10 and the terminal device 30, and each user 200 communicates with the corresponding terminal device through the user interaction device. 30 Write log data, including the situation of each encountered abnormal log and the solution or solution idea or problem-solving script, the terminal device 30 uploads the log data received by the terminal device 30 to the cloud server through the communication network The storage server 12 of the cloud server 10 or the database of the storage server 12 , that is, the storage server 12 of the cloud server 10 stores the log data input by the user 200 , which is collected through the cloud server 10 The experience of each user 200 in solving the abnormal log can collect a large amount of data to analyze the abnormal log and provide experience in solving the problem. At the same time, the user 200 can obtain the relevant experience data from the cloud server 10 through the terminal device 30, Even if a script is obtained, when the terminal device 30 automatically executes the script, the problem can be quickly solved, the cost of system maintenance can be reduced, and manpower can be saved.

It can be understood that, in order to avoid leakage of secrets, what is uploaded to the cloud server 10 may only be The description of the abnormal log, the solution of the abnormal log by the user 200, or the script written by the user 200 to process the abnormal log, when the cloud server 10 is a private cloud service, the abnormal log can also be directly The log is uploaded as a case, which is not specifically limited in this application.

In this embodiment of the present application, each server H in the data center of enterprise D is executing In the abnormal log processing method of the present application, each server H in the data center automatically scans the system log, including the system event log, the application log and the security record file. The events generated by the system baseboard management controller 11 (BMC) of the server H are recorded in the system event log. The system log may be a system log of a Windows operating system or a Linux operating system. and store the collected abnormal log in the system log in the database or memory 301 corresponding to the server ID, such as the local file server database, and then store the abnormal log in the local file server database Comparing with the data on the database of the cloud server 10 to detect log data similar to the abnormal log, and when detecting the log data similar to the abnormal log, read the log data to obtain corresponding experience . The local file server database of each server can automatically detect and monitor when the event log is uploaded, and record the writing of the abnormal log.

Please refer to FIG. 7. FIG. 7 is a schematic diagram of an exception log processing method according to an embodiment of the present application. flow chart. The exception log processing method is applied to the cloud server 10. According to different requirements, the sequence of steps in the flowchart can be changed, and some steps can be omitted.

Step S00: Acquire a service access request sent by the terminal device.

It can be understood that the service access request carries the device information of the terminal device 30 and the Random sequence information. The device information is the unique identifier of the terminal device 30 , that is, a terminal corresponds to a unique piece of the device information, and the device information can be stored in the read only memory (ROM) of the terminal device 30 chip. The random sequence information is used for verification, and the random sequence information may be a hash value, which is not specifically limited in this application.

Step S01: responding to the service access request, establishing a connection with the terminal device, So that the terminal device writes the abnormal log description and the solution method and/or the terminal device reads the abnormal log description and the solution method.

The device information and the random sequence information are processed on the cloud server 10 When the verification is successful, the cloud server 10 opens the terminal device 30 to use cloud services, and the cloud server 10 establishes a connection with the terminal device 30, so that the terminal device 30 can write log data or read Get log data.

Please also refer to FIG. 8. FIG. 8 is an exception log processing according to another embodiment of the present application. Flowchart of the method. The exception log processing method is applied to the terminal device 30. According to different requirements, the sequence of the steps in the flowchart can be changed, and some steps can be omitted.

Step S10: Collect an exception log of the terminal device according to a preset log collection rule.

In an embodiment of the present application, the preset log collection rule is the user 200 according to It needs to be set to collect abnormal logs that conform to the rules preset by the user 200 through the log collection rules.

Please refer to FIG. 9 together, in at least one embodiment of the present application, the Log collection rules Collection exception logs include:

Step S11: Obtain keyword text.

In this embodiment of the present application, the preset log collection rule includes the keyword text In this case, the user 200 sets the system log to be an abnormal log when the keyword in the keyword text appears in the system log. Exemplarily, when "error", "fail" or "warning" occurs in the system log, the system log is judged as an abnormal log. For the BMC event log, when "Correctabl", "uncorrectable", "thermal" or "nmi" appears, the BMC event log is judged to be an abnormal log.

Step S12: Scan the log to be tested and detect the latest event information of the log to be tested; , the log to be tested includes the system log of the Windows operating system or the Linux operating system.

In the embodiment of the present application, the log to be tested is the system log of the terminal device 30 The system log includes a system event log, an application log and a security log, and events generated by the baseboard management controller 11 (BMC) of the terminal device 30 are recorded in the system event log. In an embodiment of the present application, the operating system of the terminal device 30 may be a Windows operating system or a Linux operating system.

Illustratively, the operating system of each server in the data center may be inconsistent, in When the operating system of the server is the Windows operating system, the abnormal log can be scanned and collected by the following method: the system log can be collected through the system log command line management tool wevtutil.exe built in the Windows operating system. When the operating system of the server is the Linux operating system, the system logs can be scanned and collected by the following methods: Scan and read the system logs through the log system on the Linux operating system. A standard for delivering log messages over the Internet Protocol (TCP/IP) network. Alternatively, obtain system logs through the dmesg program on Linux operating systems. For the BMC event log, you can use the command-line ipmi platform management tool (ipmitool) under the Linux operating system to obtain the BMC event log.

In an embodiment of the present application, the information of the system log changes in real time, and the system If the system log information is updated in real time, it is necessary to detect the latest event information of the log to be tested, so as to store the event information of the abnormal log as the current latest event information in the subsequent steps. In one possible implementation manner, when the system log is scanned, the result of the previous scan is compared to dump the latest event log when the system log information is updated.

In this embodiment of the present application, the terminal device 30 can not only handle abnormal system The abnormal BMC event log can also be processed. The BMC event log is an abnormal log. According to the abnormal BMC event log information stored on the cloud server 10, the abnormal BMC event log on the terminal device 30 is processed. deal with.

In the embodiment of the present application, the cloud server 10 can not only process The abnormal system log of the Windows operating system can also process the abnormal system log of the Linux operating system. The abnormal system log of the Windows operating system is processed according to the abnormal system log of the Windows operating system stored on the cloud server 10 . The abnormal system log of the Linux operating system is processed according to the abnormal system log of the Linux operating system stored on the cloud server 10 .

Step S13: Filter out the abnormal log according to the keyword text, wherein all the The event information in the exception log is the latest event information.

In this embodiment of the present application, for each system log on the terminal device 30, According to the line-by-line comparison of the keyword text, it is detected whether the system log includes one or more keywords in the keyword text, and when there are one or more keywords in the keyword file, the The system log is filtered out, and it is determined that the system log is an abnormal log.

Step S14: Store the exception log.

In this embodiment of the present application, the filtered abnormal logs are stored in the terminal device 30 The memory 301 or the database on the memory 301 corresponding to the ID, for example, a local file server database.

Specifically, the keyword text is input into each of the terminal devices 30, that is, input "Automatically filter keyword scripts", the terminal device 30 will automatically filter according to the keyword texts. The keyword text may be a txt file, including keywords such as "error", "fail", "warning", "Correctabl", "uncorrectable", "thermal" or "nmi", which are executed on the terminal device 30 When "Automatically filter keyword scripts", the system log will be automatically scanned, and then the system logs that store the keywords in the keyword text will be filtered out. After the first scan, the abnormal log will be stored in the next scan and compared with the previous one. The exception log is compared to the system log to store the latest events.

In an embodiment of the present application, step S10 is performed on the terminal device 30 according to the predetermined After the log collection rule is set to collect the abnormal log, the terminal device 30 can alert the user 200 of the abnormal information, so that the user 200 can process the abnormal log.

In an embodiment of the present application, the terminal device 30 will detect an abnormal log When the alarm information is sent to the user 200, so that the user 200 can process the abnormal log, the user 200 can click the “problems and solutions” window of the user interface of the terminal The terminal device 30 inputs an abnormal log description and a solution method about the daily log, for example, a brief description of the abnormal log event, including what system and what error occurred. The solution method may be the reason analysis of the abnormal log, the idea of how to solve the abnormal log, and the script for solving the abnormal log. For the Windows operating system, the AutoIT language is used to develop Windows scripts. For Linux operating systems, develop Linux scripts using the Shell scripting language. Then the user 200 clicks "Upload" on the user interface, and after receiving the upload instruction from the user 200, the terminal device 30 uploads the abnormal log description and the solution to the daily log through the communication network To the cloud server 10, wherein the cloud server 10 may be a private cloud server or a public cloud server.

In an embodiment of the present application, when the user 200 clicks the terminal device 30 When you open the "Problems and Solutions" window of the user interface, you can browse the descriptions and solutions of the exception logs uploaded to the cloud server 10 by other users 200, and you can search for keywords for a certain exception log to inquire about related issues by yourself. Exception log processing experience, and evaluate these exception log processing experience. Exemplarily, to display the error information (7000) event log for the Windows system, you can enter "Windows" and "7000" in the search box of the "Problems and Solutions" window, and the user 200 searches for the relevant experience by himself. 30 Access the cloud server 10 according to the search word in the search box, compare the title and problem description of the abnormal log on the cloud server 10 to detect the abnormal log description where the search word appears, and read the occurrence of the search word. The abnormal log description is displayed on the user interface, so that the user 200 can read all log information related to the abnormal log on the cloud server 10, and the user 200 can describe and solve each log. Methods were evaluated to determine the best answer.

In the embodiment of the present application, the first exception log processing routine of the embodiment of the present application is executed The terminal device 30 can upload the received abnormal log description and solution method to the cloud server 10, and collect information about each enterprise, each organization or each individual user 200 by providing the cloud server 10. Exception log processing experience.

After step S10 is executed, compared to the above-mentioned exception log handled by the user 200 by itself, The terminal device 30 may also perform step S20 to access and read the log data on the cloud server 10 through the terminal device 30 to obtain corresponding abnormal log processing experience.

Step S20: Compare the abnormal log with the log data on the cloud server Compare, wherein, the log data includes one or more abnormal log descriptions and solutions uploaded by the terminal device to the cloud server.

Please also refer to FIG. 10 , in at least one embodiment of the present application, the abnormal Comparing the log with the log data on the cloud server 10 includes:

Step S21: Acquire the keyword of the exception log.

Step S22: Compare the keyword with the exception log on the cloud server described for comparison.

In this embodiment of the present application, the keyword of the exception log may be the same as the keyword text The keywords in this document may be coincident or inconsistent, and the keywords of the exception log can be set according to actual experience, and the keywords of the exception log are the keywords used by the user 200 when describing the exception log. For example, when user 200 describes a system event exception log: error (7000), the record title is Windows system event log showing error information (7000), and its description is: The mst64 service cannot be started due to the following error, and the Windows system cannot Verify the index signature of this document. Then the words "Windows", "warning" and "7000" with high occurrence rate in the description can be keywords.

In the embodiment of the present application, after obtaining the keyword of the abnormal log, according to the The keyword compares the description of the exception log on the cloud server 10 line by line, including the title and content description of the exception log. In this embodiment of the present application, the log data uploaded by the user 200 to the cloud service may only be log events that occur, descriptions of the event logs, and solutions. In the embodiment of the present application, a fuzzy comparison method may be used to perform a fuzzy comparison of the keyword of the exception log with the title of the exception log and the description of the exception log line by line, so as to filter out the exception log data with the keyword. This is not specifically limited.

Step S30: When the comparison result matches, obtain the corresponding solution method.

In this embodiment of the present application, when the comparison results match, the corresponding solution description is obtained. description and/or corresponding solution scripts.

Please also refer to FIG. 11. In at least one embodiment of the present application, the exception log is The method also includes the following steps:

Step S31: When acquiring the corresponding solution script, detect whether there is an execution instruction. make.

Step S32: Execute the solution script when the execution instruction is detected.

In this embodiment of the present application, the terminal device 30 communicates with the cloud server 10 by itself. After comparing and determining the matching log data, the terminal device 30 reads the matching log data, displays the log data, and asks the user 200 whether to execute the log data when the corresponding solution script is included in the log data. The solution script. After reading the solution script, the user 200 can output execution instructions on the user interface. After receiving the execution instructions, the terminal device 30 automatically executes the solution script. In the embodiment of the present application, the Windows/Linux system event log and BMC event log are automatically collected through the cloud server 10, and then automatically stored in the database of the cloud server 10, and the keyword text is manually set by the user to automatically compare and filter Generate matching abnormal system event log/BMC event log, allow users to record how to troubleshoot the system and BMC event log, upload the recorded information to the cloud server, allow users to script the solution and upload to the database of the cloud server 10. Then it is automatically compared with the database of the cloud server 10, and the method for solving the problem is automatically listed. The user can write or operate the abnormal log according to the listed method for solving the problem, or choose to execute the listed solution. For the script in the problem method, the terminal device 30 executes the solution script by itself. You can also comment on solutions provided by other users on the cloud server, so that each user can learn how to troubleshoot. Users can choose automated scripts to quickly and easily resolve system problems. The cloud service provided by the cloud server is to provide an experience of common/centralized debugging of event logs and a problem-solving method. Therefore, the exception log processing method of the present application can save manpower, and can explain that the user 200 automatically filters the system and the BMC event log, quickly and easily automatically filters the failure log on the server, and then automatically analyzes the exception log and provides the best solution for the event. Best advice. This will help users reduce debugging time and save time in data center debugging events.

For those skilled in the art, it is obvious that the present application is not limited to the above-mentioned exemplary embodiments details, and the present application may be embodied in other specific forms without departing from the spirit or essential characteristics of the present application. Therefore, from any point of view, the above-mentioned embodiments of the present application should be regarded as exemplary and non-restrictive, as long as appropriate changes to the above-mentioned embodiments are made within the spirit and scope of the present application and variations should fall within the scope of protection claimed in this application.

100: Exception log processing system 200: user 10: Cloud server 30: Terminal equipment 301: Memory 302: Processor 303: The first abnormal log processing device 31: Collection module 32: Compare Mods 33: Matching modules 11: Controller 12: Storage Server 13: Second exception log processing device 101: Get Mods 102: Response module S10: Response module S00~S01: Steps S10~S30: Steps S11~S14: Steps S21~S22: Steps S31~S32: Steps

FIG. 1 is a schematic diagram of an application environment of an exception log processing system provided by an embodiment of the present application. FIG. 2 is a schematic diagram of a terminal device module provided by an embodiment of the present application. FIG. 3 is a functional module diagram of a preferred embodiment of the first exception log processing apparatus of the present application. FIG. 4 is a schematic diagram of a cloud server module according to an embodiment of the present application. FIG. 5 is a functional module diagram of the second exception log processing apparatus in this embodiment of the embodiment of the present application. FIG. 6 is a schematic diagram of a working principle of an exception log processing system in an application environment according to an embodiment of the present application. FIG. 7 is a flowchart of an exception log processing method according to an embodiment of the present application. FIG. 8 is a flowchart of an exception log processing method according to another embodiment of the present application. FIG. 9 is a flowchart of an exception log processing method according to another embodiment of the present application. FIG. 10 is a flowchart of an exception log processing method according to another embodiment of the present application. FIG. 11 is a flowchart of an exception log processing method according to another embodiment of the present application.

without

S10~S30: Steps

Claims (11)

An exception log processing method, applied to a terminal device, the improvement is that the exception log processing method includes: collecting abnormal logs of the terminal device; Compare the abnormal log with the log data on the cloud server, and determine whether there is log data matching the abnormal log, wherein the log data includes one or more terminal devices uploaded to the cloud server Exception log description and resolution for ; and If there is log data matching the exception log, obtain the matching log data. The abnormal log processing method according to claim 1, wherein the comparing the abnormal log with log data on a cloud server, and determining whether there is log data matching the abnormal log includes: obtain the keyword of the exception log; and The keyword of the exception log is compared with the exception log description to determine whether there is an exception log description matching the exception log. The abnormal log processing method according to claim 2, wherein, if there is log data matching the abnormal log, acquiring the matching log data includes: If there is an exception log description matching the exception log, obtain a solution description and/or a corresponding solution script corresponding to the matching exception log description. The exception log processing method according to claim 3, wherein, if there is an exception log description matching the exception log, after obtaining the solution description and/or the corresponding solution script corresponding to the matching exception log description ,Also includes; When acquiring the solution script, detect whether there is an execution instruction; The solution script is executed when the execution instruction is detected. The exception log processing method as described in request item 1, further comprising: Receive exception log descriptions and resolutions; and When an upload instruction is detected, the abnormal log description and the solution method are uploaded to the cloud server, wherein the cloud server is a private cloud server or a public cloud server. The abnormal log processing method according to any one of request items 1 to 5, wherein the collecting the abnormal log of the terminal device comprises: get keyword text; Scan the log to be tested and detect the latest event information of the log to be tested; wherein, the log to be tested includes the system log of the Windows operating system or the Linux operating system; Filter out the exception log according to the keyword text, wherein the event information of the exception log is the latest current event information; The exception log is stored. An exception log processing device, which is improved in that it includes: Collection module, used to collect abnormal logs of terminal equipment; A comparison module, used to compare the abnormal log with the log data on the cloud server, and determine whether there is log data matching the abnormal log, wherein the log data includes one or more terminal devices uploaded Exception log description and solution to the cloud server; and The matching module is used to obtain the matching log data when there is log data matching the abnormal log. A terminal device improved by comprising: one or more processors; When one or more programs are executed by the one or more processors, the one or more processors implement the exception log processing method described in any one of request items 1 to 6. An exception log processing method, which is improved in that it includes: Obtain service access requests sent by terminal devices; and, In response to the service access request, a connection is established with the terminal device, so that the terminal device writes the abnormal log description and the solution method and/or the terminal device reads the abnormal log description and the solution method. A cloud server, which is improved by including: The acquisition module is used to acquire the service access request sent by the terminal device; and, A response module, used to respond to the service access request and establish a communication connection with the terminal device, so that the terminal device can write the abnormal log description and solution method and/or the terminal device can read the abnormal log description and solution method. An exception log processing system, which is improved by comprising a communication network, one or more terminal devices as described in claim 8, and a cloud server as described in claim 10, the terminal devices passing through the communication network communicate with the cloud server.

Images