Fault handling method, device, storage medium, program product, and electronic device

Abstract

The present application discloses a fault handling method, device, storage medium, program product, and electronic device. Relating to the field of artificial intelligence, the method comprises: obtaining fault information of a system fault on a target platform to obtain target fault information; determining at least one reference text segment from multiple text segments based on the target fault information, wherein different text segments contain fault information and fault handling solutions for different system faults; processing the at least one reference text segment and the target fault information using a fault handling model to obtain target information, wherein the target information at least includes a target handling solution for the system fault on the target platform; and performing fault handling on the target platform based on the target handling solution in the target information. The method solves the technical problem of low reliability of fault handling when a platform fault occurs in related technologies.

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence, and more specifically, to a fault handling method, device, storage medium, program product, and electronic device. Background Art

[0002] In modern information technology systems, platforms (such as intelligent computing cloud platforms) serve as core infrastructure for data processing and operational support, and their stability and high availability are crucial. However, during platform operation, various failures are inevitable. These failures not only affect service continuity but can also cause serious damage to user data and operational operations. Currently, in related technologies, when a platform fails, manual processing of system failures is often relied upon. This approach relies on individual experience and expertise and is prone to misjudgments or omissions. Especially in complex fault diagnosis and emergency situations, manual processing may be difficult to ensure the accuracy of fault handling due to pressure and time constraints, resulting in low reliability of fault handling.

[0003] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0004] The embodiments of the present application provide a fault handling method, apparatus, storage medium, program product, and electronic device to at least solve the technical problem in related technologies of low reliability of fault handling when a platform fault occurs.

[0005] According to one aspect of an embodiment of the present application, a fault handling method is provided, including: obtaining fault information of a system fault of a target platform to obtain target fault information; determining at least one reference text segment from a plurality of text segments based on the target fault information, wherein different text segments contain fault information of different system faults and fault handling solutions; processing the at least one reference text segment and the target fault information through a fault handling model to obtain target information, wherein the target information at least includes a target handling solution for the system fault of the target platform; and performing fault handling on the target platform based on the target handling solution in the target information.

[0006] Furthermore, before determining at least one reference text segment from multiple text segments based on the target fault information, the method also includes: obtaining an operation and maintenance knowledge document of the target platform; for the system fault recorded in the operation and maintenance knowledge document, extracting the fault analysis results and fault handling solutions of the system fault from the operation and maintenance knowledge document; determining the fault information based on the system log corresponding to the system fault; generating different text segments based on the fault analysis results, fault handling solutions and fault information of different system faults to obtain multiple text segments.

[0007] Furthermore, a query text vector is determined based on the target fault information; a text vector corresponding to a text segment from the multiple text segments is obtained; and at least one reference text segment is determined from the multiple text segments based on the similarity between the query text vector and the text vector.

[0008] Furthermore, a first prompt statement is generated based on at least one reference text segment, target fault information and a preset first prompt template, wherein the first prompt statement is at least used to guide the fault handling model to generate a target fault analysis result and a target processing solution based on at least one reference text segment and the target fault information; the first prompt statement is input into the fault handling model, and the target fault analysis result and the target processing solution are obtained through the fault handling model; the target fault analysis result and the target processing solution are determined as target information.

[0009] Furthermore, a second prompt statement is generated based on the target information and a preset second prompt template, wherein the second prompt statement is used to guide the fault handling model to determine the source of the target information based on multiple text fragments; the second prompt statement is input into the fault handling model, and the source information corresponding to the target information is obtained through the fault handling model; when the source information represents that the target information belongs to multiple text fragments, the target platform is fault handled based on the target processing solution.

[0010] Furthermore, the text fragment includes a function identifier of an executable function corresponding to a fault handling solution. When the source information indicates that the target information belongs to multiple text fragments, performing fault handling on the target platform based on the target handling solution includes: determining the executable function corresponding to the target handling solution based on the function identifier corresponding to the target handling solution in the target information and the attribute information in the target database, wherein the target database is used to store the attribute information of the executable function; and performing fault handling on the target platform based on the executable function corresponding to the target handling solution.

[0011] Furthermore, the target processing solution includes at least a fault repair method, and performing fault processing on the target platform based on the target processing solution in the target information includes: performing fault repair processing on the target platform based on the first executable function in the executable functions corresponding to the target processing solution, wherein the first executable function is used to execute the fault repair method.

[0012] Furthermore, after performing fault repair processing on the target platform based on the first executable function in the executable function corresponding to the target processing scheme, the method also includes: if the target processing scheme also includes a repair verification method, performing repair verification processing on the target platform based on the second executable function in the executable function to obtain a repair verification result, wherein the second executable function is used to execute the repair verification method; in the case where the repair verification result indicates that the repair has failed, if the target processing scheme also includes a rollback method, performing rollback processing on the target platform based on the third executable function in the executable function, wherein the third executable function is used to execute the rollback method.

[0013] Furthermore, performing fault processing on the target platform based on the target processing solution in the target information includes: obtaining the fault level of the system fault of the target platform; determining the execution time point of the target processing solution based on the fault level; and performing fault processing on the target platform based on the target processing solution at the execution time point.

[0014] According to another aspect of an embodiment of the present application, a fault handling method is also provided, including: obtaining fault information of a system fault of a target platform uploaded by a client to obtain target fault information; determining at least one reference text segment from multiple text segments based on the target fault information in a cloud server, wherein different text segments contain fault information of different system faults and fault handling solutions; processing at least one reference text segment and target fault information through a fault handling model to obtain target information, wherein the target information at least includes a target handling solution for the system fault of the target platform; and feeding back the target information to the client, wherein the target information is used to instruct the client to perform fault handling on the target platform based on the target handling solution.

[0015] According to another aspect of an embodiment of the present application, a fault processing device is also provided, including: a first acquisition unit, used to acquire fault information of a system fault of a target platform to obtain target fault information; a determination unit, used to determine at least one reference text segment from multiple text segments based on the target fault information, wherein different text segments contain fault information and fault processing solutions of different system faults; a first processing unit, used to process at least one reference text segment and target fault information through a fault processing model to obtain target information, wherein the target information at least includes a target processing solution for the system fault of the target platform; and a second processing unit, used to perform fault processing on the target platform based on the target processing solution in the target information.

[0016] Furthermore, the fault processing device also includes: a second acquisition unit, used to obtain the operation and maintenance knowledge document of the target platform; a first extraction unit, used to extract the fault analysis results and fault handling solutions of the system fault recorded in the operation and maintenance knowledge document from the operation and maintenance knowledge document; a second extraction unit, used to determine the fault information based on the system log corresponding to the system fault; a generation unit, used to generate different text fragments according to the fault analysis results, fault handling solutions and fault information of different system faults to obtain multiple text fragments.

[0017] Furthermore, the determination unit includes: a first determination subunit, used to determine the query text vector based on the target fault information; a first acquisition subunit, used to obtain the text vector corresponding to the text segment among the multiple text segments; and a second determination subunit, used to determine at least one reference text segment from the multiple text segments based on the similarity between the query text vector and the text vector.

[0018] Furthermore, the first processing unit includes: a first generating subunit, used to generate a first prompt statement based on at least one reference text segment, target fault information and a preset first prompt template, wherein the first prompt statement is at least used to guide the fault processing model to generate a target fault analysis result and a target processing solution based on at least one reference text segment and the target fault information; a first processing subunit, used to input the first prompt statement into the fault processing model, and obtain the target fault analysis result and target processing solution through the fault processing model; a third determining subunit, used to determine the target fault analysis result and target processing solution as target information.

[0019] Furthermore, the second processing unit includes: a second generation subunit, used to generate a second prompt statement based on the target information and a preset second prompt template, wherein the second prompt statement is used to guide the fault handling model to determine the source of the target information based on multiple text fragments; a second processing subunit, used to input the second prompt statement into the fault handling model, and obtain the source information corresponding to the target information through the fault handling model; a third processing subunit, used to perform fault handling on the target platform based on the target processing solution when the source information represents that the target information belongs to multiple text fragments.

[0020] Furthermore, the text segment includes a function identifier of an executable function corresponding to the fault handling solution, and the third processing sub-unit includes: a determination module for determining the executable function corresponding to the target processing solution based on the function identifier corresponding to the target processing solution in the target information and the attribute information in the target database, wherein the target database is used to store the attribute information of the executable function; and a processing module for performing fault handling on the target platform based on the executable function corresponding to the target processing solution.

[0021] Furthermore, the target processing solution includes at least a fault repair method, and the second processing unit includes: a fourth processing sub-unit, which is used to perform fault repair processing on the target platform based on the first executable function in the executable function corresponding to the target processing solution, wherein the first executable function is used to execute the fault repair method.

[0022] Furthermore, the fault processing device also includes: a third processing unit, which is used to perform repair verification processing on the target platform based on the second executable function in the executable function to obtain a repair verification result if the target processing solution also includes a repair verification method, wherein the second executable function is used to execute the repair verification method; a fourth processing unit, which is used to perform rollback processing on the target platform based on the third executable function in the executable function when the repair verification result indicates that the repair has failed, if the target processing solution also includes a rollback method, wherein the third executable function is used to execute the rollback method.

