Fault recovery method

Abstract

The invention discloses a fault recovery method. Relates to the field of artificial intelligence. The method comprises the following steps: acquiring alarm data information for carrying out fault description on a fault event; a data type matched with the alarm data information is determined, the data type comprises structured data and unstructured data, under the condition that the data type matched with the alarm data information is structured data, parameter identification is carried out on the alarm data information, and a self-healing strategy matched with the fault event is determined according to a parameter identification result; under the condition that the data type matched with the alarm data information is unstructured data, performing target format conversion on the alarm data information to obtain alarm filling information, and determining a self-healing strategy matched with the alarm filling information; and the fault event is subjected to fault recovery according to a self-healing strategy. Through the method and the device, the problem of low fault recovery efficiency in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence, and in particular, to a fault recovery method. Background Art

[0002] For operation and maintenance personnel, they often encounter production alarms (transaction errors, log errors, network, memory, etc.), and often need to analyze the root cause of the problem based on specific scenarios. It often takes a long time to locate a problem. After locating the problem, it is necessary to perform differentiated repairs based on the transaction scope affected by the alarm to maintain stable production operations.

[0003] Currently, production alarms often require long-term human intervention from alarm to problem location and then to problem solving. In the process of problem analysis, it is often necessary to query production data multiple times to locate the data range affected by the fault and accurately carry out data repair and other work. In other words, there is a technical problem of low fault recovery efficiency in the existing technology.

[0004] Currently, no effective solution has been proposed to address the problem of low fault recovery efficiency in related technologies. Summary of the invention

[0005] The main purpose of this application is to provide a fault recovery method to solve the problem of low fault recovery efficiency in related technologies.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a fault recovery method is provided. The method includes: obtaining alarm data information used to describe the fault event; determining the data type matching the alarm data information, wherein the data type includes structured data and unstructured data, and when the data type matching the alarm data information is structured data, performing parameter identification on the alarm data information, and determining the self-healing strategy matching the fault event according to the parameter identification result; when the data type matching the alarm data information is unstructured data, performing target format conversion on the alarm data information to obtain alarm filling information, and determining the self-healing strategy matching the alarm filling information; the fault event performs fault recovery according to the self-healing strategy.

[0007] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a fault recovery device is provided. The device includes: an acquisition unit, which acquires alarm data information used to describe the fault event; a first determination unit, which determines the data type matching the alarm data information, wherein the data type includes structured data and unstructured data; a second determination unit, which, when the data type matching the alarm data information is structured data, performs parameter identification on the alarm data information, and determines the self-healing strategy matching the fault event according to the parameter identification result; a third determination unit, which, when the data type matching the alarm data information is unstructured data, performs target format conversion on the alarm data information to obtain alarm filling information, and determines the self-healing strategy matching the alarm filling information; and an execution unit, the fault event performs fault recovery according to the self-healing strategy.

[0008] Optionally, the above-mentioned first determination unit includes: a parsing module, used to parse the alarm data information to determine the format description information that matches the alarm data information; determine the key field set that matches the alarm data information based on the format description information; perform type matching on the parameter value of each key field in the key field set with the field value at the corresponding position in the target format to obtain a type matching result; determine the data type that matches the alarm data information based on the type matching result.

[0009] Optionally, the above-mentioned parsing module includes: a first matching module, which is used to perform parameter identification on the alarm data information according to the data type that matches each key field indicated by the type matching result to obtain a parameter identification result; perform parameter mapping on each parameter value in the parameter identification result to obtain policy description information; and match the self-healing strategy according to the policy description information.

[0010] Optionally, the above-mentioned parsing module includes: a second matching module, used to extract features from the alarm data information to obtain feature description information; perform target format conversion based on the feature description information to obtain alarm filling information, wherein the target format conversion is used to fill in parameters according to a reference template; and determine a self-healing strategy that matches the alarm filling information.

[0011] Optionally, the second matching module includes: a conversion module, used to obtain attribute data indicated by the feature description information; map the attribute data with fields of corresponding attributes in the reference template, and convert the attribute data into a target format to obtain alarm filling information.

[0012] Optionally, the above-mentioned execution unit is also used to determine the fault recovery steps and at least one execution parameter matching each fault recovery step according to the self-healing strategy; and execute the fault recovery command matching each fault recovery step according to the execution parameters.

[0013] Optionally, the above-mentioned execution unit includes: a marking module, which is used to obtain alarm data information of the fault event when the matched self-healing strategy does not meet the target matching conditions; generate an alarm tag that matches the high priority according to the alarm data information, and a policy matching record; send a self-healing policy matching request according to the alarm tag, wherein the self-healing policy matching request includes a policy matching record.

[0014] In an embodiment of the present application, alarm data information used to describe a fault event is obtained, and a data type that matches the alarm data information is determined, wherein the data type includes structured data and unstructured data. When the data type that matches the alarm data information is structured data, parameter identification is performed on the alarm data information, and a self-healing strategy that matches the fault event is determined based on the parameter identification result; when the data type that matches the alarm data information is unstructured data, the alarm data information is converted into a target format to obtain alarm fill information, and a self-healing strategy that matches the alarm fill information is determined, thereby achieving the purpose of fault recovery of the fault event according to the self-healing strategy, thereby realizing the technical effect of automated fault recovery, and further solving the technical problem of low fault recovery efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0016] Figure 1 A hardware structure block diagram of a computer terminal for implementing a fault recovery method is shown;

