Fault event processing method and device, equipment and storage medium
By receiving the root cause analysis results of fault events in the business system and retrieving the fault cause in the knowledge database to generate a processing solution, the problem of low efficiency in the business system is solved, and intelligent fault processing is achieved.
Patent Information
- Application Number
- CN202510217555.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-26
- Publication Date
- 2025-06-13
AI Technical Summary
With the continuous expansion and iterative update of business system functions, the frequency and complexity of fault events are increasing, and it is difficult for the existing technology to solve fault events efficiently.
By receiving the root cause analysis results for the target failure event, searching based on the fault cause in the preset knowledge database, obtaining the search results, and building the model based on this input prompt words, inputting them into the target model to generate a troubleshooting plan.
An intelligent generation of fault processing solution based on root cause analysis results is realized, and the overall processing efficiency of fault events is improved.
Smart Images
Figure CN120144792A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of data processing, and in particular, to a method, apparatus, device, and storage medium for processing fault events. Background Art
[0002] A fault event may refer to an event such as a running failure or a running result that does not match the expectation during the operation of a business system. Currently, with the continuous expansion and iterative update of the functions of business systems, the occurrence frequency of fault events is increasing day by day, and its complexity is also increasing.
[0003] Therefore, how to efficiently solve fault events has become an urgent technical problem to be solved currently. Summary of the Invention
[0004] To solve the above technical problem or at least partially solve the above technical problem, the present disclosure provides a method, apparatus, device, and storage medium for processing fault events.
[0005] In a first aspect, an embodiment of the present disclosure provides a method for processing a fault event, the method including:
[0006] Receiving a root cause analysis result for a target fault event; wherein, the root cause analysis result includes a fault cause corresponding to the target fault event;
[0007] Retrieving in a preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result; wherein, the retrieval result includes fault handling information corresponding to the fault cause;
[0008] Constructing a model input prompt word based on the retrieval result and the fault cause corresponding to the target fault event, and inputting the model input prompt word into a first target model, and outputting a fault handling solution corresponding to the target fault event after being processed by the first target model; wherein, the fault handling solution is used to handle the target fault event.
[0009] In an optional implementation manner, the root cause analysis result further includes log analysis information corresponding to the fault cause, and the log analysis information includes log line information corresponding to the fault cause. Before retrieving in the preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result, it further includes:
[0010] Obtaining log line content from a log file corresponding to the target fault event according to the log line information corresponding to the fault cause;
[0011] Correspondingly, retrieving in the preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result includes:
[0012] Retrieve in a preset knowledge database based on the cause of the target fault event and the content of the log line to obtain a retrieval result.
[0013] In an alternative implementation, before retrieving in the preset knowledge database based on the cause of the target fault event and the content of the log line to obtain a retrieval result, it further includes:
[0014] Obtain a target source code fragment from the source code file according to the content of the log line;
[0015] Correspondingly, retrieving in the preset knowledge database based on the cause of the target fault event and the content of the log line to obtain a retrieval result includes:
[0016] Retrieve in the preset knowledge database based on the cause of the target fault event, the content of the log line, and the target source code fragment to obtain a retrieval result.
[0017] In an alternative implementation, constructing a model input prompt based on the retrieval result and the cause of the target fault event includes:
[0018] Construct a model input prompt based on the retrieval result, the cause of the target fault event, and the content of the log line.
[0019] In an alternative implementation, before constructing a model input prompt based on the retrieval result and the cause of the target fault event, it further includes:
[0020] Identify the uniform resource locator (URL) link in the retrieval result, replace the URL link in the retrieval result with a preset locator, and record the correspondence between the preset locator and the URL link;
[0021] Correspondingly, after inputting the model input prompt into the target model and outputting the fault handling solution corresponding to the target fault event after the processing of the target model, it further includes:
[0022] Based on the correspondence between the preset locator and the URL link, replace the preset locator in the fault handling solution with the URL link.
[0023] In an alternative implementation, the retrieval result includes multiple document fragments. After retrieving in the preset knowledge database based on the cause of the target fault event to obtain a retrieval result, it further includes:
[0024] Determine a target document segment from the multiple document segments based on the vector similarity between the multiple document segments and the cause of the target fault event;
[0025] Correspondingly, constructing a model input prompt based on the retrieval result and the cause of the target fault event includes:
[0026] Construct a model input prompt based on the target document segment and the cause of the target fault event.
[0027] In an alternative embodiment, the method further includes:
[0028] Determine a target fault handling tool corresponding to the target fault event from a fault handling tool library according to the fault handling solution corresponding to the target fault event; the target fault handling tool is used to handle the target fault event.
[0029] In an alternative embodiment, the determining a target fault handling tool corresponding to the target fault event from a fault handling tool library according to the fault handling solution corresponding to the target fault event includes:
[0030] Perform similarity matching based on the fault handling solution corresponding to the target fault event and the description information of each fault handling tool in the fault handling tool library, and determine multiple fault handling tools from the fault handling tool library;
[0031] Input the description information of the multiple fault handling tools and the fault handling solution corresponding to the target fault event into a second target model, and output the tool information of the target fault handling tool corresponding to the target fault event after being processed by the second target model.
[0032] In a second aspect, the present disclosure provides a fault event processing device, and the device includes:
[0033] A receiving module, configured to receive a root cause analysis result for a target fault event; wherein, the root cause analysis result includes the cause of the target fault event;
[0034] A retrieval module, configured to retrieve in a preset knowledge database based on the cause of the target fault event to obtain a retrieval result; wherein, the retrieval result includes fault handling information corresponding to the cause;
[0035] A building block for constructing a model input prompt word based on the retrieval result and the fault cause corresponding to the target fault event, and inputting the model input prompt word into a first target model, and outputting a fault handling solution corresponding to the target fault event after being processed by the first target model; wherein, the fault handling solution is used to handle the target fault event.
[0036] In a third aspect, an embodiment of the present disclosure further provides an electronic device, where the electronic device includes: a processor; a memory for storing executable instructions of the processor; the processor is configured to read the executable instructions from the memory and execute the instructions to implement the fault event processing method provided by the embodiment of the present disclosure.
[0037] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is used to execute the fault event processing method provided by the embodiment of the present disclosure.
[0038] In a fifth aspect, the present disclosure provides a computer program product, where the computer program product includes computer programs / instructions, and when the computer programs / instructions are executed by a processor, the above-mentioned method is implemented.
[0039] The technical solution provided by the embodiment of the present disclosure has the following advantages compared with the prior art:
[0040] In the fault event processing method provided by the embodiment of the present disclosure, first, a root cause analysis result for a target fault event is received, where the root cause analysis result includes a fault cause corresponding to the target fault event, and then, a search is performed in a preset knowledge database based on the fault cause corresponding to the target fault event to obtain a search result, where the search result includes fault handling information corresponding to the fault cause. Subsequently, a model input prompt word is constructed based on the search result and the fault cause corresponding to the target fault event, and the model input prompt word is input into a first target model, and a fault handling solution corresponding to the target fault event is output after being processed by the first target model, where the fault handling solution is used to handle the target fault event.
[0041] In the fault event processing method provided by the embodiment of the present disclosure, a search result is obtained by searching for the fault cause corresponding to the target fault event, and a model input prompt word is constructed based on the search result and the fault cause, so as to use the first target model to obtain a fault handling solution for handling the target fault event. It can be seen that the embodiment of the present disclosure can intelligently generate a fault handling solution corresponding to the target fault event based on the root cause analysis result for use in handling the target fault event, thereby improving the overall processing efficiency of the target fault event. Description of the Drawings
[0042] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages and aspects of the various embodiments of the present disclosure will become more apparent. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic and the original elements and elements are not necessarily drawn to scale.
[0043] Figure 1 It is a schematic flowchart of a method for processing a fault event provided by an embodiment of the present disclosure;
[0044] Figure 2 It is a schematic flowchart of another method for processing a fault event provided by an embodiment of the present disclosure;
[0045] Figure 3 It is a schematic structural diagram of a device for processing a fault event provided by an embodiment of the present disclosure;
[0046] Figure 4 It is a schematic structural diagram of a device for processing a fault event provided by an embodiment of the present disclosure. Specific Embodiments
[0047] The embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.
[0048] It should be understood that the various steps recited in the method embodiments of the present disclosure can be executed in a different order and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.
[0049] As used herein, the term "comprising" and its variations are open-ended, i.e., "including but not limited to". The term "based on" is "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.
[0050] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or the interdependence relationship therebetween.
[0051] It should be noted that the modifications of "one" and "multiple" mentioned in this disclosure are illustrative rather than restrictive. Those skilled in the art should understand that unless clearly specified otherwise in the context, it should be understood as "one or more".
[0052] The names of the messages or information exchanged between multiple devices in the embodiments of this disclosure are only for illustrative purposes and are not used to limit the scope of these messages or information.
[0053] In related technologies, it is usually relied on manual experience, referring to knowledge bases in related fields, etc. to analyze fault events and locate the root causes of faults. However, this series of processes requires a large amount of time and labor costs and it is difficult to quickly find solutions to fault events.
[0054] With the continuous expansion and iterative update of the functions of business systems, the occurrence frequency of fault events is increasing day by day, and its complexity is also increasing day by day. Therefore, how to efficiently solve fault events has become a technical problem that urgently needs to be solved currently.
[0055] For this reason, the embodiments of this disclosure provide a method for processing fault events. Specifically, first, receive the root cause analysis result for a target fault event, where the root cause analysis result includes the fault cause corresponding to the target fault event. Then, perform a search in a preset knowledge database based on the fault cause corresponding to the target fault event to obtain a search result, where the search result includes the fault handling information corresponding to the fault cause. Subsequently, construct a model input prompt word based on the search result and the fault cause corresponding to the target fault event, and input the model input prompt word into a first target model. After being processed by the first target model, output the fault handling solution corresponding to the target fault event, where the fault handling solution is used to handle the target fault event.
[0056] In the method for processing fault events provided by the embodiments of this disclosure, a search result is obtained by searching for the fault cause corresponding to a target fault event, and a model input prompt word is constructed based on the search result and the fault cause, so as to use a first target model to obtain a fault handling solution for handling the target fault event. It can be seen that the embodiments of this disclosure can intelligently generate a fault handling solution corresponding to a target fault event based on the root cause analysis result for use in handling the target fault event, improving the overall handling efficiency of the target fault event.
[0057] Based on this, the embodiments of this disclosure provide a method for processing fault events, which will be introduced below in combination with specific embodiments.
[0058] Figure 1The flowchart of a fault event processing method provided by an embodiment of the present disclosure. This method can be executed by a fault event processing device, which can be implemented by software and / or hardware and is generally integrated in an electronic device. As Figure 1 shown, the method includes:
[0059] S101: Receive the root cause analysis result for the target fault event.
[0060] Among them, the root cause analysis result includes the fault cause corresponding to the target fault event. The target fault event can be the fault event that needs to be solved currently. This fault event can refer to an event with abnormal conditions such as operation failure or unexpected results during the operation of devices, systems, etc. The root cause analysis result of the target fault event can be the relevant conclusion obtained by analyzing the reasons for the occurrence of the target fault event. The present disclosure does not limit the acquisition process of the root cause analysis result.
[0061] The fault cause can refer to the root cause of the occurrence of the target fault event. The fault cause can be used to subsequently solve the target fault event. For example, the fault cause can be: unable to obtain A configuration information, resulting in operation failure.
[0062] S102: Retrieve in the preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result.
[0063] Among them, the retrieval result includes the fault handling information corresponding to the fault cause.
[0064] The preset knowledge database in the embodiment of the present disclosure is pre-set. The preset knowledge database can be used to store various types of information, and this information can cover multiple fields. Specifically, the preset knowledge database can include a document database and a Q&A database of relevant knowledge.
[0065] The retrieval result corresponds to the fault cause. The document fragment included in the retrieval result can be used to solve the fault cause, and the document fragment can include fault handling information such as solutions and relevant suggestions for handling the fault cause.
[0066] In an alternative implementation, when retrieving in the preset knowledge database based on the fault cause corresponding to the target fault event, retrieval can be performed based on multiple dimensions to ensure that the retrieval result is more comprehensive. Set the retrieval dimensions, and retrieve in the preset knowledge database based on different retrieval dimensions respectively, so as to obtain a retrieval result including document fragments with different dimension contents. Specifically, the retrieval dimensions can include retrieving by document title, specific content of the document, etc.
[0067] In an alternative embodiment, after retrieving based on the fault cause corresponding to the target fault event and obtaining the retrieval result, if it is detected that the retrieval result includes multiple document fragments, the document fragments in the retrieval result can be screened to improve the efficiency of subsequent model processing.
[0068] Specifically, vectorize each document fragment included in the retrieval result, and vectorize the fault cause corresponding to the target fault event, and calculate the vector similarity between each document fragment and the fault cause. Select the document fragments with vector similarity exceeding the preset threshold from multiple document fragments as the target document fragments. Then, construct a model input prompt based on the target document fragments and the fault cause corresponding to the target fault event. Among them, the preset threshold is a similarity value set in advance.
[0069] Based on the above embodiment, after obtaining the target document fragments, the target document fragments and the fault cause corresponding to the target fault event can be input into the third target model. After the processing of the third target model, the sorting result between the target document fragments is obtained, and at least one target document fragment is confirmed from the target document fragments based on the sorting result and the screening strategy for constructing the model input prompt, so as to further improve the similarity between the target document fragments and the fault cause. Among them, the screening strategy is a preset screening rule for document fragments. The screening strategy can be the default strategy, and the default strategy can be set based on historical experience. The default strategy can specifically be to select the target document fragments with higher rankings.
[0070] In an alternative embodiment, to improve the accuracy of the retrieval result, the log line content corresponding to the fault cause can also be obtained for retrieval based on the fault cause and the log line content. Specifically, when receiving the root cause analysis result for the target fault event, if it is detected that the root cause analysis result also includes the log analysis information corresponding to the fault cause, obtain the log file corresponding to the target fault event, and obtain the log line content from the log file according to the log line information. Among them, the log analysis information is the content obtained by analyzing the logs generated during the operation of the system, etc. The log analysis information includes the log line information corresponding to the fault cause. The log line information can be the log lines including information related to the fault cause, and the log line content is the log content corresponding to the log line information. The log line information includes information related to the fault cause. For example, the log line information can include the position of the fault cause in the log file.
[0071] Illustrate with an example as follows:
[0072] The log analysis information includes: Log line information: Log line 12 - 37 indicates that when executing the Y unit test, the test failed because the A configuration information could not be obtained;
[0073] Log line information: Log lines 42 - 67 indicate that when performing the XXX unit test, since the B file could not be obtained during the execution of the G unit test, the test failed.
[0074] Log line content: ERROR: An exception occurred in function A, XXXX.
[0075] It can be seen that the log analysis information includes two log line information, and each log line information includes the location of the cause of the failure in the log file. The log line information contains the log content corresponding to the log line information, and the log content is related to the cause of the failure.
[0076] After obtaining the cause of the failure and the log line content corresponding to the target failure event as described above, a retrieval is performed in a preset knowledge database based on the cause of the failure and the log line content to obtain a retrieval result. Among them, the retrieval method in the preset knowledge database based on the cause of the failure and the log line content can be to extract keywords from the cause of the failure and the log line content, construct a retrieval statement based on the extracted keyword information, and then perform a retrieval in the preset knowledge database based on the retrieval statement to obtain a retrieval result.
[0077] In an optional implementation manner, on the basis that the root cause analysis result includes the log analysis information corresponding to the cause of the failure, if the log analysis information includes multiple log line information corresponding to the cause of the failure, to further improve the accuracy of the retrieval result, it is also possible to obtain the log line information with a relatively high similarity to the cause of the failure from the multiple log line information. Specifically, calculate the similarity between each log line information in the log analysis information and the cause of the failure, and obtain the log line information whose similarity exceeds the preset similarity threshold for subsequent obtaining of the log line content from the log file.
[0078] On the basis of the above embodiment, if multiple log line information with similarities exceeding the similarity threshold is obtained, the multiple log line information can also be sorted based on the similarity, and the target log line information is obtained from the multiple log line information for subsequent retrieval in the preset knowledge database.
[0079] In practical applications, on the basis of the above embodiment, to further improve the accuracy of the retrieval result, it is also possible to obtain the target source code fragment on the basis of obtaining the log line content, so as to perform a retrieval based on the cause of the failure, the log line content, and the target source code fragment corresponding to the target failure event.
[0080] Specifically, after obtaining the fault cause and the log line content corresponding to the target fault event, if it is detected that the log line content contains information related to the target source code, a source code file is obtained based on the log line content, and a target source code fragment is obtained from the source code file. The source code file is the code file that causes the fault, and the target source code fragment may include the relevant code fragments where the fault cause occurs.
[0081] After obtaining the target source code fragment, a search is performed in a preset knowledge database based on the fault cause, the log line content, and the target source code fragment corresponding to the target fault event to obtain a search result.
[0082] S103: Construct a model input prompt word based on the search result and the fault cause corresponding to the target fault event, and input the model input prompt word into the first target model. After being processed by the first target model, the fault handling solution corresponding to the target fault event is output.
[0083] The fault handling solution is used to handle the target fault event.
[0084] The model input prompt word in the embodiment of the present disclosure is an input parameter of the first target model. The model input prompt word includes the search result retrieved based on the fault cause corresponding to the target fault event in the preset knowledge data and the fault cause. The first target model is used to generate a fault handling solution.
[0085] When the model input prompt word is input into the first target model, after being analyzed and processed by the first target model, a fault handling solution is output. The fault handling solution is an output parameter. The fault handling solution is used to solve the target fault event, and the fault handling solution can be a method or suggestion for solving the target fault event.
[0086] In an alternative implementation, to improve the accuracy of the generation result of the first target model, if it is detected that the root cause analysis result further includes log analysis information corresponding to the fault cause, log line content can also be obtained based on the log analysis information. After obtaining the log line information, the search result, the fault cause corresponding to the target fault event, and the log line content are used to construct a model input prompt word for input into the first target model.
[0087] Based on the above embodiment, in an alternative implementation, to further improve the accuracy of the generation result of the first target model, user role information and model constraint conditions can also be used to construct a model input prompt word and input it into the first target model. The user role information can be role information set for the model. The model constraint conditions can be restriction requirements set for the model. The model constraint conditions can include the structure, form, and language style requirements of the generation result.
[0088] In practical applications, during the process of constructing the model input prompt based on the retrieval result and the cause of the target fault event and inputting the model input prompt into the first target model for processing, if the above retrieval result contains the URL link, it may cause deviation in the processing and analysis of the first target model and affect the output result.
[0089] In an alternative implementation, since there may be a URL link in the retrieval result retrieved based on the cause of the target fault event, to prevent the first target model from generating an incorrect result by processing the URL link, it is also possible to identify the retrieval result before constructing the model input prompt based on the retrieval result retrieved based on the cause of the target fault event and the cause, and after identifying the URL link, perform replacement processing on the URL link to improve the reliability of the output result.
[0090] Specifically, identify the URL link in the retrieval result. If the URL link is found in the retrieval result, use the preset locator to replace the URL link to obtain the replaced retrieval result, and record the corresponding relationship between the preset locator and the URL link. The preset locator is an identification symbol for identifying the URL link. By recording the corresponding relationship between the preset locator and the URL link, it is clear which URL link the preset locator specifically replaces, for use in restoring the URL link later. The present disclosure does not limit the method for identifying the URL link.
[0091] Then, construct the model input prompt based on the replaced retrieval result and the cause of the target fault event, and input it into the first target model. After being processed by the first target model, the fault handling solution corresponding to the target fault event is output.
[0092] Based on the above embodiments, after obtaining the fault handling solution corresponding to the target fault event output after the processing of the first target model, it is also possible to restore the preset locator in the fault handling solution to facilitate the user's understanding of the fault handling solution and trace the fault handling solution. Specifically, identify the preset locator in the fault handling solution, and based on the corresponding relationship between the preset locator and the URL link, replace the preset locator in the fault handling solution with the URL link.
[0093] The fault event handling method provided by the embodiments of the present disclosure. Specifically, first, receive the root cause analysis result for the target fault event, where the root cause analysis result includes the fault cause corresponding to the target fault event. Then, retrieve in the preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result, where the retrieval result includes the fault handling information corresponding to the fault cause. Subsequently, construct a model input prompt word based on the retrieval result and the fault cause corresponding to the target fault event, and input the model input prompt word into the first target model. After being processed by the first target model, output the fault handling solution corresponding to the target fault event, where the fault handling solution is used to handle the target fault event.
[0094] In the fault event handling method provided by the embodiments of the present disclosure, a retrieval result is obtained by retrieving the fault cause corresponding to the target fault event, and a model input prompt word is constructed based on the retrieval result and the fault cause, so as to use the first target model to obtain a fault handling solution for handling the target fault event. It can be seen that the embodiments of the present disclosure can intelligently generate a fault handling solution corresponding to the target fault event based on the root cause analysis result for use in handling the target fault event, improving the overall handling efficiency of the target fault event.
[0095] In an alternative implementation, after constructing a model input prompt word based on the retrieval result retrieved in the preset knowledge database based on the fault cause corresponding to the target fault event and the fault cause, and inputting the model input prompt word into the first target model, and after the first target model processes it to output the fault handling solution corresponding to the target fault event, the target fault handling tool can also be determined based on the fault handling solution. The target fault handling tool corresponds to the target fault event, and the target fault event can be handled by the target fault handling tool. The target fault handling tool can, for example, include a configuration management tool, a network diagnosis tool, a task restart tool, etc.
[0096] Specifically, according to the fault handling solution corresponding to the target fault event, determine the target fault handling tool corresponding to the target fault event from the fault handling tool library. The fault handling tool library can contain various information related to fault handling tools. Specifically, the fault handling tool library can include the description information of each fault handling tool.
[0097] In an alternative implementation, the manner of determining the target fault handling tool corresponding to the target fault event according to the fault handling solution corresponding to the target fault event can determine the target fault handling tool through a similarity matching method.
[0098] Specifically, calculate the similarity between the calculated fault handling solution and the description information of each fault handling tool in the fault handling tool library, so as to determine multiple fault handling tools from the fault handling tool library. The description information of the fault handling tool may include information such as the name, features, functions, usage methods, and applicable situations of the fault handling tool. The applicable situation can be obtained based on historical successful cases.
[0099] Then, after determining multiple fault handling tools, input the description information of the multiple fault handling tools and the fault handling solution corresponding to the target fault event into the second target model. After being processed by the second target model, output the tool information of the target fault handling tool corresponding to the target fault event, and the tool information is used to identify the target fault handling tool. It is used to subsequently call the target fault handling tool to handle the target fault event. The second target model is used to determine the target fault handling tool.
[0100] After determining the target fault handling tool, in order to call the target fault handling tool to solve the target fault handling event, it is also necessary to obtain the parameter information of the target fault handling tool.
[0101] Specifically, the root cause analysis result corresponding to the target fault event, the fault handling solution, and the tool information of the target fault handling tool can be input into the fourth target model. After being processed by the fourth target model, output the parameter information of the target fault handling tool, and then generate an interaction control corresponding to the target fault handling tool based on the parameter information. The interaction control is used to trigger the call of the target fault handling tool, and then repair the target fault event.
[0102] To facilitate the understanding of the content of the above embodiments, the present disclosure also provides another fault event handling method. Refer to Figure 2 , which is a schematic flowchart of another fault event handling method provided by the embodiments of the present disclosure.
[0103] In an optional implementation, input the root cause analysis result of fault event A, and the root cause analysis result includes the fault cause corresponding to fault event A and the log analysis information corresponding to the fault cause.
[0104] In an optional implementation, after obtaining the log analysis information corresponding to the fault cause, if the log analysis information includes multiple log line information, calculate the similarity between each log line information and the fault cause, obtain the log line information whose similarity exceeds the preset similarity threshold, and obtain the log line content from the log file corresponding to fault event A according to the log line information.
[0105] In an alternative embodiment, after obtaining the cause of the fault and the content of the log line, keyword information is extracted from the cause of the fault and the content of the log line to construct a retrieval object, and then a retrieval is performed in the knowledge database based on the retrieval statement to obtain a retrieval result.
[0106] In an alternative embodiment, if the retrieval result includes multiple document fragments, vectorization processing is performed on each of the document fragments and the retrieval object to obtain the vector similarity between each document fragment and the retrieval object, and a target document fragment is determined based on the vector similarity.
[0107] In an alternative embodiment, after obtaining the target document fragment as described above, the target document fragment and the retrieval object are input into a third target model, and after being processed by the third target model, a sorting result between the target document fragments is obtained, and a target document fragment object is confirmed from the target document fragments based on the sorting result and a screening strategy.
[0108] In an alternative embodiment, to avoid deviation in the processing and analysis by the first target model and affect the output result, it is also possible to perform identification processing on the target document fragment object included in the retrieval result. Specifically, the uniform resource locator (URL) link of the target document fragment object is identified. If the URL link exists in the target document fragment object, the URL link is replaced with a preset locator to obtain a replaced target document fragment object, and the corresponding relationship between the preset locator and the URL link is recorded.
[0109] In an alternative embodiment, a model input word is constructed based on the replaced target document fragment object, the retrieval object, the role description information, and the model constraint conditions, and is input into the first target model. After being processed by the first target model, a fault handling solution corresponding to the fault event A is output.
[0110] Based on the above embodiments, after obtaining the fault handling solution, the preset locator in the fault handling solution is identified, and based on the corresponding relationship between the preset locator and the uniform resource locator (URL) link, the preset locator in the fault handling solution is replaced with the URL link to obtain a replaced fault handling solution.
[0111] In an alternative embodiment, similarity matching is performed between the replaced fault handling solution and the description information of each fault handling tool in the fault handling tool library to determine multiple fault handling tools from the fault handling tool library.
[0112] In an alternative embodiment, after determining multiple fault handling tools, the description information of the multiple fault handling tools and the fault handling solution corresponding to fault event A are input into a second target model. After being processed by the second target model, the tool information of the target fault handling tool corresponding to fault event A is output, and the tool information is used to identify the target fault handling tool.
[0113] After determining the target fault handling tool, the fault cause, the log analysis information corresponding to the fault cause, the replaced fault handling solution, and the tool information of the target fault handling tool are input into a fourth target model. After being processed by the fourth target model, the parameter information of the target fault handling tool is output, and an interactive control corresponding to the target fault handling tool is generated and displayed on the interface. The interactive control is used to trigger the invocation of the target fault handling tool, thereby repairing fault event A.
[0114] To implement the above embodiments, the present disclosure also proposes a fault event processing device. Figure 3 As shown in the structural schematic diagram of a fault event processing device provided by an embodiment of the present disclosure, the device can be implemented by software and / or hardware and is generally integrated in an electronic device. Figure 3 As shown in the figure, the device includes:
[0115] A receiving module 301, configured to receive a root cause analysis result for a target fault event; wherein, the root cause analysis result includes a fault cause corresponding to the target fault event;
[0116] A retrieval module 302, configured to retrieve in a preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result; wherein, the retrieval result includes fault handling information corresponding to the fault cause;
[0117] A construction module 303, configured to construct a model input prompt word based on the retrieval result and the fault cause corresponding to the target fault event, and input the model input prompt word into a first target model. After being processed by the first target model, a fault handling solution corresponding to the target fault event is output; wherein, the fault handling solution is used to handle the target fault event.
[0118] In an alternative embodiment, the root cause analysis result further includes log analysis information corresponding to the fault cause, and the log analysis information includes log line information corresponding to the fault cause. The device further includes:
[0119] A first acquisition module, configured to acquire log line content from a log file corresponding to the target fault event according to the log line information corresponding to the fault cause;
[0120] Correspondingly, the retrieval module is specifically configured to:
[0121] Retrieve in a preset knowledge database based on the cause of the target fault event and the content of the log line to obtain a retrieval result.
[0122] In an optional implementation manner, the device further includes:
[0123] A second acquisition module, configured to acquire a target source code segment from a source code file according to the content of the log line;
[0124] Correspondingly, the retrieval module is specifically configured to:
[0125] Retrieve in a preset knowledge database based on the cause of the target fault event, the content of the log line, and the target source code segment to obtain a retrieval result.
[0126] In an optional implementation manner, the construction module is specifically configured to:
[0127] Construct a model input prompt word based on the retrieval result, the cause of the target fault event, and the content of the log line.
[0128] In an optional implementation manner, the device further includes:
[0129] A first replacement module, configured to identify a Uniform Resource Locator (URL) link in the retrieval result, replace the URL link in the retrieval result with a preset locator, and record the correspondence between the preset locator and the URL link;
[0130] Correspondingly, the device further includes:
[0131] A second replacement module, configured to replace the preset locator in the fault handling solution with the URL link based on the correspondence between the preset locator and the URL link.
[0132] In an optional implementation manner, the retrieval result includes multiple document fragments, and the device further includes:
[0133] A first determination module, configured to determine a target document fragment from the multiple document fragments based on the vector similarity between the multiple document fragments and the cause of the target fault event;
[0134] Correspondingly, the construction module is specifically configured to:
[0135] Construct a model input prompt word based on the target document fragment and the cause of the target fault event.
[0136] In an optional implementation manner, the device further includes:
[0137] A second determination module, configured to determine a target fault handling tool corresponding to the target fault event from a fault handling tool library according to the fault handling solution corresponding to the target fault event; the target fault handling tool is used to handle the target fault event.
[0138] In an optional implementation manner, the second determination module includes:
[0139] A determination sub-module, configured to perform similarity matching based on the description information of each fault handling tool in the fault handling tool library and the fault handling solution corresponding to the target fault event, and determine multiple fault handling tools from the fault handling tool library;
[0140] An output sub-module, configured to input the description information of the multiple fault handling tools and the fault handling solution corresponding to the target fault event into a second target model, and output the tool information of the target fault handling tool corresponding to the target fault event after being processed by the second target model.
[0141] In the fault event handling device provided in the embodiments of the present disclosure, specifically, first, receive the root cause analysis result for the target fault event, where the root cause analysis result includes the fault cause corresponding to the target fault event, and then retrieve in a preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result, where the retrieval result includes the fault handling information corresponding to the fault cause. Subsequently, construct a model input prompt word based on the retrieval result and the fault cause corresponding to the target fault event, and input the model input prompt word into a first target model, and output the fault handling solution corresponding to the target fault event after being processed by the first target model, where the fault handling solution is used to handle the target fault event.
[0142] In the fault event handling method provided in the embodiments of the present disclosure, by retrieving the fault cause corresponding to the target fault event to obtain a retrieval result, and constructing a model input prompt word based on the retrieval result and the fault cause, so as to obtain a fault handling solution for handling the target fault event by using a first target model. It can be seen that the embodiments of the present disclosure can intelligently generate a fault handling solution corresponding to the target fault event based on the root cause analysis result for handling the target fault event, thereby improving the overall handling efficiency of the target fault event.
[0143] The fault event handling device provided in the embodiments of the present disclosure can execute the fault event handling method provided in any embodiment of the present disclosure, and has corresponding functional modules and beneficial effects for executing the method.
[0144] To implement the above embodiments, the present disclosure also provides a computer program product, including a computer program / instructions, which when executed by a processor implement the fault event processing method in the above embodiments.
[0145] In addition to the above methods and devices, the embodiments of the present disclosure also provide a computer-readable storage medium, in which instructions are stored. When the instructions run on a terminal device, the terminal device implements the fault event processing method described in the embodiments of the present disclosure.
[0146] In addition, the embodiments of the present disclosure also provide a fault event processing device, as shown in Figure 4 shown, may include:
[0147] A processor 401, a memory 402, an input device 403, and an output device 404. The number of processors 401 in the fault event processing device may be one or more. Figure 4 Here, one processor is taken as an example. In some embodiments of the present disclosure, the processor 401, the memory 402, the input device 403, and the output device 404 may be connected through a bus or other means. Among them, Figure 4 here, the connection through the bus is taken as an example.
[0148] The memory 402 can be used to store software programs and modules. The processor 401 runs the software programs and modules stored in the memory 402, thereby implementing various functional applications and data processing of the fault event processing device. The memory 402 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function, etc. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices. The input device 403 can be used to receive input digital or character information, and generate signal inputs related to the user settings and function controls of the fault event processing device.
[0149] Specifically, in this embodiment, the processor 401 will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby implementing various functions of the above fault event processing device.
[0150] It should be noted that in this document, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the said element.
[0151] The above are only specific embodiments of the present disclosure, enabling those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for handling a fault event, characterized in that: include: Receive a root cause analysis result for a target fault event; wherein the root cause analysis result includes a fault cause corresponding to the target fault event; Searching a preset knowledge database based on the fault cause corresponding to the target fault event to obtain a search result; wherein the search result includes fault handling information corresponding to the fault cause; A model input prompt word is constructed based on the retrieval result and the fault cause corresponding to the target fault event, and the model input prompt word is input into the first target model. After being processed by the first target model, a fault handling solution corresponding to the target fault event is output; wherein the fault handling solution is used to handle the target fault event.
2. The method according to claim 1, characterized in that The root cause analysis result also includes log analysis information corresponding to the fault cause, and the log analysis information includes log line information corresponding to the fault cause. Before the search result is obtained based on the fault cause corresponding to the target fault event in the preset knowledge database, the search further includes: Obtaining log line content from the log file corresponding to the target fault event according to the log line information corresponding to the fault cause; Accordingly, searching the preset knowledge database based on the fault cause corresponding to the target fault event to obtain the search result includes: A search is performed in a preset knowledge database based on the fault cause corresponding to the target fault event and the log line content to obtain a search result.
3. The method according to claim 2, characterized in that Before the search is performed in the preset knowledge database based on the fault cause corresponding to the target fault event and the log line content to obtain the search result, the method further includes: Obtain a target source code snippet from a source code file according to the log line content; Accordingly, the search is performed in the preset knowledge database based on the fault cause corresponding to the target fault event and the log line content to obtain the search result, including: A search is performed in a preset knowledge database based on the fault cause corresponding to the target fault event, the log line content, and the target source code fragment to obtain a search result.
4. The method according to claim 2 or 3, characterized in that: The constructing a model input prompt word based on the search result and the fault cause corresponding to the target fault event includes: A model input prompt word is constructed based on the search result, the fault cause corresponding to the target fault event and the log line content.
5. The method according to claim 1, characterized in that Before constructing a model inputting a prompt word based on the search result and the fault cause corresponding to the target fault event, the method further includes: Identify the uniform resource locator URL link in the search result, replace the URL connection in the search result with a preset locator, and record the corresponding relationship between the preset locator and the URL link; Correspondingly, after inputting the model input prompt word into the target model and outputting the fault handling solution corresponding to the target fault event after being processed by the target model, the method further includes: Based on the correspondence between the preset locator and the URL link, the preset locator in the fault handling solution is replaced with the URL link.
6. The method according to claim 1, characterized in that The search result includes a plurality of document fragments. After the search is performed in the preset knowledge database based on the fault cause corresponding to the target fault event and the search result is obtained, the search further includes: Determining a target document segment from the multiple document segments based on vector similarities between the multiple document segments and the fault causes corresponding to the target fault event; Accordingly, the step of constructing a model input prompt word based on the search result and the fault cause corresponding to the target fault event includes: A model input prompt word is constructed based on the target document segment and the fault cause corresponding to the target fault event.
7. The method according to claim 1, characterized in that The method further comprises: According to the fault handling solution corresponding to the target fault event, a target fault handling tool corresponding to the target fault event is determined from a fault handling tool library; the target fault handling tool is used to handle the target fault event.
8. The method according to claim 7, characterized in that The determining, according to the fault handling solution corresponding to the target fault event, from a fault handling tool library, a target fault handling tool corresponding to the target fault event comprises: Based on similarity matching between the fault handling solution corresponding to the target fault event and the description information of each fault handling tool in the fault handling tool library, a plurality of fault handling tools are determined from the fault handling tool library; The description information of the multiple fault handling tools and the fault handling solutions corresponding to the target fault event are input into the second target model, and the tool information of the target fault handling tool corresponding to the target fault event is output after being processed by the second target model.
9. A fault event processing device, characterized in that: The device comprises: A receiving module, configured to receive a root cause analysis result for a target fault event; wherein the root cause analysis result includes a fault cause corresponding to the target fault event; A retrieval module, used to search a preset knowledge database based on the fault cause corresponding to the target fault event to obtain a retrieval result; wherein the retrieval result includes fault handling information corresponding to the fault cause; A construction module is used to construct a model input prompt word based on the retrieval result and the fault cause corresponding to the target fault event, and input the model input prompt word into the first target model, and output the fault handling plan corresponding to the target fault event after processing by the first target model; wherein the fault handling plan is used to handle the target fault event.
10. An electronic device, characterized in that: The electronic device comprises: processor; a memory for storing instructions executable by the processor; The processor is used to read the executable instructions from the memory and execute the instructions to implement the fault event processing method described in any one of claims 1-8 above.
11. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and the computer program is used to execute the fault event processing method described in any one of claims 1 to 8.
12. A computer program product, characterized in that The computer program product comprises a computer program / instruction, and when the computer program / instruction is executed by a processor, the method according to any one of claims 1 to 8 is implemented.