[0023] Furthermore, the second processing unit includes: a second acquisition subunit, used to obtain the fault level of the system fault of the target platform; a fourth determination subunit, used to determine the execution time point of the target processing solution based on the fault level; and a fifth processing subunit, used to perform fault processing on the target platform based on the target processing solution at the execution time point.

[0024] According to another aspect of an embodiment of the present invention, an electronic device is provided, including: a memory storing an executable program; and a processor for running the program, wherein any one of the above-mentioned fault processing methods is executed when the program is running.

[0025] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, which stores a program, wherein when the program is running, the device where the storage medium is located is controlled to execute any of the above-mentioned fault processing methods.

[0026] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the computer program implements any one of the above-mentioned fault processing methods.

[0027] In an embodiment of the present application, target fault information is obtained by acquiring fault information of a system fault of a target platform; at least one reference text segment is determined from a plurality of text segments based on the target fault information, wherein different text segments contain fault information of different system faults and fault handling solutions; at least one reference text segment and the target fault information are processed by a fault handling model to obtain target information, wherein the target information at least includes a target handling solution for the system fault of the target platform; a method of performing fault handling on the target platform based on the target handling solution in the target information is combined with retrieval enhancement technology. When the fault information of the system of the target platform is obtained, relevant knowledge is first extracted from the plurality of text segments through information retrieval, and then the obtained relevant knowledge is injected into the fault handling model generation process. This "retrieval-generation" collaborative mode not only retains the logical reasoning and natural language generation capabilities of the model, but also breaks through the limitations of its static knowledge boundaries, thereby improving the accuracy of the generated target information, thereby improving the reliability of fault handling. Furthermore, by setting up different text segments to contain fault information and fault handling solutions for different system faults, the relevant information of the same system fault is aggregated in the same text segment, which improves the relevance of the content in the same text segment, thereby improving the retrieval accuracy in the retrieval process, and achieving the purpose of combining retrieval enhancement technology to generate fault handling solutions based on text segments with differentiated fault knowledge for fault handling, thereby achieving the technical effect of improving the reliability of fault handling, and thus solving the technical problem of low reliability of fault handling in related technologies when a platform failure occurs. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0029] Figure 1 is a schematic diagram of a computer terminal provided according to the first embodiment of the present application;

[0030] Figure 2 This is the process of the fault handling method provided in Example 1 of this application Figure 1 ;

[0031] Figure 3 This is the process of the fault handling method provided in Example 1 of this application Figure 2 ;

[0032] Figure 4 This is a flowchart of a fault handling method provided in accordance with the second embodiment of the present application;

[0033] Figure 5is a schematic diagram of a fault handling device provided in accordance with the third embodiment of the present application;

[0034] Figure 6 This is a structural block diagram of an electronic device provided according to Example 4 of the present application. DETAILED DESCRIPTION

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

[0036] 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 sequential order. 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 a sequence 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.

[0037] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

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

[0039] RAG (Retrieval-Augmented Generation): By combining dynamic knowledge retrieval with a generative model, the generative model can access external documents when answering questions, thereby providing accurate and rich responses based on relatively recent, contextually relevant knowledge.

[0040] Vector knowledge base: The vector knowledge base converts text data into high-dimensional vector form for storage, making semantic retrieval and similarity calculation more efficient and accurate, thereby improving the intelligence level of information retrieval.

[0041] Text chuncks: refers to the process of dividing long text into smaller semantic units or fragments to enable more precise matching of user queries and semantic analysis during information retrieval and processing, thereby enhancing the model's response accuracy and contextual relevance.

[0042] Example 1

[0043] According to an embodiment of the present application, a method for handling a fault 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.

[0044] 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 The following is a hardware block diagram of a computer terminal (or mobile device) for implementing a method for handling a fault. Figure 1 As shown, the computer terminal (or mobile device) 10 may include a processor set 102 (the processor set 102 may include but is not limited to a processing device such as a microcontroller unit (MCU) or a programmable logic device (FPGA), and the processor set 102 may include a processor set, Figure 1 102a, 102b, ..., 102n are used to illustrate), 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 can be included as one of the ports of the BUS), a network interface, a power supply and / or a camera. Those skilled in the art will understand 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 than shown, or with Figure 1 Different configurations shown.

[0045] It should be noted that the one or more processors 102 and / or other data processing circuitry described above may generally be referred to herein as "data processing circuitry." The data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, standalone processing module, or may be fully or partially integrated into any of the other components of the computer terminal 10 (or mobile device).

[0046] 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 handling 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, implementing the above-mentioned fault handling method. 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 instances, the memory 104 may further include a memory remotely located 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.

[0047] Transmission device 106 is used to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communications provider of computer terminal 10. In one embodiment, transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

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

[0049] In modern information technology systems, platforms (such as intelligent computing cloud platforms) serve as core infrastructure for data processing and operational support, and their stability and high availability are crucial. However, during platform operation, various failures are inevitable. These failures not only affect service continuity but can also cause serious damage to user data and operational operations. Currently, in related technologies, when a platform fails, manual processing of system failures is often relied upon. This approach relies on individual experience and expertise and is prone to misjudgments or omissions. Especially in complex fault diagnosis and emergency situations, manual processing may be difficult to ensure the accuracy of fault handling due to pressure and time constraints, resulting in low reliability of fault handling.

[0050] In the above technical background, the present application provides Figure 2 How to handle the fault shown. Figure 2 This is the process of the fault handling method provided in Example 1 of this application Figure 1 .like Figure 2 As shown, the method includes:

[0051] Step S201: Acquire fault information of a system fault on a target platform to obtain target fault information.

[0052] Optionally, electronic devices, application systems, servers and other devices may be used as the execution subject of the present application. In this embodiment, the target processing system is used as the execution subject to execute the aforementioned fault handling method.

[0053] Optionally, the target platform refers to a platform with data processing capabilities. For example, the target platform can be an intelligent cloud platform, a data center, or an Internet of Things platform. The target platform varies depending on the actual application scenario, so no specific limitation is made here.

[0054] Optionally, the system failure of the target platform includes, but is not limited to, hardware, software, or network-level failures detected in the target platform. Fault information of the system failure can be extracted from the system log. For example, when a fault occurs in the target platform during operation, the target platform or a detection system for fault detection on the target platform issues an early warning message. After receiving the early warning message, the target processing system collects the system early warning log (also referred to as the system log) of the target platform and extracts keywords from the system early warning log, thereby determining the keywords as fault information of the system failure of the target platform, that is, determining them as target fault information.

[0055] Optionally, the extracted keywords are used to describe the fault characteristics of the system fault. The keywords may include at least one of the following: error code, error message, system component name, timestamp, resource status, operation or command, host name or IP address, process ID, port number, etc., wherein a system error or exception usually has a specific error code, which is an identifier issued by the system or application when encountering a problem and is used to indicate the error type or location. The error message is used to describe the specific circumstances of the fault, such as memory overflow, connection timeout, file system corruption, certificate expiration, etc. The system component name refers to the name of the system component that failed. The timestamp refers to the time point when the fault occurred. The resource status is used to describe the current status of the system resources, such as disk full, CPU overload, etc. The operation or command refers to the operation that may cause the fault or the command being executed. The host name or IP address refers to the name or IP address of the physical host (or virtual host) where the fault occurred. The process ID refers to the ID of the process involved in the fault. The port number refers to the port number involved in the fault.

[0056] In an optional embodiment, the fault information also includes at least one of the following: the fault type and version information of the system fault. Optionally, the target processing system can determine the fault type of the target platform based on the system warning log or keywords extracted from the log. For example, a preset fault type identification rule is obtained, and the fault type identification rule includes the judgment conditions corresponding to each fault type. When the system warning log or keyword meets the judgment conditions of one of the fault types, the fault type is determined to be the fault type of the target platform. For another example, the system warning log or keyword is input into a fault classification model, and the fault type is determined by the fault classification model, and the fault classification model is a neural network model.

[0057] Optionally, the version information includes at least one of the following: a system version number and a component version number, wherein the system version number refers to the version number of the system where the failure occurs, and the component version number refers to the version number of the system component where the failure occurs.

[0058] In an optional embodiment, when a system failure is detected on the target platform, the target processing system may also generate a fault handling work order so as to record the target failure information and the process of handling the system failure in the work order for subsequent tracing.

[0059] Step S202: determining at least one reference text segment from a plurality of text segments based on the target fault information, wherein different text segments contain fault information and fault handling solutions of different system faults.

[0060] Optionally, the target processing system can use RAG technology to determine at least one reference text segment from multiple text segments. In the RAG framework, the vector knowledge base plays a key role. The vector knowledge base is a knowledge base that stores text data in the form of high-dimensional vectors. A piece of text, a document, or a knowledge unit is encoded into a numerical vector that captures the semantic information of the text, making semantic retrieval efficient and accurate. When a user initiates a query, the query content is also converted into a vector, and fast matching and similarity calculation are performed in the knowledge base to filter out more relevant knowledge entries. This vector-based semantic retrieval method is more intelligent than traditional keyword matching, and can understand and extract deeper semantic relationships, thereby providing accurate and context-related knowledge support for large models, significantly improving the quality and professionalism of generated results.