[0017] Figure 2 is a flowchart of a fault recovery method provided according to an embodiment of the present application;

[0018] Figure 3 is a schematic diagram of a fault recovery method provided according to an embodiment of the present application;

[0019] Figure 4 is a schematic diagram of another fault recovery method provided according to an embodiment of the present application;

[0020] Figure 5 is a flowchart of another fault recovery method provided according to an embodiment of the present application;

[0021] Figure 6 is a schematic diagram of a fault recovery device provided according to an embodiment of the present application;

[0022] Figure 7 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0025] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following explanations:

[0026] NPL technology, the full name of which is Natural Language Processing, analyzes the structure and meaning of text so that computers can perform tasks such as answering questions, translating, summarizing, sentiment analysis, and text generation.

[0027] Example 1

[0028] According to an embodiment of the present application, a method embodiment of fault recovery is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0029] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG. 1 shows a hardware structure block diagram of a computer terminal (or mobile device) for implementing a fault recovery method. Figure 1As shown, the computer terminal 10 (or mobile device) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0030] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0031] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the fault recovery method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the above-mentioned fault recovery method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0032] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0033] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0034] Under the above operating environment, this application provides Figure 2 Fault recovery method shown. Figure 2 It is a flowchart of the fault recovery method according to Example 1 of the present application.

[0035] Step S101, obtaining alarm data information for describing a fault event;

[0036] Step S102: determining a data type that matches the alarm data information, wherein the data type includes structured data and unstructured data.

[0037] Step S103, when the data type matching the alarm data information is structured data, parameter identification is performed on the alarm data information, and a self-healing strategy matching the fault event is determined according to the parameter identification result;

[0038] Step S104, when the data type matching the alarm data information is unstructured data, convert the alarm data information into a target format to obtain alarm filling information, and determine a self-healing strategy matching the alarm filling information;

[0039] Step S105: The fault event is recovered according to the self-healing strategy.

[0040] As an optional implementation, in the above step S101, the above fault events include but are not limited to application crash, network connection interruption, hardware failure, storage failure, data loss, system log exception, database failure, etc.; optionally, the alarm data information for fault description of the fault event may include the type of fault, alarm level, alarm description (specific information of the fault), timestamp, occurrence location (may include server name, IP address), additional information (such as error log, stack trace, system status, etc.), and the system preset emergency rule number, for example: application service abnormal alarm information includes: alarm type: application service alarm; alarm level: high; alarm information: service [ServiceName] access timeout, error code 504, affecting all users; timestamp: 2023-04-05 14:32:05; occurrence location: server [Server1], IP address 192.168.1.100; additional information: stack trace or error log fragment; emergency rule number: A001.

[0041] Further, in step S102, the data type that matches the alarm data information is determined; it is understandable that unstructured alarm information is usually alarm content that appears in the form of free text, has no fixed format or structure, and may contain various descriptive information, error codes, timestamps, etc. At this time, it is necessary to call an artificial intelligence algorithm to identify which type of error it is.