[0061] Therefore, in this embodiment, the target processing system can determine text vectors corresponding to multiple text segments and construct a vector knowledge base based on the text vectors corresponding to the multiple text segments. A vector matching operation is then performed in the vector knowledge base based on the target fault information to obtain at least one reference text segment. Optionally, the reference text segment refers to a text segment whose vector similarity with the target fault information is greater than a preset similarity.

[0062] Optionally, documents are pre-cleaned and sliced ​​during the construction of the vector knowledge base. In the RAG architecture, document slicing is an important step, which involves dividing the complete document into several smaller text units, called text chunks. The purpose of this is to improve the accuracy and efficiency of retrieval, because smaller text units are not only easier to match with user queries, but also can capture semantic details more finely. When a user initiates a query, the system searches the sliced ​​document set based on the query text, looking for chunks that are more semantically and content-related to the query text. This fine-grained retrieval method can inject more accurate and context-related knowledge into the large model generation process, ensuring the accuracy and reliability of the generated results. However, the size of the chunks and the relevance of the content in a single chunk have a significant impact on the accuracy of the retrieval results.

[0063] Therefore, in order to achieve more accurate and comprehensive knowledge retrieval and improve the appropriateness of the content in the text segment, in an optional embodiment, the fault information and fault handling solutions belonging to the same system fault are set in the same text segment, that is, different text segments contain fault information and fault handling solutions for different system faults.

[0064] In an optional embodiment, the system failure recorded in the text segment may be a system failure for the target platform. For example, the system failure recorded in the text segment is a system failure that has occurred on the target platform. For another example, the system failure recorded in the text segment is a system failure that may occur on the target platform.

[0065] In an optional embodiment, the system failure recorded in the text segment may be a system failure for at least one reference platform, where the reference platform refers to a platform whose system architecture similarity with the target platform is greater than a preset similarity, and the at least one reference platform may include the target platform. For example, the system failure recorded in the text segment is a system failure that has occurred on the reference platform.

[0066] In an optional embodiment, the fault information in the text segment includes at least keywords extracted from the system log corresponding to the system fault. The content format of the keywords is the same as that of the target fault information, so it is not repeated here.

[0067] In an optional embodiment, the fault information in the text segment may include, in addition to the aforementioned keywords, at least one of the following: the fault type and version information of the system fault, so as to improve the accuracy of knowledge retrieval.

[0068] In an optional embodiment, the aforementioned fault handling solution includes at least a fault repair method, wherein the fault repair method refers to a method for repairing a system fault, for example, the fault repair method may be restarting a service, applying a patch, adjusting configuration parameters, executing a specific script command, etc.

[0069] In an optional embodiment, the aforementioned fault handling solution may include, in addition to a fault repair method, at least one of a repair verification method and a rollback method. The repair verification method refers to a method used to verify whether the fault has been resolved after executing the fault repair method. For example, the repair verification method may include rechecking system logs, running diagnostic tools, executing health check scripts, etc. The rollback method is used to roll back the target platform system to restore it to its pre-fault repair state if the fault repair fails (e.g., if the fault is not resolved or side effects occur).

[0070] In an optional embodiment, the text fragment may also include a fault analysis result of the system fault, which is used to characterize the cause of the system fault. For example, an optional fault analysis result may be: "Due to insufficient disk space on the server, logging failed, which in turn caused the service to automatically restart."

[0071] Step S203 : Processing at least one reference text segment and target fault information through a fault processing model to obtain target information, wherein the target information at least includes a target processing solution for the system fault of the target platform.

[0072] Optionally, the fault handling model can be a large language model. Based on RAG technology, the target processing system can combine this proprietary technical knowledge (i.e., knowledge from text segments) with a general large model (i.e., a pre-trained large language model) to automatically analyze faults and generate solutions. RAG's semantic search capability accurately retrieves more relevant and timely remediation suggestions from a continuously updated vector knowledge base, thereby improving the efficiency and accuracy of platform fault handling.

[0073] In an optional embodiment, the target processing system can generate a prompt statement based on at least one reference text segment and target fault information, and then input the prompt statement into the fault processing model, so that the fault processing model performs fault analysis and solution generation on the target fault information based on at least one reference text segment to obtain the target information.

[0074] In an optional embodiment, the target information includes a target solution for the system failure of the target platform. The target solution includes at least a failure repair method and may also include at least one of the following: a repair verification method and a rollback method.

[0075] In an optional embodiment, when a text segment of a plurality of text segments includes a fault analysis result, the target information may include, in addition to the above-mentioned target processing solution, a target fault analysis result for a system fault of a target platform.

[0076] Step S204: performing fault processing on the target platform based on the target processing solution in the target information.

[0077] Optionally, after obtaining the target information, the target processing system may perform fault handling on the target platform based on the target handling solution in the target information. For example, an executable function corresponding to the target handling solution in the target information may be obtained, and then the executable function may be executed to handle the fault on the target platform. There may be at least one executable function, and the aforementioned fault handling may include at least performing fault repair processing on the target platform.

[0078] Optionally, the executable function corresponding to the target processing solution in the target information can be obtained based on a matching method. For example, if the target processing solution contains a function identifier corresponding to the solution, the target processing system can match the corresponding executable function's attribute information obtained from the target database based on the function identifier, thereby determining the executable function based on the attribute information. The target database stores attribute information of multiple executable functions.

[0079] Optionally, the executable function corresponding to the target processing solution in the target information can be obtained based on a generation method. For example, the target processing solution is input into a function generation model, which can be a pre-trained and fine-tuned large language model, so that the function generation model generates an executable function corresponding to the target processing solution.

[0080] In this solution, by incorporating retrieval enhancement technology, when system fault information for the target platform is obtained, relevant knowledge is first extracted from multiple text segments through information retrieval, and then the obtained relevant knowledge is injected into the fault handling model generation process. This "retrieval-generation" collaborative model not only retains the logical reasoning and natural language generation capabilities of the language model, but also breaks through the limitations of its static knowledge boundaries, improving the accuracy of the generated target information, thereby improving the reliability of fault handling. Furthermore, by setting different text segments to contain fault information and fault handling solutions for different system faults, relevant information for the same system fault is aggregated in the same text segment, improving the relevance of content within the same text segment, thereby improving retrieval accuracy during the retrieval process. This achieves the purpose of combining retrieval enhancement technology to generate fault handling solutions based on text segments that have differentiated fault knowledge for fault handling, achieving the technical effect of improving fault handling reliability and resolving the technical problem of low fault handling reliability in related technologies when platform faults occur.

[0081] How to improve the accuracy of the retrieval process in RAG is crucial. Therefore, in the fault handling method provided in Example 1 of the present application, before determining at least one reference text segment from multiple text segments based on the target fault information, the fault handling method also includes: obtaining the operation and maintenance knowledge document of the target platform; for the system fault recorded in the operation and maintenance knowledge document, extracting the fault analysis results and fault handling solutions of the system fault from the operation and maintenance knowledge document; determining the fault information according to the system log corresponding to the system fault; generating different text segments according to the fault analysis results, fault handling solutions and fault information of different system faults to obtain multiple text segments.

[0082] In an optional embodiment, the target platform's operation and maintenance knowledge document is used to record knowledge related to system failures that have occurred and been resolved on the target platform. For example, the target platform's operation and maintenance knowledge document includes failure analysis results and troubleshooting solutions for the target platform's system failure scenarios. In other words, the knowledge in the operation and maintenance knowledge document is verified professional knowledge and is reliable.

[0083] Optionally, the target platform's operation and maintenance knowledge document can be maintained by the user. For example, in the early stages of the operation and maintenance knowledge document's maintenance (i.e., when the document contains relatively little knowledge), if a system failure occurs on the target platform, the user can record the failure in the operation and maintenance knowledge document, analyze the failure, and obtain a fault analysis and troubleshooting plan, which they then record in the operation and maintenance knowledge document.

[0084] Optionally, the target platform's operation and maintenance knowledge document can be maintained by the target processing system. For example, in the later stages of the operation and maintenance knowledge document's maintenance (i.e., when the document contains relatively more knowledge), if a system failure occurs on the target platform, the target processing system will use RAG technology to determine the corresponding fault analysis and fault resolution plan for the system failure. It will then perform fault resolution on the target platform according to the fault resolution plan. If the fault is successfully repaired, the corresponding fault analysis and fault resolution plan will be recorded in the operation and maintenance knowledge document. Otherwise, the operation and maintenance knowledge document will not be updated.

[0085] In an optional embodiment, if the operation and maintenance knowledge document contains images, the target processing system may use OCR (Optical Character Recognition) to extract information from the images in the operation and maintenance knowledge document and then append the extracted textual information to the operation and maintenance knowledge document to obtain an updated operation and maintenance knowledge document. For example, the extracted textual information may be appended to a location adjacent to the image (e.g., below or above the image). Another example is the extraction of textual information to replace the corresponding image in the operation and maintenance knowledge document.

[0086] Optionally, after obtaining the operation and maintenance knowledge document (or an updated operation and maintenance knowledge document), the target processing system can extract the fault analysis results and fault handling solutions for the system fault recorded in the operation and maintenance knowledge document. For example, based on the fault name or fault identifier of the system fault, the target processing system can extract the fault analysis results and fault handling solutions corresponding to the same system fault from the operation and maintenance knowledge document.

[0087] Optionally, the target processing system can also determine fault information based on the system log corresponding to the system fault. For example, keywords can be extracted from the log content corresponding to the system fault in the system log, thereby determining the keywords as the fault information of the system fault. Optionally, the extracted keywords are used to describe the fault characteristics of the system fault. Keywords can include at least one of the following: error code, error message, system component name, timestamp, resource status, operation or command, host name or IP address, process ID, port number, etc.

[0088] In an optional embodiment, the fault information further includes at least one of the following: a fault type of the system fault and version information. Optionally, the version information includes at least one of the following: a system version number and a component version number, wherein the system version number refers to the version number of the system in which the fault occurred, and the component version number refers to the version number of the system component in which the fault occurred.

[0089] In an optional embodiment, the fault handling solution includes at least a fault repair method.

[0090] In an optional embodiment, the aforementioned fault handling solution may include, in addition to the fault repair method, at least one of a repair verification method and a rollback method.

[0091] Optionally, after determining the fault analysis results, fault handling solutions and fault information of a certain system fault, the target processing system can generate a text segment corresponding to the system fault based on the fault analysis results, fault handling solutions and fault information of the system fault. For example, a text segment template is obtained, and the keywords in the fault information are set at the target position in the text segment template. The target position refers to the title and / or the first N lines in the text segment template, where N is a positive integer. The fault analysis results and the fault handling solutions are imported into the first position in the text segment template together, thereby obtaining the text segment corresponding to the system fault. The first position refers to the position in the text segment template other than the target position. The first position and the target position can be set according to actual needs, and the target processing system can be preset with import rules. The import rules can be used to describe the way to set the aforementioned keywords at the target position, as well as the way to import the fault analysis results and the fault handling solutions into the first position. In the process of generating text segments, corresponding measures can also be taken to prevent security issues such as prompt injection. Prompt injection is an attack method against the model.

[0092] Optionally, after obtaining multiple text segments, a vector knowledge base can be constructed based on the multiple text segments for subsequent knowledge retrieval. For example, the text segments can be vectorized using a text embedding model to obtain text vectors corresponding to the text segments, and a vector knowledge base can be constructed based on the text vectors corresponding to the text segments.

[0093] It should be noted that by generating different text segments based on the fault information, fault analysis results and fault handling solutions of different system faults, the rich fault instances and handling strategies of the target platform can be effectively divided into different text segments. On the one hand, this avoids the compatibility issues that may be caused by the use of general industry knowledge. On the other hand, it improves the relevance and richness of the content in the text segments, thereby effectively improving the knowledge retrieval efficiency and the quality of the retrieval results.

[0094] In order to achieve accurate knowledge retrieval, in the fault handling method provided in Example 1 of the present application, determining at least one reference text segment from multiple text segments based on target fault information includes: determining a query text vector based on the target fault information; obtaining a text vector corresponding to a text segment from multiple text segments; and determining at least one reference text segment from multiple text segments based on the similarity between the query text vector and the text vector.

[0095] In an optional embodiment, the target processing system may directly use a text embedding model to perform vector conversion on the target fault information to obtain a query text vector.

[0096] In an optional embodiment, after obtaining the target fault information, the target processing system may also generate a query statement based on the target fault information and the query statement template. For example, the query statement may be "find the corresponding knowledge fragment according to the following content: keyword A, keyword B, keyword C", thereby using a text embedding model to perform vector conversion on the query statement to obtain a query text vector.

[0097] Optionally, after obtaining the query text vector, the target processing system may obtain text vectors corresponding to text segments from the multiple text segments and calculate the similarity between the query text vector and the text vector, thereby determining at least one reference text segment from the multiple text segments based on the calculated similarity. For example, the similarity between the query text vector and the text vector is calculated based on cosine similarity, and the text segments corresponding to the text vectors having a similarity greater than a preset threshold are determined as reference text segments. For another example, the text vectors of the multiple text segments are sorted in descending order of similarity to obtain sorted text vectors, and the text segments corresponding to the first M text vectors in the sorted text vectors are determined as reference text segments, where M is a positive integer greater than 1.

[0098] Optionally, the similarity between the text vector of a certain text segment and the query text vector may be regarded as the similarity between the text segment and the target fault information.

[0099] It should be noted that by quantifying the semantic similarity between texts during the retrieval process, the retrieval accuracy can be improved, and historical cases and solutions that are highly relevant to the current system failure can be quickly located, thereby improving the reliability of fault handling.

[0100] In order to obtain accurate target information, in the fault handling method provided in Example 1 of the present application, at least one reference text segment and target fault information are processed by a fault handling model to obtain the target information, including: generating a first prompt statement based on at least one reference text segment, target fault information and a preset first prompt template, wherein the first prompt statement is at least used to guide the fault handling model to generate a target fault analysis result and a target processing solution based on at least one reference text segment and target fault information; inputting the first prompt statement into the fault handling model, obtaining the target fault analysis result and target processing solution through the fault handling model; and determining the target fault analysis result and target processing solution as the target information.

[0101] Optionally, the first prompt template is used to provide clear guidance for the fault handling model, so that the fault analysis results and handling solutions it generates are both professional and closely aligned with the current fault scenario. The structure and content of the template can be adjusted according to the specific needs of fault handling, so it is not specifically limited here. In this embodiment, it is only used as an example. For example, an optional first prompt template can be as follows:

[0102] Please analyze the cause of the current system failure and provide detailed handling steps based on the following fault description and historical reference processing records:

[0103] Fault description: [target fault information]

[0104] Historical reference processing records: [at least one reference text fragment];

[0105] Please output the fault analysis results and solutions in the following format:

[0106] Fault Analysis: [Fault Analysis Results]

[0107] Solution: [target solution]".

[0108] Optionally, the target processing system may fill the target fault information into the above-mentioned "fault description" and fill at least one reference text segment into the above-mentioned "historical reference record processing" to obtain the first prompt statement.

[0109] After receiving the first prompt statement, the target processing system can input the first prompt statement into the fault processing model, and obtain the target fault analysis result and target treatment plan through the fault processing model. The target fault analysis result refers to the fault analysis result for the system fault of the target platform. The target fault analysis result and target treatment plan are thus determined as target information. The target fault analysis result can be presented to the user to facilitate the user to trace and monitor the fault handling process. The target fault analysis result can also be stored as a new knowledge fragment in the operation and maintenance knowledge document for use in updating the vector knowledge base.

[0110] It's important to note that generating the first prompt statement and obtaining the target information based on it effectively guides the fault handling model to more accurately generate fault analysis results and solutions. By guiding the model to generate fault analysis results in addition to the target solution, users can more readily understand the cause of the fault, providing a direct basis for subsequent task execution and manual oversight. This also facilitates updating the operation and maintenance knowledge document with new knowledge fragments, thereby improving fault handling reliability.

[0111] In order to further improve the reliability of fault handling, in the fault handling method provided in Example 1 of the present application, fault handling of the target platform based on the target handling solution in the target information includes: generating a second prompt statement based on the target information and a preset second prompt template, wherein the second prompt statement is used to guide the fault handling model to determine the source of the target information based on multiple text fragments; inputting the second prompt statement into the fault handling model, and obtaining the source information corresponding to the target information through the fault handling model; when the source information represents that the target information belongs to multiple text fragments, fault handling of the target platform is performed based on the target handling solution.

[0112] Large language models may experience hallucinations during processing. This means that they may contain common hardware failures and solutions. When these unverified solutions are executed on a specific platform (such as the target platform mentioned above), they may lead to further failures due to compatibility issues. Therefore, to address this difficulty, it is necessary to avoid using general knowledge for fault handling. In other words, it is necessary to use knowledge from multiple text segments for fault handling.

[0113] Therefore, the target processing system can reorganize the target information returned by the large language model into a prompt statement, perform a secondary query in the large language model, and require the large language model to answer the source of the content in the query statement (specifically in which text segment). When the query content is not in the text segment, the large language model is required to answer "I don't know" to obtain the source information corresponding to the target information.

[0114] Optionally, the structure and content of the second prompt template can be adjusted according to the specific requirements of fault handling, so it is not specifically limited here and is only used as an example in this embodiment. For example, an optional second prompt template can be as follows:

[0115] Please confirm whether the following fault analysis results and solutions are from the knowledge base document and clearly indicate their specific source:

[0116] Fault analysis results: [target fault analysis results]

[0117] Solution: [Target solution]

[0118] Please answer in the following format:

[0119] The analysis results are from the fragment [Fragment Title], and the specific fragment is located at [Fragment Location]. The treatment plan is from the fragment [Fragment Title], and the specific fragment is located at [Fragment Location]. If the analysis results or treatment plan are not in the text fragment, please answer 'Don't know'.