[0042] For example, structured data can be a table, database text data, etc. Specifically, it can be a transaction processing service exception: "Alarm Type": "Application Service Exception", "Alarm Level": "High", "Service Name": "TransactionProcessor", "Error Code": "4001", "Error Description": "Transaction Processing Timeout", "Timestamp": "2023-04-10 15:23:47", "Occurrence Location": {"Server Name": "ServerA", "IP Address": "192.168.1.10", "Physical Location": "Data Center Area A"}, "Additional Information": {"Affected Transaction ID": [123456, 789012, 345678], "Stack Trace": "Stack trace at TransactionProcessor.java:123", "System Load": {"CPU Usage": 85, "Memory Usage": 90};

[0043] Unstructured data can be text data, image data, etc. Unstructured alarm data usually comes from application logs, system logs, or free text reports of monitoring tools: for example, plain text [2023-04-10 15:24:03] ERROR in file TransferManager.log: Transfer to server B failed. Connection refused. Tried reconnecting but the issue persists. Last successful transfer was at 15:23:55. Suspect network issue or server B being down. Recommend checking network status and server B's availability. The above content is a log entry from the file transfer manager, which includes the time, description, possible cause, and recommended action of the error, but there is no clear definition of fields and data types.

[0044] Optionally, in the above step S103, when the data type matching the alarm data information is structured data, parameter identification is performed on the alarm data information, and a self-healing strategy matching the fault event is determined based on the parameter identification result. Taking the structured data in step S1012-2 as an example, parameter identification determines that the type of the fault event is "application service alarm", high level, service name (for example, PaymentService), error code "504" (for example, indicating a gateway timeout, that is, the server timed out while waiting for another service response), affecting all users, timestamp "2023-04-05 14:32:05", the physical location and network location of the fault are "server [Server1], IP address 192.168.1.100", and the query number for fault recovery is "A001".

[0045] To match the self-healing strategy, you can use "Emergency Rule Number: A001" as the query condition to retrieve the corresponding self-healing strategy from the self-healing strategy library. It should be noted that the self-healing strategy A001 may include multiple recovery operations, such as restarting services, checking dependent service status, performing health checks, adding service instances, adjusting network configurations, etc. Figure 3It is a table describing the fault event, including the fault event error type, error code, error specific description, parameter information involved, corresponding emergency rule number and emergency status. According to the priority and applicable conditions of the policy, analyze whether it is suitable for the current fault scenario one by one. It can be understood that the policy execution process involves executing the policy according to the identified parameters, such as checking the configuration information of the network address.

[0046] As an optional implementation, in the above step S104, when the data type matching the alarm data information is unstructured data, the alarm data information is converted into a target format to obtain alarm filling information, and a self-healing strategy matching the alarm filling information is determined. Specifically, a structured information template or database can be constructed based on the extracted features. Then, the information in the unstructured text is filled into the template or database to generate structured alarm information. This can be achieved through rule matching, machine learning algorithms, or deep learning models.

[0047] Specifically, an implementation method is used to convert the target format of the alarm data information to obtain the alarm filling information: first preprocessing, including text clarity, word segmentation and part-of-speech tagging, and entity recognition, and then feature extraction and template construction. Specifically, keywords or phrases are extracted from the preprocessed text. These keywords may be related to the alarm type, level, and description. Based on common failure modes and alarm types, one or more templates are constructed, each of which represents a specific alarm type. The fields contained in the template, such as service name, error code, impact range, timestamp, etc., will be used for subsequent filling and matching.

[0048] Further template filling maps the information in the unstructured text to the corresponding fields of the template based on the results of feature extraction, for example: markdown original log: [2023-04-10 15:24:03] ERROR in file TransferManager.log: Transfer to server B failed. Connection refused. Tried reconnecting but the issue persists. Last successful transfer was at 15:23:55. Suspect network issue or server B being down. Recommend checking network status and server B's availability. After preprocessing and feature extraction, the following template can be filled in: "Alarm Type": "Network Connection Failure", "Alarm Level": "High", "Service Name": "TransferManager", "Error Description": "Transfer to server B failed. Connection refused.", "Timestamp": "2023-04-10 15:24:03", "Affected Scope": "All Users", "Potential Causes": ["Network Problem", "Server B Unavailable"], "Additional Information": {"Last Success Time": "2023-04-10 15:23:55", "Number of Recovery Attempts": 1.

[0049] Finally, determine the self-healing strategy that matches the alarm fill information. For example, if the matching strategy ID is "S001", the system will automatically try to redirect the service from the failed Server B to the backup server to restore service availability.

[0050] In the above step S105, the fault event is restored according to the self-healing strategy. Obtain the corresponding self-healing strategy. For example, if it is EVENT001, it is found that it is the following emergency processing process A00001, and then according to Figure 4 The configuration shown continues each step of data query, statement update, server restart, etc.

[0051] Through the above implementation mode, the alarm data information used to describe the fault event is obtained, and the data type matching the alarm data information is determined, wherein the data type includes structured data and unstructured data. When the data type matching the alarm data information is structured data, the alarm data information is parameter identified, and the self-healing strategy matching the fault event is determined according to the parameter identification result; when the data type matching the alarm data information is unstructured data, the alarm data information is converted into a target format to obtain alarm fill information, and the self-healing strategy matching the alarm fill information is determined, thereby achieving the purpose of fault recovery of the fault event according to the self-healing strategy, thereby realizing the technical effect of automated fault recovery, and further solving the technical problem of low fault recovery efficiency.

[0052] Optionally, in the fault recovery method provided in the embodiment of the present application, determining the data type matching the alarm data information further includes:

[0053] S1, parsing the alarm data information to determine the format description information matching the alarm data information;

[0054] S2, determining a key field set matching the alarm data information according to the format description information;

[0055] S3, performing type matching on the parameter value of each key field in the key field set and the field value at the corresponding position in the target format to obtain a type matching result;

[0056] S4, determining the data type that matches the alarm data information according to the type matching result.

[0057] In the above steps S1-S3, the alarm data information is parsed to determine the format description information that matches the alarm data information; the key field set that matches the alarm data information is determined based on the format description information; the parameter value of each key field in the key field set is type matched with the field value at the corresponding position in the target format to obtain a type matching result; and the data type that matches the alarm data information is determined based on the type matching result.

[0058] There may be multiple types of the above-mentioned format description information. For example, format description information A can be used to parse the alarm data information related to the database connection loss failure. The key field set contained in template A may be: Service Name: used to identify the service or application involved in the alarm information. Timestamp: records the specific time when the alarm event occurs. Error Description: describes the detailed information of the alarm, such as "database connection lost". Error Code: a specific error code, for example, "1045" indicates a database credential error. Suspected Cause: the cause of the failure inferred based on the alarm information, such as "database credential error". Impact Scope: describes the scope of users or services affected by the alarm. Emergency Rule ID: the preset emergency processing rule ID related to the alarm type.

[0059] Further, the parameter values ​​in the alarm data information are obtained according to the fields at different positions in the template, and it is further determined whether the data type of the extracted parameter value matches the parameter type at the corresponding position of the template. If the extracted parameter value type does not match the parameter type at the corresponding position of the template, it is determined that the alarm data information is unstructured data. If the corresponding parameter types all match, it means that the alarm data information is structured data. This is just an example.

[0060] Through the above technical features recorded in this application, fault alarm information is divided into structured data and unstructured data. For structured data, policy matching tags can be automatically identified and self-healing strategies can be executed. For unstructured data, key parameters can be accurately identified through multiple template parsing, and then effective self-healing strategies can be matched and executed to achieve automatic fault recovery. The system's processing capability and response speed for various alarm information are enhanced, the frequency of manual intervention is reduced, and the operation and maintenance efficiency and reliability of IT systems are improved.

[0061] Optionally, in the fault recovery method provided in the embodiment of the present application, parameter identification is performed on the alarm data information, and a self-healing strategy matching the fault event is determined according to the parameter identification result, further comprising:

[0062] S1, according to the data type matched with each key field indicated by the type matching result, parameter identification is performed on the alarm data information to obtain a parameter identification result;

[0063] S2, performing parameter mapping on each parameter value in the parameter identification result to obtain policy description information;

[0064] S3, matching the self-healing strategy according to the strategy description information.

[0065] In the above steps S1-S3, according to the data type that matches each key field indicated by the type matching result, the alarm data information is parameter identified to obtain a parameter identification result; parameter mapping is performed on each parameter value in the parameter identification result to obtain policy description information; and the self-healing policy is matched according to the policy description information.

[0066] As an optional implementation, for event alarms, the alarm information already contains special information to indicate the type of alarm. At this time, you only need to query the fault type self-healing strategy library to obtain the corresponding self-healing strategy. Figure 3 EVENT0001 in the above code is found to correspond to the emergency handling process A00001. Figure 4 The configuration in the table completes each step of data query, statement update, server restart, etc.

[0067] Alternatively, the most suitable strategy is determined based on the multiple parameters analyzed, for example, all parameters in the parameter identification result match the parameter types involved in strategy A, and strategy A is determined to be the self-healing strategy that matches the fault event.

[0068] Through the above-mentioned implementation methods recorded in this application, the type and level of the alarm can be determined, and the specific fault number can be located. According to the self-recovery strategy capability preset by the fault number, the data impact range can be automatically determined, and a fault repair script can be automatically generated based on the data impact range, thereby achieving self-healing of the fault and greatly improving the processing time of production faults.

[0069] Optionally, in the fault recovery method provided in the embodiment of the present application, the target format conversion is performed on the alarm data information to obtain the alarm filling information, and the self-healing strategy matching the alarm filling information is determined, which further includes:

[0070] S1, extracting features from the alarm data information to obtain feature description information;

[0071] S2, converting the target format according to the feature description information to obtain alarm filling information, wherein the target format conversion is used to fill the parameters according to the reference template;

[0072] S3, determine a self-healing strategy that matches the alarm filling information.

[0073] In the above steps S1-S3, feature extraction is performed on the alarm data information to obtain feature description information; target format conversion is performed according to the feature description information to obtain alarm filling information, wherein the target format conversion is used to fill parameters according to a reference template; and a self-healing strategy matching the alarm filling information is determined.

[0074] It should be noted that the feature description information obtained above may be obtained through text preprocessing: cleaning the alarm text and removing irrelevant noise information, such as timestamp, IP address, log level, etc., to make the text easier to analyze; keyword extraction: using NLP technology to identify keywords in the text, such as service name, error code, fault description, impact range, etc.; entity recognition: using entity recognition technology in NLP to identify entities mentioned in the alarm text, such as specific hardware devices, software components, users, etc. Semantic parsing: putting keywords and entities into context, parsing their semantics, and understanding the meaning of the alarm, for example, judging that "connection timeout" may be a network failure.

[0075] According to the needs of alarm processing, design a structured alarm information template, which contains fields related to fault handling, such as "alarm type", "alarm level", "service name", "error code", "timestamp", "impact scope", etc. Feature mapping: Map the keywords, entities and semantic parsing results obtained in the feature extraction process to the corresponding fields in the reference template. For example, map "PaymentService" to the "Service Name" field, and map "504" to the "Error Code" field. Format conversion: Ensure that the filled information meets the requirements of the target format, which may involve operations such as data type conversion, formatting date and time, and checking field length limits. Template filling: Fill in all extracted feature description information according to the designed reference template format to form complete alarm filling information.

[0076] According to the fields such as "alarm type" and "error code" in the filled information, the self-healing strategy library is queried to find the self-healing strategy that matches the current alarm. Alarm processing decision: Based on the filled information, the decision system can automatically determine whether the self-healing operation needs to be performed immediately or further manual review is required.

[0077] Through the above-mentioned implementation methods recorded in this application, unstructured data is deeply analyzed, and key information can be identified from a large amount of unstructured text data by using feature extraction. The unstructured information is further converted into a structured template through template filling, thereby improving the accuracy of the alarm information, and then automatically matching the preset rules or strategies, thereby realizing automated alarm response and fault recovery, and improving the efficiency of fault recovery.

[0078] Optionally, in the fault recovery method provided in the embodiment of the present application, converting the target format according to the feature description information to obtain the alarm filling information further includes:

[0079] S1, obtaining attribute data indicated by feature description information;

[0080] S2, mapping the attribute data with the fields of the corresponding attributes in the reference template, and converting the target format to obtain the alarm filling information.

[0081] In the above steps S1-S2, the attribute data indicated by the feature description information is obtained; the attribute data is mapped with the fields of the corresponding attributes in the reference template, and the target format is converted to obtain the alarm filling information.

[0082] It should be noted that the above attribute data can be data of attributes such as timestamp type data and string type data, and the extracted attribute data is mapped one by one with the fields in the designed reference template. For example, the extracted "PaymentService" is mapped to the "Service Name" field, "1045" is mapped to the "Error Code" field, and "2023-04-1015:24:03" is mapped to the "Timestamp" field. Format standardization: Format the mapped data to ensure that it meets the requirements of the target format. For example, convert the timestamp to the ISO 8601 standard format, and convert the service status to a predefined enumeration value (such as running, interrupted, recovered, etc.). Data type conversion: Convert the extracted attribute data to the correct data type according to the requirements of the target format. For example, convert the error code in text form to an integer type, and convert the impact range description to the number of users or service list. Integrity check: Verify that all template fields are correctly filled to ensure the integrity of the alarm filling information. If some fields cannot be directly obtained from the text, they may need to be filled with default values ​​or obtained through other means.

[0083] Through the above implementation methods recorded in this application, by mapping the unstructured feature description into the structured reference template, the system can unify the format of the alarm information so that all alarms follow the same structure and attributes, which is convenient for subsequent automated processing and analysis. The mapping and format conversion ensure the accuracy and consistency of the alarm information, speed up the analysis and understanding of the alarm, and thus improve the efficiency of the alarm response and fault recovery. That is, the original unstructured alarm data is accurately converted into structured alarm filling information, which is not only convenient for the system to understand and process, but also improves the efficiency and accuracy of the alarm processing.

[0084] Optionally, in the fault recovery method provided in the embodiment of the present application, the fault event is recovered according to the self-healing strategy, and further includes:

[0085] S1, determining a fault recovery step and at least one execution parameter matching each fault recovery step according to a self-healing strategy;

[0086] S2, executing the fault recovery command matching each fault recovery step according to the execution parameters.

[0087] In the above steps S1-S2, the fault recovery steps and at least one execution parameter matching each fault recovery step are determined according to the self-healing strategy; and the fault recovery command matching each fault recovery step is executed according to the execution parameter. For example, if the network connection abnormality self-healing strategy is matched, strategy step 1: detect the network connection status of the service. Execution parameters: the host name of the service (for example, app-server-01) and the IP address of the target server (for example, 192.168.1.100). Fault recovery command: use the ping command to detect network connectivity. bash ping-c4192.168.1.100; further execute strategy step 2: check whether the database connection credentials are correct. Execution parameters: service name, database server name, current database credentials. Fault recovery command: call the credential management system API to check and update the credentials. Then execute strategy step 3: restart the database connection of the service. Execution parameters: service name, database connection parameters (such as address, port). Fault recovery command: reinitialize the database connection through the service API.

[0088] Through the above-mentioned technical features recorded in this application, the parameter values ​​are automatically acquired according to the execution parameters preset in the execution steps specified by the matching recovery strategy, without the need for manual analysis and decision-making, thereby greatly shortening the fault recovery time.

[0089] Optionally, in the fault recovery method provided in the embodiment of the present application, before the fault event is recovered according to the self-healing strategy, the method further includes:

[0090] S1, when the matched self-healing strategy does not meet the target matching condition, obtain the alarm data information of the fault event;

[0091] S2, generating a matching high-priority alarm tag based on the alarm data information, and recording the policy matching;

[0092] S3: Send a self-healing policy matching request according to the alarm mark, wherein the self-healing policy matching request includes a policy matching record.

[0093] It should be noted that in the above steps S1-S3, when the matched self-healing strategy does not meet the target matching conditions, the alarm data information of the fault event is obtained; an alarm tag matching a high priority is generated according to the alarm data information, and a policy matching record is recorded; a self-healing strategy matching request is sent according to the alarm tag, wherein the self-healing strategy matching request includes a policy matching record. The above target matching conditions may be consistency of environment and context, non-conflicting execution order, available resources, complete execution parameters, etc. The above policy matching record may include relevant operation information, matching status, etc. in the process of matching the self-healing strategy.

[0094] Specifically, the above process may be: analyzing alarm information, such as error description, service name and timestamp, to obtain more contextual information about the fault; based on the analysis result, generating a high-priority alarm tag, which includes a detailed description of the fault, the policy ID that was not successfully matched, and the current environmental information of the system (for example, network status, database configuration status, etc.); based on the generated alarm tag and policy matching record, constructing a self-healing policy matching request, which includes information such as the alarm tag, service name, database server, and policy records that failed to initially match; the request may be sent to relevant operators, who manually perform fault recovery.

[0095] Through the above implementation methods recorded in this application, for the fault self-healing strategy that is not matched, the system needs to generate a self-healing strategy record to be supplemented, which will be supplemented later. In parallel, the alarm level needs to be upgraded to prompt manual intervention until the fault is restored. After the fault is handled, the self-healing strategy is supplemented to facilitate the next system self-healing process. Even in the case of an initial strategy mismatch, the fault handling process can be standardized to facilitate maintenance and improvement, and if the initial strategy does not work, the system will not blindly repeat invalid operations, but will re-initiate policy matching through a higher level alarm mark, avoiding unnecessary resource consumption.

[0096] The following is a flow chart Figure 5 Take this as an example to fully explain this solution:

[0097] S502, real-time monitoring of alarms (logs, availability, event alarms, network, memory, CPU, etc.); specifically, the device connects to system logs, system availability detection, receives event alarms, detects equipment failures, memory, CUP, etc. in real time, and detects related content in real time.

[0098] Data collection module: responsible for collecting data sources from various monitoring systems, application logs, network devices, etc., including system logs, application logs, alarms generated by monitoring tools, etc. These data will be used for subsequent analysis and processing. Among them: the alarms generated by the monitoring tool are structured data, and only the error code needs to be identified in the future, and the error information interface determines which type of error information it belongs to. Other application logs and system logs are unstructured data, which need to be identified by means and summarized into a category of data.

[0099] S504, intelligent analysis of alarm types and levels, and self-healing strategies; including S504-1 logs, S504-2 event alarms, etc.

[0100] For S512, no self-healing strategy is matched; S512-1, automatically generate a self-healing strategy to be supplemented; S512-2, alarm upgrade; S512-3, manual intervention. That is, for the self-healing strategy that is not matched, the system needs to generate a record of the self-healing strategy to be supplemented, and then supplement it later. In parallel, the alarm level needs to be upgraded, prompting manual intervention until the fault is restored. After the fault is handled, the self-healing strategy is supplemented so that the system can self-heal next time.

[0101] For S514, obtain the self-healing strategy; S514-1, locate the fault recovery parameters in a decision tree manner; S514-2, assemble the execution statement, and execute the self-healing strategy; S514-3, verify whether the execution is successful;

[0102] Specifically, for faults that obtain self-healing strategies, the first step is to obtain the self-healing strategy and obtain fault resolution parameters according to the preset mechanism. For restarting the server and other operations that do not require specific parameters, the self-healing strategy is directly executed. For fault parameters that need to be obtained, the parameters can be obtained from the log according to the parameter acquisition type, or specific parameters can be obtained from the database according to the statement. For parameters that need to be obtained from the log, the transaction-related information required for this fault recovery, such as transaction number, status, etc., can be obtained according to the log record. For information that needs to be obtained from the database, the database can be connected to query the required specific information. For the obtained information, if further acquisition is required, the loop can be nested until the required information is obtained. Assemble execution statements and verification statements, assemble executable self-healing scripts according to the key information obtained, or restart the application server and other specific operations. Execute the self-healing operation. For those that need to be backed up, the backup operation is performed first, then the self-healing steps are executed, and finally the self-healing results are verified.

[0103] It should also be noted that this solution also executes S514-4 to parse out key information based on specific information in the log or other alarm information; S514-5 to query data to obtain further parameter information required for executing the statement. The parameter information in S514-5 is further obtained according to the self-healing configuration based on the information parsed in S514-4, and after obtaining the parameter information, all the obtained parameters are returned to the self-healing strategy obtained in S514.

[0104] Finally, S516 is executed according to the strategies determined in the two situations to recover from the failure.

[0105] It should be noted that for unstructured data represented by logs, S506 needs to be executed to perform natural semantic recognition through logs to obtain the fault type; S506-1, historical learning information library.

[0106] Specifically, unstructured alarm information usually refers to alarm content that appears in the form of free text. They have no fixed format or structure and may contain various descriptive information, error codes, timestamps, etc. At this time, artificial intelligence algorithms need to be called to identify which type of error it is.

[0107] If it is a log alarm, first learn the alarm logs that have occurred in the past based on artificial intelligence and natural semantic recognition to generate a historical learning information library. When a new error log is sent, automatically match the alarm type to which this alarm belongs based on the current error information, and make an accurate match. And query the fault type self-healing strategy library based on the acquired alarm type to obtain the corresponding self-healing strategy.

[0108] The specific implementation method of the conversion from unstructured to structured can be: Data preprocessing: First, the unstructured alarm information needs to be preprocessed, including removing irrelevant information, word segmentation, and removing stop words, to reduce data noise and improve the accuracy of subsequent processing. Feature extraction and representation: Using NLP technology and deep learning models, key features are extracted from the preprocessed text and represented in a computer-understandable format (such as vectors, matrices, etc.). These features can include lexical features, syntactic features, semantic features, etc. Structured information generation: Based on the extracted features, a structured information template or database is constructed. Then, the information in the unstructured text is filled into the template or database to generate structured alarm information. This can be achieved through rule matching, machine learning algorithms, or deep learning models.

[0109] For structured data represented by event alarms, S508 needs to be executed to match the number sent by the event alarms. Specifically, if it is structured data, there is already a specific problem type (error identification code), and subsequently, it is considered that all error identification codes are caused by a common problem, and the relevant error logs are stored.

[0110] For example, for event alarms, the alarm information already contains special information to indicate the type of alarm. At this time, you only need to query the fault type self-healing strategy library to obtain the corresponding self-healing strategy. Figure 3 , Figure 4 If it is EVENT0001, the following emergency process A00001 is found, and then each step of data query, statement update, server restart, etc. is continued according to the following configuration.

[0111] Then, in S510, accurate strategy matching is performed in the fault type self-healing strategy library.

[0112] It should be noted that for some special fault types, multiple self-healing strategies may be matched. In this case, the system needs to automatically perform further detection and perform secondary or tertiary detection based on the information in the matched self-healing strategy library. For example, if the interface call does not provide service, there are two possibilities: network jitter interruption and provider server failure. Secondary detection is required to determine the specific fault type. Figure 4 Taking the table in the figure as an example, the first query operation is performed based on the parameters A and B in the alarm information. The omitted part in the middle may be the judgment based on the query result D. If D meets certain requirements, step N is executed. N is to update the data based on the query result and alarm information of step 1. Of course, other operations can also be performed here, such as restarting the application server, modifying the configuration file, etc.

[0113] The fault recovery method provided in the embodiment of the present application adopts a method of obtaining alarm data information used to describe the fault event, determining the data type that matches the alarm data information, wherein the data type includes structured data and unstructured data. When the data type that matches the alarm data information is structured data, parameter identification is performed on the alarm data information, and a self-healing strategy that matches the fault event is determined according to the parameter identification result; when the data type that matches the alarm data information is unstructured data, the alarm data information is converted into a target format to obtain alarm fill information, and a self-healing strategy that matches the alarm fill information is determined, thereby achieving the purpose of performing fault recovery on the fault event according to the self-healing strategy, thereby realizing the technical effect of automated fault recovery, and further solving the technical problem of low fault recovery efficiency.

[0114] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0115] Example 2