[0120] Optionally, the target processing system may fill in the target fault analysis result in the target information into the above-mentioned “fault analysis result”, and fill in the target processing solution in the target information into the above-mentioned “processing solution”, thereby obtaining a second prompt statement.

[0121] After receiving the second prompt, the target processing system can input the second prompt into the fault handling model. The fault handling model then obtains the source information corresponding to the target information, and then determines whether the target information belongs to the multiple text segments based on the source information. For example, if the source information contains the target field (i.e., the aforementioned "unknown"), the target information is determined not to belong to the multiple text segments. If the source information does not contain the target field, the target information is determined to belong to the multiple text segments.

[0122] Optionally, when the provenance information indicates that the target information belongs to multiple text fragments, fault handling is performed on the target platform based on the target handling solution, and the fault handling result can be recorded on the work order for subsequent tracing.

[0123] Optionally, when the source information indicates that the target information does not belong to multiple text fragments, the target platform is not fault-handled based on the target processing solution, and a prompt message can be generated and sent to the user, wherein the prompt message can be used to indicate that the current system failure of the target platform cannot be automatically resolved and needs to be manually processed.

[0124] It should be noted that the above method ensures that the subsequent fault handling solutions and fault analysis results used for troubleshooting the target platform are verified professional knowledge rather than general industry knowledge, thereby avoiding compatibility issues caused by the use of general industry knowledge and effectively improving the reliability of fault handling.

[0125] In order to realize automatic execution of fault handling, in the fault handling method provided in Example 1 of the present application, the text fragment includes the function identifier of the executable function corresponding to the fault handling solution. When the source information represents that the target information belongs to multiple text fragments, fault handling of the target platform based on the target handling solution includes: determining the executable function corresponding to the target handling solution based on the function identifier corresponding to the target handling solution in the target information and the attribute information in the target database, wherein the target database is used to store the attribute information of the executable function; and performing fault handling on the target platform based on the executable function corresponding to the target handling solution.

[0126] In an optional embodiment, an atomic operation library (i.e., the target database described above) can be pre-configured. For example, a user can decompose the execution processes of known fault repair methods, repair verification methods, and rollback methods into a series of independent, smaller operation and maintenance units, i.e., atomic operations. These operations are indivisible basic steps that can independently complete a certain function or task. In other words, one fault repair method (or repair verification method, or rollback method) corresponds to at least one atomic operation. These atomic operations are designed through functional configuration and are represented by attributes such as Action Version, Action Code, Action Desc, Action Level, Action Target, Action Params, Action TimeOut, ActionMulti, Action Depend, and Action Manual. They are saved as data in a target format (e.g., JSON (JavaScript Object Notation) format) and then stored in the atomic operation library. Among them, the aforementioned attributes (i.e., Action Version, Action Code, Action Desc, Action Level, ActionTarget, Action Params, Action TimeOut, Action Multi, Action Depend, and Action Manual) constitute the attribute information of the executable function. Optionally, the aforementioned ActionVersion represents the version information of the operation, which is used to track the update and change history of the operation; ActionCode represents the unique code identifier of the operation (i.e., the aforementioned function identifier), which is used to match the identifier in the troubleshooting solution. ActionDesc represents a detailed description of the operation, explaining the function and purpose of the operation. ActionLevel represents the urgency or permission level of the operation. For example, some operations may require manual approval before execution, while other operations can be executed automatically. ActionTarget represents the target resource or service of the operation, which determines the execution scope of the operation. ActionParams represents the parameters of the operation, including the configuration or input values ​​required for the operation to execute, such as IP address, network segment, etc.ActionTimeOut indicates the execution timeout of the operation, which is used to prevent the operation from being left unfinished for a long time and affecting system performance or stability. ActionMulti is used to mark whether the operation needs to be executed serially or in parallel with other operations to coordinate the multi-step repair process in the system. ActionDepend is used to indicate the operation's prerequisites, that is, the conditions that need to be met before executing the operation or other dependent operations. ActionManual is used to specify whether the operation is limited to manual execution, such as physical operations such as plugging and unplugging cables, and cannot be executed automatically.

[0127] Optionally, the text fragment includes the function identifier of the executable function corresponding to the fault handling solution. The number of function identifiers in the text fragment may be one or more. In the case where the source information indicates that the target information belongs to multiple text fragments, the target information must also include the function identifier of the executable function. Therefore, the target processing system can match the attribute information of the executable function corresponding to the target processing solution from the target database based on the function identifier corresponding to the target processing solution in the target information, and thus determine the executable function corresponding to the target processing solution based on the attribute information of the executable function corresponding to the target processing solution. For example, the data in the target format in the atomic operation library is parsed into a target data structure. The target data structure refers to a data structure that can be understood (or called processed) by the program, such as parsing a JSON string into a JavaScript object. After obtaining the target data structure, the atomic operations in the target data structure can be mapped to a specific initial executable function. For example, a mapping table or function registry is set up to associate the function identifier (ActionCode) with the actual initial executable function. Next, the mapping table is used to determine the initial executable function to which the function identifier corresponding to the atomic operation belongs. The information defined in the attribute information (e.g., ActionParams) is passed to the initial executable function to obtain the executable function. Since the number of function identifiers in a text fragment may be one or more, the number of executable functions obtained may also be one or more. In other words, at least one executable function can ultimately be obtained.

[0128] In an optional embodiment, in the process of matching the attribute information of the executable function corresponding to the target processing solution from the target database, the target processing system can directly read the target database and match the attribute information corresponding to the function identifier of the target processing solution from the target database.

[0129] In an optional embodiment, in the process of matching the attribute information of the executable function corresponding to the target processing solution from the target database, the target processing system can also output the attribute information through the fault processing model. For example, when it is determined that the source information represents that the target information belongs to multiple text fragments, the user inputs a third prompt statement to the fault processing model. The third prompt statement is used to guide the large model to determine the matching attribute information based on the function identifier corresponding to the target processing solution. For example, the third prompt statement can be "Please output the attribute information of the executable function corresponding to the target processing solution based on the function identifier corresponding to the target processing solution in the target information." After receiving the third prompt statement, the fault processing model can read the content in the target database through the target plug-in to obtain the attribute information corresponding to the function identifier and output it to the user. Among them, the target plug-in is used for interaction between the fault processing model and the target database, which enables the target processing model to read the attribute information stored in the target database. Optionally, read-only permissions can be set for the fault processing model to improve the data security in the target database and prevent injection attacks. Optionally, in order to avoid the query operation occupying database resources for too long, a query timeout can also be set. If the query operation is not completed within the specified time, the system will automatically terminate the query so that the target database can still maintain a good response speed in high concurrency scenarios.

[0130] Optionally, after obtaining the executable function, the target processing system may execute the executable function to perform fault processing on the target platform.

[0131] It should be noted that, through the above method, automatic determination of the executable function for fault handling is achieved, avoiding the problems of low efficiency and low reliability when manually writing executable functions, thereby further improving the reliability of fault handling.

[0132] In order to effectively perform fault repair, in the fault handling method provided in Example 1 of the present application, the target handling solution includes at least a fault repair method, and performing fault handling on the target platform based on the target handling solution in the target information includes: performing fault repair processing on the target platform based on the first executable function in the executable functions corresponding to the target handling solution, wherein the first executable function is used to execute the fault repair method.

[0133] Optionally, the target processing solution includes at least a fault repair method, wherein the fault repair method refers to a method for repairing a system fault, for example, the fault repair method may be restarting a service, applying a patch, adjusting configuration parameters, executing a specific script command, etc.

[0134] Optionally, the first executable function refers to an executable function having a function identifier identical to a function identifier corresponding to the fault repair method in the target processing solution, and the first executable function is used to execute the fault repair method in the target processing solution.

[0135] The target processing system may determine a first executable function from at least one executable function corresponding to the target processing solution to perform fault recovery processing on the target platform. If there are multiple first executable functions, the target processing system may execute the first executable functions based on the order of the function identifiers in the target processing solution.

[0136] It should be noted that, through the above-mentioned method, automatic repair of system faults on the target platform is achieved, thereby improving the efficiency and reliability of fault repair.

[0137] In order to effectively perform repair verification and system rollback, in the fault handling method provided in Example 1 of the present application, after the target platform is repaired based on the first executable function in the executable function corresponding to the target processing scheme, the method also includes: if the target processing scheme also includes a repair verification method, the target platform is repaired and verified based on the second executable function in the executable function to obtain a repair verification result, wherein the second executable function is used to execute the repair verification method; when the repair verification result indicates that the repair has failed, if the target processing scheme also includes a rollback method, the target platform is rolled back based on the third executable function in the executable function, wherein the third executable function is used to execute the rollback method.

[0138] In an optional embodiment, the aforementioned fault handling solution may include, in addition to a fault repair method, at least one of a repair verification method and a rollback method. The repair verification method refers to a method used to verify whether the fault has been resolved after executing the fault repair method. For example, the repair verification method may include rechecking system logs, running diagnostic tools, executing health check scripts, etc. The rollback method is used to roll back the target platform system to restore it to its pre-fault repair state if the fault repair fails (e.g., if the fault is not resolved or side effects occur).