[0116] The embodiment of the present application also provides a fault recovery device. It should be noted that the fault recovery device of the embodiment of the present application can be used to execute the fault recovery method provided by the embodiment of the present application. The fault recovery device provided by the embodiment of the present application is introduced below.

[0117] According to an embodiment of the present application, a device for implementing the above fault recovery method is also provided, such as Figure 6 As shown, the device includes: an acquisition unit 602, which acquires alarm data information used for fault description of a fault event;

[0118] The first determining unit 604 determines a data type that matches the alarm data information, wherein the data type includes structured data and unstructured data.

[0119] The second determining unit 606 performs parameter identification on the alarm data information when the data type matching the alarm data information is structured data, and determines a self-healing strategy matching the fault event according to the parameter identification result;

[0120] The third determining unit 608, when the data type matching the alarm data information is unstructured data, converts the alarm data information into a target format to obtain alarm filling information, and determines a self-healing strategy matching the alarm filling information;

[0121] The execution unit 610 performs fault recovery according to the self-healing strategy for the fault event.

[0122] The fault recovery device provided in the embodiment of the present application adopts a method of obtaining alarm data information used to describe the fault event, determining the data type that matches the alarm data information, wherein the data type includes structured data and unstructured data. When the data type that matches the alarm data information is structured data, parameter identification is performed on the alarm data information, and a self-healing strategy that matches the fault event is determined according to the parameter identification result; when the data type that matches the alarm data information is unstructured data, the alarm data information is converted into a target format to obtain alarm fill information, and a self-healing strategy that matches the alarm fill information is determined, thereby achieving the purpose of fault recovery of the fault event according to the self-healing strategy, thereby realizing the technical effect of automated fault recovery, and further solving the technical problem of low fault recovery efficiency.

[0123] Optionally, in the fault recovery device provided in an embodiment of the present application, the above-mentioned first determination unit includes: a parsing module, used to parse the alarm data information to determine the format description information that matches the alarm data information; determine the key field set that matches the alarm data information based on the format description information; perform type matching on the parameter value of each key field in the key field set with the field value at the corresponding position in the target format to obtain a type matching result; and determine the data type that matches the alarm data information based on the type matching result.

[0124] Optionally, the above-mentioned parsing module includes: a first matching module, which is used to perform parameter identification on the alarm data information according to the data type that matches each key field indicated by the type matching result to obtain a parameter identification result; perform parameter mapping on each parameter value in the parameter identification result to obtain policy description information; and match the self-healing strategy according to the policy description information.

[0125] Optionally, the above-mentioned parsing module includes: a second matching module, used to extract features from the alarm data information to obtain feature description information; perform target format conversion based on the feature description information to obtain alarm filling information, wherein the target format conversion is used to fill in parameters according to a reference template; and determine a self-healing strategy that matches the alarm filling information.

[0126] Optionally, the second matching module includes: a conversion module, used to obtain attribute data indicated by the feature description information; map the attribute data with fields of corresponding attributes in the reference template, and convert the attribute data into a target format to obtain alarm filling information.

[0127] Optionally, the above-mentioned execution unit is also used to determine the fault recovery steps and at least one execution parameter matching each fault recovery step according to the self-healing strategy; and execute the fault recovery command matching each fault recovery step according to the execution parameters.