[0139] In an optional embodiment, there are multiple executable functions.

[0140] Optionally, the second executable function refers to an executable function whose function identifier is the same as the function identifier corresponding to the repair verification method in the target processing solution, and the second executable function is used to execute the repair verification method in the target processing solution.

[0141] Optionally, if the target processing solution does not include a repair verification method, it is determined that the fault processing is completed and the subsequent verification process can be handled manually.

[0142] Optionally, if the target processing solution also includes a repair verification method, after performing the fault repair process, the target processing system may execute a second executable function from the multiple executable functions to perform repair verification on the target platform and obtain a repair verification result. If there are multiple second executable functions, the target processing system may execute the second executable functions based on the order of the function identifiers in the target processing solution. The repair verification result is used to indicate whether the repair was successful.

[0143] Optionally, if the repair verification result indicates that the repair is successful, it is determined that the fault handling is completed.

[0144] Optionally, when the repair verification result indicates that the repair has failed, if the target processing solution does not include a rollback method, it is determined that the fault processing is complete and the subsequent verification process can be handled manually.

[0145] Optionally, if the repair verification result indicates a repair failure, if the target processing solution also includes a rollback method, the target platform can be rolled back based on a third executable function among the multiple executable functions. The third executable function is an executable function whose function identifier is the same as the function identifier corresponding to the rollback method in the target processing solution, and the third executable function is used to execute the rollback method in the target processing solution.

[0146] Optionally, to ensure traceability of the fault handling process, all steps, from inputting target fault information and generating a fault handling model to troubleshooting based on the target solution and the results, can be recorded in the work order. This allows for manual oversight, auditability, abortability, rollback, and traceability.

[0147] It should be noted that, through the above method, after the system failure of the target platform is repaired, the repair verification and the rollback operation of the repair failure are automatically performed, thereby improving the security and integrity of the fault handling process, enabling the system to more intelligently respond to the uncertainties that may be brought about by fault repair attempts, quickly take remedial measures, avoid secondary failures caused by improper fault repair, and at the same time reduce the workload of operation and maintenance personnel, thereby improving the efficiency and reliability of fault repair.

[0148] In order to improve the flexibility of fault handling, in the fault handling method provided in Example 1 of the present application, fault handling of the target platform based on the target handling solution in the target information includes: obtaining the fault level of the system fault of the target platform; determining the execution time point of the target handling solution based on the fault level; and performing fault handling on the target platform based on the target handling solution at the execution time point.

[0149] In platform operations and maintenance, different types of faults have varying priorities and urgency due to their scope and severity. For example, some hardware faults can pose a serious threat to the stability of current services and require immediate remediation. These faults are considered highly urgent and must be resolved swiftly to ensure service continuity and user experience. On the other hand, some hardware faults, while present, do not immediately have a devastating impact on services. These faults can be effectively managed through the platform's own capabilities. For example, elastic scaling strategies can be implemented to temporarily increase resources to alleviate pressure, or automated isolation mechanisms can be used to remove faulty devices from the primary service path, achieving dynamic service balance and stability. These faults are classified as relatively non-urgent because the platform's intelligent scheduling and resource management capabilities can mitigate the problem to a certain extent, ensuring continued smooth service operation. Therefore, different fault handling execution times can be determined for different fault scenarios. For example, for urgent hardware faults that impact service stability, the system will quickly recommend or directly implement an immediate solution. However, for minor faults that can be temporarily maintained through elastic scaling or other methods, the system will prompt for delayed resolution. In addition, considering that some self-healing measures may interfere with the service, such as requiring a server restart or modifying the network configuration, the target processing system can also intelligently assess the degree of intrusion into the service and make alternative suggestions.

[0150] Therefore, the target processing system may first obtain the fault level of the system fault of the target platform, and then determine the execution time point of the target processing solution based on the fault level.

[0151] Optionally, in the process of determining the fault level, the target processing system may adopt a preset level determination rule to determine the fault level of the system fault based on the log content about the system fault in the system log. For example, when the log content of the system fault hits a level determination rule of a certain fault level, the hit fault level is determined to be the fault level of the system fault.

[0152] Optionally, in the process of determining the fault level, the target processing system may also input the log content of the system fault into a fault level classification model, perform fault identification using the fault level classification model, and obtain the fault level of the system fault. The fault level classification model may be a neural network model.

[0153] In the target processing system, fault processing delay times corresponding to different fault levels can be preset (such as immediate processing (that is, no delay), delay of half an hour, delay until early morning, etc.). The target processing system can determine the execution time point based on the current time point and the fault processing delay time. For example, the current time point and the fault processing delay time are added to obtain the execution time point.

[0154] After determining the execution time point, the target processing system may perform fault processing on the target platform based on the target processing solution at the execution time point.

[0155] It should be noted that by intelligently judging the fault level and rationally planning the execution time points, high-priority faults can receive immediate responses, while low-priority faults are handled at a time when the impact on service availability is relatively small. This can improve the flexibility of fault handling, reduce the potential risks to the service caused by improper fault handling, and improve the reliability of fault handling.

[0156] In an optional embodiment, it is possible to use Figure 3 In this embodiment, the target processing system may include an AI (Artificial Intelligence) agent to implement automated log analysis and fault handling through the AI ​​agent. Figure 3 This is the process of the fault handling method provided in Example 1 of this application Figure 2 ,like Figure 3 As shown in , the AI ​​agent can include a corpus management module, a work order management module, an abnormal information processor, a problem analysis supervisor, and a self-healing solution processor. Figure 3 As shown, the operation and maintenance knowledge document of the target platform contains fault error information and fault self-healing solutions, which can be saved as corpus in the corpus. The corpus management module can segment the operation and maintenance knowledge document so that a single text segment contains version information corresponding to the same system fault, problem error log keywords, fault repair methods, repair verification methods, and rollback methods, and then perform vector conversion processing on it to store the obtained text vector slices in the vector knowledge base for subsequent RAG process. Optionally, the corpus management module can also refine the fault repair methods, repair verification methods, and rollback methods into atomic operations, and store them in the target format in the atomic operation library (i.e., the above-mentioned target database).

[0157] Alternatively, as Figure 3As shown, when a system failure occurs on the target platform, the exception information processor can collect and analyze system logs, extract keywords from the system logs as target failure information, and generate a query statement. Based on the query text vector of the generated query statement, knowledge retrieval is performed in the vector knowledge base to obtain at least one reference text segment. After obtaining the at least one reference text segment, the fault handling model processes the at least one reference text segment and the target failure information to obtain the target information. The problem analysis supervisor then reorganizes the target information returned by the fault handling model into a query statement, performs a secondary query within the fault handling model, and requires the large model to answer the source of the query content (specifically, in which text segment). If the query content is not in the document segment, the large model is required to answer "unknown." If it is determined that the target information belongs to multiple text segments, the fault handling model can determine the attribute information of the executable function corresponding to the target solution from the atomic operation library. The self-healing solution processor then determines the executable function based on the attribute information and then performs specific self-healing operations on the server or network on the target platform based on the executable function. The overall self-healing process includes determining whether to execute the self-healing operation (i.e., determining the execution time), executing the self-healing operation (i.e., performing fault repair), verifying the self-healing results, and rolling back the repair if it fails. Each step is stacked and pushed into the pipeline, allowing the self-healing solution processor to execute it sequentially and in an orderly manner.

[0158] Optionally, in order to ensure the traceability of the fault self-recovery process, all the information from the entry of fault information, fault handling model analysis, to the self-recovery process and results will be recorded in the work order. This will meet the requirements of manual supervision, checkability, termination, rollback, and traceability. Figure 3 As shown, when a system failure is detected on the target platform, the work order management module creates a work order, and then records the cleaning results of the system log by the exception information processor in the work order. After that, the prompt statement generated based on at least one reference text segment and the target failure information is recorded in the work order, and the work order management module can record the output results of the fault processing model feedback (i.e., the target information and the attribute information of the executable function) in the work order. During the fault self-healing process, if the fault is repaired successfully, the fault repair result is recorded in the work order, and the work order is determined to be completed. If the fault repair fails, the system is rolled back, or as shown in the following example: Figure 3As shown, select manual intervention. Methods of manual intervention include but are not limited to: adjusting the query content and re-triggering the query; updating the atomic operation library and re-triggering the query; manual operation and maintenance work orders, etc. During the manual intervention process, users can confirm the fault, manually repair it, and manually verify it, and the information generated during the manual intervention will also be recorded in the work order. In addition, when the operation level of the executable function is high and manual blocking is required for approval and execution, the self-healing solution processor can generate a reminder message to remind the user to approve the executable function before executing the executable function, so that if the user approves it, the executable function will be executed to achieve fault repair.