[0128] Optionally, the above-mentioned execution unit includes: a marking module, which is used to obtain alarm data information of the fault event when the matched self-healing strategy does not meet the target matching conditions; generate an alarm tag that matches the high priority according to the alarm data information, and a policy matching record; send a self-healing policy matching request according to the alarm tag, wherein the self-healing policy matching request includes a policy matching record.

[0129] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiment 1. It should be noted that the above modules or units may be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n), and the above modules may also be part of the device and may be run in the computer terminal 10 provided in the embodiment 1.

[0130] Example 3

[0131] An embodiment of the present application may provide an electronic device, Figure 7 is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 7 As shown, the electronic device may include: one or more ( Figure 7 (only one is shown) processor 702, memory 704, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0132] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0133] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: obtain alarm data information used to describe the fault event; determine the data type that matches the alarm data information, wherein the data type includes structured data and unstructured data, and when the data type that matches the alarm data information is structured data, perform parameter identification on the alarm data information, and determine the self-healing strategy that matches the fault event based on the parameter identification result; when the data type that matches the alarm data information is unstructured data, perform target format conversion on the alarm data information to obtain alarm fill information, and determine the self-healing strategy that matches the alarm fill information; the fault event performs fault recovery according to the self-healing strategy.

[0134] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: parse the alarm data information to determine the format description information that matches the alarm data information; determine the key field set that matches the alarm data information based on the format description information; perform type matching on the parameter value of each key field in the key field set and the field value at the corresponding position in the target format to obtain a type matching result; determine the data type that matches the alarm data information based on the type matching result.