[0159] In the embodiment of the present application, by combining retrieval enhancement technology, when the fault information of the system of the target platform is obtained, relevant knowledge is first extracted from multiple text fragments through information retrieval, and then the obtained relevant knowledge is injected into the fault handling model generation process. This "retrieval-generation" collaborative mode not only retains the logical reasoning and natural language generation capabilities of the language model, but also breaks through the limitations of its static knowledge boundaries, improves the accuracy of the generated target information, and thus can improve the reliability of fault handling. Further, by setting up different text fragments containing fault information and fault handling solutions for different system faults, it is possible to aggregate the relevant information of the same system fault in the same text fragment, improve the relevance of the content in the same text fragment, and thus improve the retrieval accuracy in the retrieval process, achieving the purpose of combining retrieval enhancement technology and generating fault handling solutions based on text fragments that have distinguished fault knowledge for fault handling, achieving the technical effect of improving the reliability of fault handling, and thus solving the technical problem of low reliability of fault handling when a platform fault occurs in the related technology.

[0160] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0161] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the existing technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0162] Example 2

[0163] According to an embodiment of the present application, a method for handling a fault is also provided, such as Figure 4 As shown, the method includes:

[0164] Step S401: Acquire the fault information of the system fault of the target platform uploaded by the client to obtain target fault information.

[0165] Step S402: In the cloud server, at least one reference text segment is determined from multiple text segments based on the target fault information, wherein different text segments contain fault information and fault handling solutions for different system faults; at least one reference text segment and the target fault information are processed through a fault handling model to obtain target information, wherein the target information at least includes a target handling solution for the system fault of the target platform.

[0166] Step S403: Feedback the target information to the client, wherein the target information is used to instruct the client to perform fault processing on the target platform based on the target processing solution.

[0167] Through the above-mentioned scheme, combined with retrieval enhancement technology, when system fault information for the target platform is obtained, relevant knowledge is first extracted from multiple text segments through information retrieval, and then the obtained relevant knowledge is injected into the fault handling model generation process. This "retrieval-generation" collaborative model not only retains the logical reasoning and natural language generation capabilities of the language model, but also breaks through the limitations of its static knowledge boundaries, improving the accuracy of the generated target information, thereby improving the reliability of fault handling. Furthermore, by setting different text segments to contain fault information and fault handling solutions for different system faults, relevant information on the same system fault is aggregated in the same text segment, improving the relevance of content within the same text segment, thereby improving retrieval accuracy during the retrieval process. This achieves the purpose of combining retrieval enhancement technology to generate fault handling solutions based on text segments that have differentiated fault knowledge for fault handling, achieving the technical effect of improving fault handling reliability, thereby solving the technical problem of low fault handling reliability in related technologies when platform faults occur.

[0168] In the cloud server, the specific method for handling the fault is the same as that in the first embodiment and will not be repeated here.

[0169] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0170] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the existing technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0171] Example 3

[0172] According to an embodiment of the present application, a fault processing device for implementing the above-mentioned fault processing method is also provided, such as Figure 5As shown, the device includes: a first acquiring unit 501 , a determining unit 502 , a first processing unit 503 and a second processing unit 504 .

[0173] The first acquisition unit 501 is configured to acquire fault information of a system fault on a target platform to obtain target fault information;

[0174] A determining unit 502 is configured to determine at least one reference text segment from a plurality of text segments based on the target fault information, wherein different text segments contain fault information and fault handling solutions for different system faults;

[0175] A first processing unit 503 is configured to process at least one reference text segment and target fault information using a fault processing model to obtain target information, wherein the target information at least includes a target processing solution for a system fault of a target platform;

[0176] The second processing unit 504 is configured to perform fault processing on the target platform based on the target processing solution in the target information.

[0177] In the fault processing device provided in the third embodiment of the present application, the fault information of the system fault of the target platform is obtained by the first acquisition unit 501 to obtain the target fault information; the determination unit 502 determines at least one reference text segment from multiple text segments based on the target fault information, wherein different text segments contain fault information and fault processing solutions of different system faults; the first processing unit 503 processes the at least one reference text segment and the target fault information through the fault processing model to obtain target information, wherein the target information at least includes the target processing solution for the system fault of the target platform; the second processing unit 504 performs fault processing on the target platform based on the target processing solution in the target information. In this solution, by combining retrieval enhancement technology, when the fault information of the system of the target platform is obtained, relevant knowledge is first extracted from multiple text segments through information retrieval, and then the obtained relevant knowledge is injected into the fault processing model generation process. This "retrieval-generation" collaborative mode not only retains the logical reasoning and natural language generation capabilities of the language model, but also breaks through the limitations of its static knowledge boundaries, improves the accuracy of the generated target information, and thus can improve the reliability of fault processing. Furthermore, by setting up different text segments to contain fault information and fault handling solutions for different system faults, the relevant information of the same system fault is aggregated in the same text segment, which improves the relevance of the content in the same text segment, thereby improving the retrieval accuracy in the retrieval process, and achieving the purpose of combining retrieval enhancement technology to generate fault handling solutions based on text segments with differentiated fault knowledge for fault handling, thereby achieving the technical effect of improving the reliability of fault handling, and thus solving the technical problem of low reliability of fault handling in related technologies when a platform failure occurs.

[0178] Optionally, in the fault processing device provided in Example 3 of the present application, the fault processing device also includes: a second acquisition unit, used to obtain the operation and maintenance knowledge document of the target platform; a first extraction unit, used to extract the fault analysis results and fault handling solutions of the system fault recorded in the operation and maintenance knowledge document from the operation and maintenance knowledge document; a second extraction unit, used to determine the fault information based on the system log corresponding to the system fault; and a generation unit, used to generate different text fragments based on the fault analysis results, fault handling solutions and fault information of different system faults to obtain multiple text fragments.

[0179] Optionally, in the fault processing device provided in Example 3 of the present application, the determination unit 502 includes: a first determination subunit, used to determine the query text vector based on the target fault information; a first acquisition subunit, used to obtain the text vector corresponding to the text segment among multiple text segments; and a second determination subunit, used to determine at least one reference text segment from the multiple text segments based on the similarity between the query text vector and the text vector.

[0180] Optionally, in the fault processing device provided in Example 3 of the present application, the first processing unit 503 includes: a first generation subunit, used to generate a first prompt statement based on at least one reference text segment, target fault information and a preset first prompt template, wherein the first prompt statement is at least used to guide the fault processing model to generate a target fault analysis result and a target processing solution based on at least one reference text segment and the target fault information; a first processing subunit, used to input the first prompt statement into the fault processing model, and obtain the target fault analysis result and target processing solution through the fault processing model; and a third determination subunit, used to determine the target fault analysis result and target processing solution as target information.

[0181] Optionally, in the fault processing device provided in Example 3 of the present application, the second processing unit 504 includes: a second generation sub-unit, used to generate a second prompt statement based on the target information and a preset second prompt template, wherein the second prompt statement is used to guide the fault processing model to determine the source of the target information based on multiple text fragments; a second processing sub-unit, used to input the second prompt statement into the fault processing model, and obtain the source information corresponding to the target information through the fault processing model; and a third processing sub-unit, used to perform fault processing on the target platform based on the target processing solution when the source information indicates that the target information belongs to multiple text fragments.

[0182] Optionally, in the fault processing device provided in Example 3 of the present application, the text segment includes a function identifier of an executable function corresponding to the fault processing solution, and the third processing sub-unit includes: a determination module for determining the executable function corresponding to the target processing solution based on the function identifier corresponding to the target processing solution in the target information and the attribute information in the target database, wherein the target database is used to store the attribute information of the executable function; and a processing module for performing fault processing on the target platform based on the executable function corresponding to the target processing solution.

[0183] Optionally, in the fault processing device provided in Example 3 of the present application, the target processing scheme includes at least a fault repair method, and the second processing unit 504 includes: a fourth processing sub-unit, used to perform fault repair processing on the target platform based on the first executable function in the executable function corresponding to the target processing scheme, wherein the first executable function is used to execute the fault repair method.

[0184] Optionally, in the fault processing device provided in Example 3 of the present application, the fault processing device also includes: a third processing unit, which is used to perform repair verification processing on the target platform based on the second executable function in the executable function to obtain a repair verification result if the target processing solution also includes a repair verification method, wherein the second executable function is used to execute the repair verification method; and a fourth processing unit, which is used to perform rollback processing on the target platform based on the third executable function in the executable function when the repair verification result indicates that the repair has failed, if the target processing solution also includes a rollback method, wherein the third executable function is used to execute the rollback method.

[0185] Optionally, in the fault processing device provided in Example 3 of the present application, the second processing unit 504 includes: a second acquisition sub-unit, used to obtain the fault level of the system fault of the target platform; a fourth determination sub-unit, used to determine the execution time point of the target processing solution based on the fault level; and a fifth processing sub-unit, used to perform fault processing on the target platform based on the target processing solution at the execution time point.

[0186] It should be noted that the first acquisition unit 501, determination unit 502, first processing unit 503, and second processing unit 504 described above correspond to steps S201 to S204 in Example 1. The examples and application scenarios implemented by the above units and corresponding steps are the same, but are not limited to the contents disclosed in Example 1. It should be noted that the above modules, as part of the device, can be run in the computer terminal 10 provided in Example 1.