[0135] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: perform parameter identification on the alarm data information according to the data type that matches each key field indicated by the type matching result to obtain a parameter identification result; perform parameter mapping on each parameter value in the parameter identification result to obtain policy description information; and match the self-healing strategy according to the policy description information.

[0136] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: extract features from the alarm data information to obtain feature description information; convert the feature description information into a target format to obtain alarm fill information, wherein the target format conversion is used to fill in parameters according to a reference template; and determine a self-healing strategy that matches the alarm fill information.

[0137] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: obtain the attribute data indicated by the feature description information; map the attribute data with the fields of the corresponding attributes in the reference template, and convert the target format to obtain the alarm filling information.

[0138] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: determine the fault recovery steps and at least one execution parameter matching each fault recovery step according to the self-healing strategy; and execute the fault recovery command matching each fault recovery step according to the execution parameter.

[0139] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: when the matched self-healing strategy does not meet the target matching conditions, obtain the alarm data information of the fault event; generate an alarm tag that matches the high priority according to the alarm data information, and record the policy matching; send a self-healing policy matching request according to the alarm tag, wherein the self-healing policy matching request includes a policy matching record.

[0140] By adopting the embodiment of the present application, there is provided a method of obtaining alarm data information used to describe a fault event, determining a data type that matches the alarm data information, wherein the data type includes structured data and unstructured data. By, when the data type that matches the alarm data information is structured data, parameter identification is performed on the alarm data information, and a self-healing strategy that matches the fault event is determined according to the parameter identification result; when the data type that matches the alarm data information is unstructured data, the alarm data information is converted into a target format to obtain alarm fill information, and a self-healing strategy that matches the alarm fill information is determined, thereby achieving the purpose of fault recovery of the fault event according to the self-healing strategy, thereby realizing the technical effect of automated fault recovery, and further solving the technical problem of low fault recovery efficiency.