[0187] It should be noted that the preferred implementation scheme involved in the above embodiments of this application is the same as the scheme provided in Example 1, as well as the application scenario and implementation process, but is not limited to the scheme provided in Example 1.

[0188] Example 4

[0189] The embodiment of the present application may provide an electronic device, which may be any electronic device in a group of electronic devices. Optionally, in this embodiment, the electronic device may also be replaced by a terminal device such as a mobile terminal.

[0190] Optionally, in this embodiment, the electronic device may be located in at least one network device among a plurality of network devices of a computer network.

[0191] In this embodiment, the electronic device may execute program codes corresponding to the steps in the fault handling method provided in any one of the above method embodiments.

[0192] Optionally, Figure 6 This is a structural block diagram of an electronic device according to an embodiment of the present application. Figure 6 As shown, the electronic device 60 may include: one or more ( Figure 6 (only one is shown) processor 602, memory 604. The electronic device 60 may further include a memory controller to control and manage the memory 604; the electronic device 60 may further include a peripheral interface to connect to a radio frequency module, an audio module, and a display screen, etc.

[0193] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the fault handling method and device in the embodiment of the present application. 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 fault handling 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 can be connected to the 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 a combination thereof.

[0194] The processor can call the information and application programs stored in the memory through the transmission device to execute the program codes corresponding to the steps in the fault handling method provided in any one of the above method embodiments.

[0195] It can be understood by those skilled in the art that Figure 6 The structure shown is for illustration only, and the electronic device may also be a terminal device such as a smart phone, a tablet computer, a PDA, a mobile Internet device (MID), or a PAD. Figure 6It does not limit the structure of the above electronic device. For example, the electronic device 60 may also include Figure 6 More or fewer components (such as network interfaces, display devices, etc.) shown in, or with Figure 6 Different configurations shown.

[0196] A person skilled in the art will 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, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0197] Example 5

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

[0199] Optionally, in this embodiment, the storage medium may be located in any electronic device in a group of electronic devices in a computer network, or in any mobile terminal in a group of mobile terminals.

[0200] Example 6

[0201] The embodiment of the present application further provides a computer program product. Optionally, in this embodiment, the computer program product may include a computer program, which, when executed by a processor, implements the fault handling method provided in the first embodiment.

[0202] 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.

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

[0204] 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 units is only a logical function division. In actual implementation, there may be other division methods. 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.

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

[0206] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0207] 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, 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. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments 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, magnetic disk or optical disk, and other media that can store program code.

[0208] The above is only a preferred embodiment 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 method for handling a fault, characterized in that: include: When a target platform fails during operation, fault information of a system fault detected on the target platform is obtained to obtain target fault information; Determining at least one reference text segment from a plurality of text segments based on the target fault information, wherein different text segments contain fault information and fault handling solutions for different system faults; Processing the at least one reference text segment and the target fault information through a fault processing model to obtain target information, wherein the target information at least includes a target processing solution for the system fault of the target platform; Performing fault processing on the target platform based on the target processing solution in the target information; The performing fault processing on the target platform based on the target processing solution in the target information includes: Inputting a second prompt statement into the fault handling model, and obtaining source information corresponding to the target information through the fault handling model, wherein the second prompt statement is used to guide the fault handling model to determine the source of the target information based on the multiple text fragments; When the source information indicates that the target information belongs to the multiple text fragments, performing fault processing on the target platform based on the target processing solution; In a case where the provenance information indicates that the target information does not belong to multiple text fragments, the target platform is not fault-handled based on the target processing solution.

2. The method according to claim 1, characterized in that Before determining at least one reference text segment from a plurality of text segments based on the target fault information, the method further includes: Obtaining operation and maintenance knowledge documents of the target platform; For the system failure recorded in the operation and maintenance knowledge document, extract the failure analysis result and failure handling solution of the system failure from the operation and maintenance knowledge document; Determine the fault information based on the system log corresponding to the system fault; Different text segments are generated according to the fault analysis results, fault handling solutions and the fault information of different system faults to obtain the multiple text segments.

3. The method according to claim 1, characterized in that Determining at least one reference text segment from a plurality of text segments based on the target fault information includes: Determine a query text vector according to the target fault information; Obtaining text vectors corresponding to text segments among the multiple text segments; The at least one reference text segment is determined from the multiple text segments according to the similarity between the query text vector and the text vector.

4. The method according to claim 2, characterized in that The at least one reference text segment and the target fault information are processed by the fault processing model to obtain target information, including: generating a first prompt statement based on the at least one reference text segment, the target fault information, and a preset first prompt template, wherein the first prompt statement is at least used to guide the fault processing model to generate a target fault analysis result and a target processing solution based on the at least one reference text segment and the target fault information; Inputting the first prompt statement into the fault processing model, and obtaining a target fault analysis result and the target processing solution through the fault processing model; The target fault analysis result and the target processing solution are determined as the target information.

5. The method according to any one of claims 1 to 4, characterized in that Handling a fault on the target platform based on the target handling solution in the target information includes: A second prompt statement is generated according to the target information and a preset second prompt template.

6. The method according to claim 5, characterized in that The text fragment includes a function identifier of an executable function corresponding to the fault handling solution. When the source information indicates that the target information belongs to the multiple text fragments, performing fault handling on the target platform based on the target handling solution includes: Determining an executable function corresponding to the target processing solution based on a function identifier corresponding to the target processing solution in the target information and attribute information in a target database, wherein the target database is used to store attribute information of executable functions; Fault processing is performed on the target platform based on an executable function corresponding to the target processing solution.

7. The method according to any one of claims 1 to 4, characterized in that The target processing solution includes at least a fault repair method, and performing fault processing on the target platform based on the target processing solution in the target information includes: Performing fault repair processing on the target platform based on a first executable function among the executable functions corresponding to the target processing solution, wherein the first executable function is used to execute the fault repair method.

8. The method according to claim 7, characterized in that After performing fault repair processing on the target platform based on the first executable function among the executable functions corresponding to the target processing solution, the method further includes: If the target processing solution further includes a repair verification method, performing repair verification processing on the target platform based on a second executable function in the executable functions to obtain a repair verification result, wherein the second executable function is used to execute the repair verification method; In the case where the repair verification result indicates that the repair has failed, if the target processing solution also includes a rollback method, the target platform is rolled back based on a third executable function in the executable functions, wherein the third executable function is used to execute the rollback method.

9. The method according to any one of claims 1 to 4, characterized in that Handling a fault on the target platform based on the target handling solution in the target information includes: Obtaining a fault level of a system fault on the target platform; Determining an execution time point of the target processing solution based on the fault level; Fault processing is performed on the target platform based on the target processing solution at the execution time point.

10. A method for handling a fault, characterized in that: include: When a target platform fails during operation, the target platform detects a system failure and obtains the target failure information. In the cloud server, at least one reference text segment is determined from a plurality of text segments based on the target fault information, wherein different text segments contain fault information and fault handling solutions for different system faults; the at least one reference text segment and the target fault information are processed using a fault handling model to obtain target information, wherein the target information at least includes a target handling solution for the system fault of the target platform; Feeding back the target information to the client, wherein the target information is used to instruct the client to perform fault processing on the target platform based on the target processing solution; The performing fault processing on the target platform based on the target processing solution in the target information includes: Inputting a second prompt statement into the fault handling model, and obtaining source information corresponding to the target information through the fault handling model, wherein the second prompt statement is used to guide the fault handling model to determine the source of the target information based on the multiple text fragments; When the source information indicates that the target information belongs to the multiple text fragments, performing fault processing on the target platform based on the target processing solution; In a case where the provenance information indicates that the target information does not belong to multiple text fragments, the target platform is not fault-handled based on the target processing solution.

11. A fault handling device, characterized in that: include: The first acquisition unit is configured to acquire fault information of a system fault detected on the target platform when a fault occurs during operation of the target platform, thereby obtaining target fault information; a determining unit, configured to determine at least one reference text segment from a plurality of text segments based on the target fault information, wherein different text segments contain fault information and fault handling solutions for different system faults; a first processing unit, configured to process the at least one reference text segment and the target fault information using a fault processing model to obtain target information, wherein the target information at least includes a target processing solution for the system fault of the target platform; a second processing unit, configured to perform fault processing on the target platform based on the target processing solution in the target information; The second processing unit is further configured to: Inputting a second prompt statement into the fault handling model, and obtaining source information corresponding to the target information through the fault handling model, wherein the second prompt statement is used to guide the fault handling model to determine the source of the target information based on the multiple text fragments; When the source information indicates that the target information belongs to the multiple text fragments, performing fault processing on the target platform based on the target processing solution; In a case where the provenance information indicates that the target information does not belong to multiple text fragments, the target platform is not fault-handled based on the target processing solution.

12. An electronic device, characterized in that: include: a memory storing an executable program; A processor is used to run the program, wherein the program executes the fault processing method of any one of claims 1 to 9 when running.

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

14. A computer program product, characterized in that The method comprises a computer program or instructions, which implements the fault processing method according to any one of claims 1 to 9 when executed by a processor.

Images