[0141] It can be understood by those skilled in the art that Figure 7 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 7The structure of the electronic device is not limited. Figure 7 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 7 Different configurations are shown.

[0142] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0143] Example 4

[0144] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the fault recovery method provided in the first embodiment.

[0145] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0146] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing the program steps of the fault recovery method.

[0147] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0148] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0149] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0150] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0151] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0152] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0153] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A fault recovery method, characterized in that: include: Obtaining alarm data information for describing the fault event; Determine a data type that matches the alarm data information, wherein the data type includes structured data and unstructured data, In the case where the data type matching the alarm data information is the structured data, performing parameter identification on the alarm data information, and determining a self-healing strategy matching the fault event according to the parameter identification result; In a case where the data type matching the alarm data information is the unstructured data, converting the alarm data information into a target format to obtain alarm filling information, and determining the self-healing strategy matching the alarm filling information; The fault event is recovered according to the self-healing strategy.

2. The method according to claim 1, characterized in that The determining of the data type matching the alarm data information further includes: Parsing the alarm data information to determine format description information matching the alarm data information; Determine a key field set matching the alarm data information according to the format description information; Performing type matching on the parameter value of each key field in the key field set and the field value at the corresponding position in the target format to obtain a type matching result; The data type matching the alarm data information is determined according to the type matching result.

3. The method according to claim 2, characterized in that The performing parameter identification on the alarm data information and determining a self-healing strategy matching the fault event according to the parameter identification result also includes: According to the data type matched with each of the key fields indicated by the type matching result, the parameter identification is performed on the alarm data information to obtain the parameter identification result; Performing parameter mapping on each of the parameter values ​​in the parameter identification result to obtain policy description information; The self-healing strategy is matched according to the strategy description information.

4. The method according to claim 2, characterized in that The converting the alarm data information into a target format to obtain alarm filling information, and determining the self-healing strategy matching the alarm filling information, further includes: Extracting features from the warning data information to obtain feature description information; Performing the target format conversion according to the feature description information to obtain the alarm filling information, wherein the target format conversion is used to fill in parameters according to a reference template; Determine the self-healing strategy that matches the alarm filling information.

5. The method according to claim 4, characterized in that The converting the target format according to the feature description information to obtain the alarm filling information also includes: Acquiring attribute data indicated by the feature description information; The attribute data is mapped with the fields of the corresponding attributes in the reference template, and the target format conversion is performed to obtain the alarm filling information.

6. The method according to claim 1, characterized in that The fault event is restored according to the self-healing strategy, further comprising: Determine, according to the self-healing strategy, a fault recovery step and at least one execution parameter matching each of the fault recovery steps; A fault recovery command matching each of the fault recovery steps is executed according to the execution parameters.

7. The method according to claim 1, characterized in that Before the fault event is restored according to the self-healing strategy, the method further includes: When the matched self-healing strategy does not meet the target matching condition, obtaining the alarm data information of the fault event; Generate a high-priority alarm tag according to the alarm data information, and record the policy match; A self-healing policy matching request is sent according to the alarm mark, wherein the self-healing policy matching request includes the policy matching record.

8. A fault recovery device, characterized in that: include: An acquisition unit, which acquires alarm data information used for describing a fault event; A first determining unit is configured to determine a data type matching the alarm data information, wherein the data type includes structured data and unstructured data. a second determining unit, which, when the data type matching the alarm data information is the structured data, performs parameter identification on the alarm data information, and determines a self-healing strategy matching the fault event according to a parameter identification result; a third determining unit, which, when the data type matching the alarm data information is the unstructured data, converts the alarm data information into a target format to obtain alarm filling information, and determines the self-healing strategy matching the alarm filling information; The execution unit performs fault recovery according to the self-healing strategy for the fault event.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the fault recovery method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 7 when running.

11. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images