Fault analysis method and device, equipment, storage medium and program product

Through the large language model, the problem of failure analysis time-consuming problem in the existing technology is solved, and the efficiency and accuracy of fault analysis are improved.

CN118916262APending Publication Date: 2024-11-08CHINABANK PAYMENT (BEIJING) TECH CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202410870590.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-06-28
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

When software system failure occurs, the existing technology relies on developers to manually simulate and analyze, resulting in long-term failure location and cause analysis and inefficient efficiency.

Method used

The large language model is used for fault analysis, and by receiving the fault trigger information, determining the relevant running code from the code database, generating prompt information, and using the large language model to process this information to obtain the cause of the failure and repair suggestions.

Benefits of technology

It improves the efficiency and accuracy of fault analysis, reduces the amount of data analyzed by large language model, and reduces the time-consuming failure location and cause analysis.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916262A_ABST
    Figure CN118916262A_ABST
Patent Text Reader

Abstract

The invention provides a fault analysis method which can be applied to the technical field of computers and artificial intelligence. The fault analysis method provided by the invention comprises the following steps: in response to received trigger information used for representing that a fault exists in a target service, determining an operation code related to the generation of the fault from a code database based on the trigger information; generating prompt information based on the operation code, the trigger information and the prompt template; and processing the prompt information by using a large language model to obtain a target analysis result. The invention further provides a fault analysis device and equipment, a storage medium and a program product.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the fields of computer technology and artificial intelligence technology, and in particular to technical fields such as large language models, software development, testing, and fault analysis. More specifically, it relates to a fault analysis method, apparatus, device, storage medium, and program product. Background Art

[0002] With the rapid development of communication and computer technology, the complexity of computer software systems and their components is increasing. In order to ensure that these systems can run efficiently and stably, it is necessary to continuously monitor and optimize the performance and status of the software system. Through continuous monitoring, data analysis and maintenance of software system performance, problems can be discovered and solved in a timely manner, and the reliability and operating efficiency of the software system can be improved.

[0003] In the process of realizing the concept disclosed in the present invention, the inventors found that there are at least the following problems in the related technology. When a fault occurs in the software running state, the prior art relies on manual simulation and analysis by developers. This method takes a long time to locate and analyze the cause of the fault, resulting in inefficient troubleshooting. Summary of the invention

[0004] In view of this, the present disclosure provides a fault analysis method, apparatus, device, storage medium, and program product.

[0005] One aspect of the present disclosure provides a fault analysis method, including: in response to receiving trigger information for characterizing the existence of a fault in a target business, based on the trigger information, determining the running code related to the fault from a code database; based on the running code, the trigger information and the prompt template, generating prompt information; and using a large language model to process the prompt information to obtain a target analysis result.

[0006] According to an embodiment of the present disclosure, the step of determining the running code related to the fault from the code database based on the trigger information includes: determining the running code from the code database based on the code identifier related to the fault in the trigger information.

[0007] According to an embodiment of the present disclosure, the above-mentioned fault analysis method further includes determining a code identifier from the trigger information in a determination manner that matches an information type of the trigger information.

[0008] According to an embodiment of the present disclosure, the above-mentioned determination method according to which the information type of the trigger information is matched to determine the code identifier from the trigger information includes: determining a target field that matches the information type of the trigger information; and determining the code identifier based on the field value of the target field.

[0009] According to an embodiment of the present disclosure, the code identifier includes stack information; the above-mentioned code identifier related to the fault in the trigger information is used to determine the running code from the code database, including: determining the running code that matches the vector data of the code identifier from the code database, wherein the code database includes the running code after vector conversion.

[0010] According to an embodiment of the present disclosure, the code identifier includes an interface identifier; the above-mentioned determining the running code from the code database based on the code identifier related to the fault in the trigger information includes: based on the interface identifier, determining from the code database a code block corresponding to the interface identifier; determining from the code block an associated interface identifier associated with the interface identifier; determining from the code database an associated code block corresponding to the associated interface identifier; and obtaining the running code based on the code block and the associated code block.

[0011] According to an embodiment of the present disclosure, the above-mentioned fault analysis method also includes splitting the running code used to process the target business according to the splitting granularity of the code block to obtain a code block set, wherein the target business includes multiple business operations, and the code block includes the running code for processing a single business operation; and determining the code database based on the code block set.

[0012] According to an embodiment of the present disclosure, the above-mentioned generation of prompt information based on the running code, trigger information and prompt template includes: determining a prompt template that matches the information type of the trigger information from multiple predetermined prompt templates; and adding the running code and trigger information to the preset field of the prompt template to obtain the prompt information.

[0013] According to an embodiment of the present disclosure, the above-mentioned use of a large language model to process prompt information to obtain a target analysis result includes: using a large language model to process prompt information to obtain a fault cause analysis result and a fault repair suggestion result; and obtaining a target analysis result based on the fault cause analysis result and the fault repair suggestion result.

[0014] Another aspect of the present disclosure provides a fault analysis device, including: a code determination module, which is used to determine the running code related to the fault from a code database in response to receiving trigger information for characterizing the existence of a fault in a target business, based on the trigger information; an information generation module, which is used to generate prompt information based on the running code, the trigger information and the prompt template; and a result analysis module, which is used to process the prompt information using a large language model to obtain a target analysis result.

[0015] Another aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned fault analysis method.

[0016] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above fault analysis method when executed.

[0017] Another aspect of the present disclosure provides a computer program product, which includes computer executable instructions, and the instructions are used to implement the above fault analysis method when executed.

[0018] According to the embodiments of the present disclosure, because a large language model is applied to the scenario of fault analysis, and the trigger information of the fault and the running code related to the fault are used as auxiliary information for the large language model analysis, the efficiency and accuracy of the fault analysis are improved. Furthermore, the relevant running code generated by the fault is determined according to the trigger information, the pertinence of the running code is improved, and the amount of data analyzed by the large language model is reduced, thereby improving the processing efficiency. The technical problem that the location and cause analysis of the fault takes a long time is at least partially overcome, thereby achieving the technical effect of improving the efficiency of fault analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0020] Figure 1 An exemplary system architecture to which a fault analysis method according to an embodiment of the present disclosure can be applied is schematically shown;

[0021] Figure 2 A flowchart of a fault analysis method according to an embodiment of the present disclosure is schematically shown;

[0022] Figure 3 The schematic diagram shows a principle diagram of a fault analysis method according to an embodiment of the present disclosure;

[0023] Figure 4 Schematically shows a flowchart of determining associated code blocks according to an embodiment of the present disclosure;

[0024] Figure 5 A flowchart schematically shows the operation code management and storage according to an embodiment of the present disclosure;

[0025] Figure 6 A block diagram schematically shows a fault analysis device according to an embodiment of the present disclosure; and

[0026] Figure 7 A block diagram of an electronic device suitable for implementing the above-described fault analysis method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0027] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0028] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0029] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0030] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0031] In the embodiments of the present disclosure, the collection, updating, analysis, processing, use, transmission, provision, disclosure, storage, etc. of the data involved (for example, including but not limited to user personal information) are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. In particular, necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security, and national security.

[0032] In the embodiments of the present disclosure, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

[0033] For example, to count the usage of our products / services, we will aggregate, analyze and use the technically processed user data, and share the processed statistical information with third parties. We will use secure encryption technology and other methods to ensure that the recipient of the information cannot re-identify a specific individual.

[0034] Due to the increasing complexity of computer software systems and components, there is a need to continuously monitor, analyze and maintain the performance of software systems in order to promptly discover and resolve problems and improve the reliability and efficiency of software systems.

[0035] In the prior art, when a software system fails, developers are required to perform manual simulation and analysis.

[0036] For example, during the software testing phase, if a defect is discovered during testing, the developer can use the test report to simulate the input scenario, perform log analysis, and call link tracking to manually analyze the cause of the defect.

[0037] In software production and operation, if an error or exception occurs, the developer is mainly responsible for tracking the call link, debugging, analysis, and finally manual simulation and scenario reproduction based on the error log.

[0038] This method takes a long time to locate and analyze the cause of the fault, resulting in low efficiency in troubleshooting.

[0039] In order to at least partially solve the above technical problems, the embodiments of the present disclosure locate and repair faults by using the understanding and analysis capabilities of a large language model. Specifically, the embodiments of the present disclosure provide a fault analysis method, including: in response to receiving trigger information for characterizing the existence of a fault in a target business, based on the trigger information, determining the running code related to the fault from a code database; based on the running code, the trigger information and the prompt template, generating prompt information; and using a large language model to process the prompt information to obtain a target analysis result.

[0040] Figure 1 The exemplary system architecture 100 to which the fault analysis method according to the embodiment of the present disclosure can be applied is schematically shown. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0041] like Figure 1 As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and / or wireless communication links, etc.

[0042] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients and / or social platform software, etc. (only for example).

[0043] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0044] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0045] It should be noted that the fault analysis method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the fault analysis device provided in the embodiment of the present disclosure can generally be set in the server 105. The fault analysis method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal device 101, 102, 103 and / or the server 105. Accordingly, the fault analysis device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal device 101, 102, 103 and / or the server 105. Alternatively, the fault analysis method provided in the embodiment of the present disclosure can also be executed by the terminal device 101, 102, or 103, or it can also be executed by other terminal devices different from the terminal device 101, 102, or 103. Accordingly, the fault analysis device provided in the embodiment of the present disclosure can also be set in the terminal device 101, 102, or 103, or it can be set in other terminal devices different from the terminal device 101, 102, or 103.

[0046] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0047] It should be noted that the sequence numbers of the operations in the following method are only used as representations of the operations for the purpose of description, and should not be regarded as representing the execution order of the operations. Unless explicitly stated, the method does not need to be executed completely in the order shown.

[0048] Figure 2 The flowchart of the fault analysis method according to the embodiment of the present disclosure is schematically shown.

[0049] like Figure 2 As shown, the method 200 includes operations S210 to S230.

[0050] In operation S210 , in response to receiving trigger information indicating that a target service has a fault, a running code related to the fault is determined from a code database based on the trigger information.

[0051] In operation S220, prompt information is generated based on the running code, the trigger information, and the prompt template.

[0052] In operation S230, the prompt information is processed using the large language model to obtain a target analysis result.

[0053] According to the embodiments of the present disclosure, the trigger information of the fault represents the information or signal that can trigger the start of the fault handling process, or the object or event that triggers the fault handling process when certain conditions are met or specific anomalies are detected during the test or operation of the target business. The trigger information may include the time when the fault occurred, the type of fault, the code information involved, related parameters, results, and other descriptive information.

[0054] According to the embodiments of the present disclosure, various trigger information can be obtained by setting a unified trigger response module, and the fault handling process can be started after the trigger information is obtained. The trigger response module has a certain versatility and can be compatible with various forms of triggering methods. For example, it can be compatible with software bug (fault) test reports, error logs in production operations, and other triggering methods.

[0055] According to an embodiment of the present disclosure, the code database is a database that stores the running code of the target business as a file or a data structure. After a failure occurs in the target business, the associated information of the running code related to the failure can be extracted from the trigger information, and the extracted associated information can be used to query the code database for related code fragments, thereby obtaining the running code related to the failure.

[0056] According to an embodiment of the present disclosure, a prompt template may be a task configuration parameter used to help a large language model understand a fault code, and a prompt template may be a prompt tag sequence based on controlling the large language model to make accurate predictions, and the prompt tag sequence may include any type of prompt tags such as characters, fields, and text. The prompt template may be used to indicate the actions that the large language model should take or the output results that it should generate when performing a specific task.

[0057] According to an embodiment of the present disclosure, a large language model (LLM) is a neural network model containing ultra-large-scale parameters (usually more than one billion), and the large language model has a strong semantic learning ability. The large language model can process a very large amount of information, and can continuously learn and optimize its own parameters during the training process, and can achieve good performance in natural language tasks. By inputting the prompt information into the large language model, the understanding and analysis capabilities of the large language model can be used to understand and analyze the prompt information and output relevant results.

[0058] According to the embodiments of the present disclosure, because a large language model is applied to the scenario of fault analysis, and the trigger information characterizing the existence of a fault in the target business and the running code related to the fault are used as auxiliary information for the large language model analysis, the efficiency and accuracy of the fault analysis are improved. Furthermore, the relevant running code generated by the fault is determined based on the trigger information, the pertinence of the running code is improved, and the amount of data analyzed by the large language model is reduced, thereby improving the processing efficiency. Therefore, the technical problem of time-consuming fault location and cause analysis is at least partially overcome, thereby achieving the technical effect of improving the efficiency of fault analysis.

[0059] Reference below Figure 3 to Figure 5 , the fault analysis method 200 according to the embodiment of the present invention is further described.

[0060] Figure 3 The principle diagram of the fault analysis method according to the embodiment of the present disclosure is schematically shown.

[0061] like Figure 3 As shown, the running code 301 for processing the target service is stored in the code database 302. When the target service fails, trigger information 303 is generated, and the trigger information 303 may include multiple types of trigger information, such as trigger type A, trigger type B, trigger type C, etc.

[0062] The fault analysis method provided in the embodiment of the present disclosure is triggered by the trigger information 303, and the trigger information 303 is sent to the recall module 304. The recall module 304 can query the running code related to the fault in the code database 302 based on the trigger information 303, and recall the queried running code from the code database 302. The query result can also be used as a priori knowledge of the large model.

[0063] The recall module 304 calls the trigger information 303 and the recalled running code to the automatic analysis module 305. In the automatic analysis template 305, the trigger information 303 and the running code are used to update the prompt template to generate prompt information. The prompt information is sent to the large language model M306, which uses the understanding and generation capabilities of the large language model to output the analysis results and return them to the automatic analysis module 305.

[0064] The fault analysis report 307 is generated by the automatic analysis module 305. The fault analysis report 307 may include a multi-dimensional report such as error content, error code location, error cause, and suggested repair solutions.

[0065] According to an embodiment of the present disclosure, when executing Figure 2 Before the operation S210 shown determines the running code related to the fault from the code database based on the trigger information, the fault analysis method further includes determining the code identifier from the trigger information in a determination manner that matches the information type of the trigger information.

[0066] According to an embodiment of the present disclosure, the trigger information may include system monitoring and alarm information, error logs, test reports, user feedback and complaints, etc. Based on the different information types of the trigger information, the information content and format contained in the trigger information are also different, for example, it may be text, numbers, binary data, structured data, etc. Different types of information require matching methods to extract useful information.

[0067] For example, if the trigger information is in text format, natural language processing or text search technology can be used to identify keywords or phrases, thereby obtaining a code identifier. If the trigger information is structured data, the code identifier can be obtained by accessing specific fields or attributes.

[0068] According to the embodiments of the present disclosure, code identifiers refer to names and comments given to entities such as variables, functions, classes, modules, etc. in the code to identify their meanings and functions, and are uniquely corresponding to various elements in the code, such as variables, functions, classes, modules, etc. Code identifiers can be keywords, predefined identifiers, or user-defined identifiers, etc. Code identifiers use consistent naming rules.

[0069] In such an implementation, a matching method is selected according to the information type of the trigger information so as to extract information that can accurately identify the relevant code from the trigger information. This determination method can improve the flexibility and pertinence of determining the code identification, and will not introduce erroneous information or omission of information due to improper processing.

[0070] According to an embodiment of the present disclosure, determining a code identifier from the trigger information in a determination method that matches the information type of the trigger information may include: determining a target field that matches the information type of the trigger information; and determining the code identifier based on the field value of the target field.

[0071] According to an embodiment of the present disclosure, based on the type of trigger information, multiple fields included in the trigger information are determined, and then a target field related to the code identifier is determined from the multiple fields. Specific field values ​​are extracted from the target field, and the code identifier is determined using these field values.

[0072] According to an embodiment of the present disclosure, the code identifier is determined based on the field value of the target field, and the field value may directly point to the code identifier; or the corresponding code identifier may be found through the field value through a predetermined rule or mapping relationship.

[0073] By screening the target fields and field values ​​that match the type of trigger information, the code identifier is obtained, which serves as the basis for the subsequent determination of the running code based on the code identifier. By filtering out noise information, the processing accuracy is improved.

[0074] According to an embodiment of the present disclosure, determining the running code related to the generation of the fault from the code database based on the trigger information may include: determining the running code from the code database based on the code identifier related to the generation of the fault in the trigger information.

[0075] According to the embodiments of the present disclosure, based on the uniqueness of the code identifier, the code fragment containing the code identifier can be quickly queried from the code database through the code identifier, thereby determining the running code related to the fault, thereby improving processing efficiency.

[0076] According to an embodiment of the present disclosure, determining a code identifier from the trigger information in a determination manner that matches the information type of the trigger information may include: determining stack information from the trigger information when the information type of the trigger information includes a running error log type; and determining the code identifier from the stack information.

[0077] According to an embodiment of the present disclosure, stack information can be directly used as a code identifier. Stack information is stored according to the last-in-first-out principle. When a fault occurs, the exception stack trace will show the location where the exception occurred and the order in which the methods are called, which can help understand the source of the fault. Through the stack information, a code fragment with complete semantics can be recalled.

[0078] According to an embodiment of the present disclosure, based on the code identifier related to the fault in the trigger information, the running code is determined from the code database, including: determining the running code that matches the vector data of the code identifier from the code database, wherein the code database includes the running code after vector conversion.

[0079] According to the embodiments of the present disclosure, feature extraction can be performed on the split code blocks, and based on the extracted features, the code blocks can be converted into vector data using vector coding technology to obtain the running code after vector conversion. The code is stored in the form of vector data. The running code related to the fault is obtained by performing a similarity comparison between the vector data of the code identifier and the vector data of the code block.

[0080] Through direct vector comparison, the influence of data structure on matching accuracy is reduced, the processing is simplified, and the accuracy and reliability of extracted running code are improved.

[0081] In an illustrative embodiment, taking a HelloWord project as an example, during the software running phase, the automatic analysis function is triggered by monitoring the running error log. When a fault occurs, the relevant trigger information is extracted according to the running error log. The parameters of the trigger information of an illustrative embodiment may include the interface involved, input parameters, and error stack information. For detailed information, see Table 1.

[0082] Table 1:

[0083]

[0084] Since the software running error log contains stack information, we can extract the stack information and use it as a code identifier to recall the code snippet with complete semantics. The main process is as follows: determine the code identifier through the stack information, and recall the three code blocks of HelloController, HelloService, and RedisUtil in turn, so as to obtain the running code with complete context.

[0085] According to another embodiment of the present disclosure, the code identifier may also include an interface identifier. For trigger information that does not include stack information, multiple recalls may be performed through the interface identifiers involved until a code segment with complete semantics is recalled.

[0086] According to an embodiment of the present disclosure, based on the code identifier related to the fault in the trigger information, the running code is determined from the code database, including: based on the interface identifier, determining from the code database a code block corresponding to the interface identifier; determining from the code block an associated interface identifier associated with the interface identifier; determining from the code database an associated code block corresponding to the associated interface identifier; and obtaining the running code based on the code block and the associated code block.

[0087] According to an embodiment of the present disclosure, a code block and an associated code block represent a plurality of code blocks having a mutual dependency relationship, and a code fragment with a complete context can be combined through the code block and the associated code block.

[0088] In such an implementation, code blocks and associated code blocks are combined into code fragments with complete contexts, thereby improving the information of the entire call link and improving the integrity of the running code.

[0089] According to an embodiment of the present disclosure, determining a code identifier from the trigger information in a determination manner that matches the information type of the trigger information may include: when the information type of the trigger information includes a test report type, determining interface information from the trigger information; and determining the code identifier based on the interface information.

[0090] In an illustrative embodiment, taking a HelloWord project as an example, the project contains three code identifiers, namely HelloController, HelloService, and RedisUtil. It mainly implements a function that returns "Hello <input parameter>" for input. Among them, the HelloController: class is the controller layer, which is responsible for processing user requests and calling service layer methods, and exposing a sayHelloWord() method to the outside world. The HelloService: class is the service layer, which is responsible for processing business logic and providing the domain service queryHelloWord(). The RedisUtil: class is a tool class that is responsible for interacting with the Redis database and providing corresponding configuration information from the cache based on the name.

[0091] During the testing phase, a test report as shown in Table 2 is generated. The parameters of the test report include test scenario, input parameters, expected results, actual results, involved interfaces, and description.

[0092] Table 2:

[0093]

[0094] Since there is no stack information in the test report, the interface identifier of the code block can be determined to be HelloController based on the interface information involved. The code snippet recalled based on HelloController does not have complete semantics, and it is necessary to recall multiple times through the associated interface identifier associated with HelloController until a code snippet with complete semantics is recalled.

[0095] Figure 4 The flowchart of determining associated code blocks according to an embodiment of the present disclosure is schematically shown.

[0096] like Figure 4 As shown, HelloController.sayHelloWord() depends on HelloService.queryHelloWord(), and HelloService.queryHelloWord() depends on RedisUtil.getString(). Therefore, the interface identifier HelloController 410 is associated with the associated interface identifiers HelloService 420 and RedisUtil 430. According to the dependency relationship, the code blocks corresponding to HelloController 410, HelloService 420, and RedisUtil 430 are recalled in turn, and a code snippet with a complete context is obtained.

[0097] The recall process is as follows: based on HelloController.sayHelloWord(), the code block corresponding to HelloController 410 is recalled; based on the dependency of HelloController.sayHelloWord() on HelloService.queryHelloWord(), the code block corresponding to HelloService 420 is recalled in the second round; based on the dependency of HelloService.sayHelloWord() on RedisUtil.getString, the code block corresponding to RedisUtil 430 is recalled in the third round.

[0098] Figure 5 The flowchart of the storage of the running code according to the embodiment of the present disclosure is schematically shown.

[0099] like Figure 5As shown, the running code of the target business can be obtained from the remote warehouse of Git warehouse 510. Git warehouse 510 is a version control system for storing and managing code, which is divided into a local warehouse and a remote warehouse. The local warehouse is located on the developer's own computer, while the remote warehouse is located on a remote server. Through Git warehouse 510, developers can easily perform code version control, collaborative development, and backup operations.

[0100] When monitoring the changes of the running code, the latest code is pulled from the Git repository 510 to achieve synchronization of the running code. The code pulled from the GIT repository can be sent to the code management module 520, and the corresponding create (Create), read (Read), update (Update) and delete (Delete) operations are performed through the code management 521; the running code is split into multiple code blocks through the sharding strategy 522, and the updates are stored in the code database 530. The code blocks can also be converted into vector data through vector encoding technology, and the updates are stored in the code database 530.

[0101] According to an embodiment of the present disclosure, the running code for processing the target business is split according to the splitting granularity of the code block to obtain a code block set, wherein the target business includes multiple business operations and the code block includes the running code for processing a single business operation; and based on the code block set, a code database is determined.

[0102] According to the embodiments of the present disclosure, a suitable splitting granularity can be selected according to the actual situation and requirements of the target business. The running code can be split based on functions, classes, or configuration files, and each code block is ensured to have sufficient context information during the splitting, so that each code block has complete semantic functions. Each code block contains the logical running code for performing a specific task or function, and focuses on processing a single business operation or function.

[0103] According to an embodiment of the present disclosure, the split code blocks can be stored, managed and accessed separately.

[0104] By splitting the running code, complex running code can be split into small-grained code blocks for processing single business operations. In this way, during the fault analysis process, the analysis granularity can be refined, the code related to the fault can be extracted, and the analysis noise can be reduced.

[0105] According to an embodiment of the present disclosure, prompt information is generated based on a running code, trigger information and a prompt template, including: determining a prompt template that matches the information type of the trigger information from a plurality of predetermined prompt templates; and adding the running code and trigger information to a preset field of the prompt template to obtain the prompt information.

[0106] According to an embodiment of the present disclosure, different types of trigger information contain different parameters. For example, when the type of trigger information is a test report, the parameters contained therein may include test scenarios, input parameters, actual results, expected results, interfaces involved, and specific descriptions, etc. When the type of trigger information is an error log, the parameters contained therein may include interfaces involved, input parameters, and stack information, etc. A plurality of different prompt templates may be preset based on the type of trigger information to adapt to the parameters in the corresponding trigger information.

[0107] According to an embodiment of the present disclosure, the preset field is a description item to be updated in the prompt template, corresponding to the parameters in the trigger information and the running code determined based on the trigger information. The preset template is updated by the parameters of the trigger information and the running code to obtain the completed prompt information.

[0108] In an illustrative embodiment, still taking the HelloWord project as an example, when the information type of the trigger information is a running error log type, the prompt information obtained based on the running code and the trigger information may be, for example:

[0109] Prompt word template:

[0110] **Problem Description:**

[0111] I encountered a runtime exception. Please help me analyze the cause of the exception and provide optimization suggestions. The output is in JSON format. The JSON format contains "cause of the problem" and "repair suggestions". The three most valuable repair suggestions are retained.

[0112] Involved interface: HelloController.sayHelloWord()

[0113] Input parameter: null

[0114] **Exception information:**

[0115] java.lang.NullPointerException

[0116] atcom.jd.jdt.chatbot.rpu.general.dm.fanwen.domian.HelloService.queryHelloWord(HelloService.java:18)

[0117] atcom.jd.jdt.chatbot.rpu.general.dm.fanwen.domian.HelloController.sayHelloWord(HelloController.java:18)

[0118] atcom.jd.jdt.kf.FanwenRpuImplTest.testFanWen(FanwenRpuImplTest.java:82)

[0119] **Relevant source code:**

[0120] @Servicepublic class HelloController { @Resource private HelloServicehelloService; public String sayHelloWord(String name) { returnhelloService.queryHelloWord(name);}}

[0121] @Servicepublic class HelloService { @Resource private RedisUtilredisUtil; public String queryHelloWord(String name) { if (name.equals("Zhang San")) { return "Hello, Mr. Zhang";} return "Hello, " + redisUtil.getString(name);}}

[0122] @Servicepublic class RedisUtil { @Resource private JRedisTemplater2mClient; public String getString(String name) { return r2mClient.get(name);}}

[0123] In another illustrative embodiment, still taking the HelloWord project as an example, when the information type of the trigger information is a test report, the prompt information obtained based on the running code and the trigger information can be, for example:

[0124] Prompt word template:

[0125] **Problem description:**

[0126] I received a software test report. Please help me analyze the cause of the exception and provide optimization suggestions. And output in json format. The json format contains "problem cause" and "fix suggestions". Keep the top 3 most valuable fix suggestions

[0127] **Abnormal information:**

[0128] Test scenario: Test the welcome message interface

[0129] Input parameter: Li Si

[0130] Actual result: Hello,

[0131] Expected result: Hello, Li Si

[0132] Involved interface: HelloController.sayHelloWord()

[0133] Description: Did not correctly return "Hello, Li Si"

[0134] **Related source code:**

[0135] @Service

[0136] public class HelloController {

[0137] @Resource

[0138] private HelloService helloService;

[0139] public String sayHelloWord(String name) {

[0140] return helloService.queryHelloWord(name);

[0141] }

[0142] }

[0143] @Service

[0144] public class HelloService {

[0145] @Resource

[0146] private RedisUtil redisUtil;

[0147] public String queryHelloWord(String name) {

[0148] if (name.equals("Zhang San")) {

[0149] return "Hello, Mr. Zhang";

[0150] }

[0151] return "Hello," + redisUtil.getString(name);

[0152] }

[0153] }

[0154] @Service

[0155] public class RedisUtil {

[0156] @Resource

[0157] private JRedisTemplate r2mClient;

[0158] public String getString(String name) {

[0159] return r2mClient.get(name);

[0160] }

[0161] }

[0162] Prompt information is generated using a preset prompt template. The prompt information is rich information updated by combining trigger information and running code, which can help large language models perform accurate analysis and improve fault analysis accuracy.

[0163] According to an embodiment of the present disclosure, prompt information is processed using a large language model to obtain a target analysis result, including: using a large language model to process prompt information to obtain a fault cause analysis result and a fault repair suggestion result; and obtaining a target analysis result based on the fault cause analysis result and the fault repair suggestion result.

[0164] According to the embodiments of the present disclosure, since the prompt information includes a description of the fault, relevant parameters, and running code, the prompt information is processed by a large language model, which can analyze the cause of the fault and provide relevant repair suggestions. The fault cause analysis result may include the root cause of the problem, the factors that cause the fault, etc.; the fault repair suggestion result may be a specific repair method or suggestion provided for the analyzed fault cause, and multiple fault repair suggestion results may be output for the user's reference, and the user can select the most appropriate one as the target analysis result.

[0165] In an illustrative embodiment, still taking the HelloWord project as an example, when the information type of the trigger information is a running error log type, the large language model can output the result:

[0166] {

[0167] "Problem cause": "In the HelloController.sayHelloWord() method, the parameter name passed in is null, causing the HelloService.queryHelloWord(String name) method to try to parse the empty string, thus causing a NullPointerException."

[0168] "Repair suggestion": [

[0169] "1. Make sure that the parameter name passed in when calling the sayHelloWord() method is not null."

[0170] "2. Add parameter validation. When the passed name is null, return a default welcome word or throw an exception to prompt the user to pass in a valid name."

[0171] "3. In the HelloService.queryHelloWord() method, add a judgment condition. When the passed name is empty or contains invalid characters, a default welcome word is returned." ]

[0173] }

[0174] In another exemplary embodiment, still taking the HelloWord project as an example, when the information type of the trigger information is a test report, the large language model can output the result:

[0175] {

[0176] "Problem cause": "When the name passed in is 'Li Si', the return value of RedisUtil.getString(name) is empty, resulting in the final return result being only 'Hello' instead of the expected 'Hello, Li Si'."

[0177] "Repair suggestion": [

[0178] "1. Check the implementation of the RedisUtil.getString(String name) method to ensure that the passed name has a corresponding value in Redis."

[0179] "2. In the HelloService.queryHelloWord() method, check whether the return value of redisUtil.getString(name) is empty. If it is empty, return a default welcome word, such as "Hello, user."

[0180] "3. If necessary, you can add a log record in the HelloController.sayHelloWord() method to facilitate troubleshooting." ]

[0182] }

[0183] According to the embodiments of the present disclosure, the large prediction model can quickly locate the cause and provide multiple solutions, thereby improving the richness of the target analysis results and helping to improve the efficiency and accuracy of fault handling.

[0184] According to the above embodiments, the present disclosure elaborates on a method for fault analysis using a large language model, which can effectively reduce the time for developers to locate, reproduce, and debug, improve defect handling efficiency, fault diagnosis, and reduce fault handling time.

[0185] Figure 6 A block diagram of a fault analysis device according to an embodiment of the present disclosure is schematically shown.

[0186] like Figure 6 As shown, the fault analysis device 600 includes a code determination module 610 , an information generation module 620 and a result analysis module 630 .

[0187] The code determination module 610 is used to, in response to receiving trigger information for indicating that a target service has a fault, determine, based on the trigger information, from a code database an operating code related to the fault.

[0188] The information generation module 620 is used to generate prompt information based on the running code, the trigger information and the prompt template.

[0189] The result analysis module 630 is used to process the prompt information using a large language model to obtain a target analysis result.

[0190] According to an embodiment of the present disclosure, the code determination module 610 further includes a type matching submodule, which is used to determine the code identifier from the trigger information in a determination manner that matches the information type of the trigger information.

[0191] According to an embodiment of the present disclosure, the type matching submodule includes a field matching unit and a field value matching unit.

[0192] The field matching unit is used to determine a target field that matches the information type of the trigger information.

[0193] The field value matching unit is used to determine the code identifier based on the field value of the target field.

[0194] According to an embodiment of the present disclosure, the code determination module 610 includes a code identification submodule for determining the running code from the code database based on the code identification related to the fault in the trigger information.

[0195] According to an embodiment of the present disclosure, the fault analysis device 600 further includes a code management module, and the code association module includes a slicing submodule and a storage submodule.

[0196] The slicing submodule is used to split the running code for processing the target business according to the splitting granularity of the code block to obtain a set of code blocks, wherein the target business includes multiple business operations and the code block includes the running code for processing a single business operation.

[0197] The storage submodule is used to determine the code database based on the code block set.

[0198] According to an embodiment of the present disclosure, the code identification submodule includes a vector matching unit for determining an operating code matching the vector data of the code identification from a code database, wherein the code database includes the operating code after vector conversion.

[0199] According to an embodiment of the present disclosure, the code identification submodule further includes a code block determination unit, an associated identification determination unit, an associated code block determination unit, and a running code determination unit.

[0200] The code block determining unit is used to determine the code block corresponding to the interface identifier from the code database based on the interface identifier.

[0201] The associated identifier determining unit is used to determine the associated interface identifier associated with the interface identifier from the code block.

[0202] The associated code block determining unit is used to determine the associated code block corresponding to the associated interface identifier from the code database.

[0203] The running code determining unit is used to obtain the running code based on the code block and the associated code blocks.

[0204] According to an embodiment of the present disclosure, the information generation module 620 includes a template matching unit and an information updating unit.

[0205] The template matching unit is used to determine a prompt template that matches the information type of the trigger information from a plurality of predetermined prompt templates.

[0206] The information update unit is used to add the running code and trigger information to the preset field of the prompt template to obtain the prompt information.

[0207] According to an embodiment of the present disclosure, the result analysis module 630 includes an analysis processing unit and a determination unit.

[0208] The analysis and processing unit is used to use the large language model to process the prompt information to obtain the fault cause analysis results and fault repair suggestion results.

[0209] The determination unit is used to obtain a target analysis result based on the fault cause analysis result and the fault repair suggestion result.

[0210] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging circuits, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

[0211] For example, any multiple of the code determination module 610, the information generation module 620, and the result analysis module 630 can be combined in one module / unit / sub-unit for implementation, or any one of the modules / units / sub-units can be split into multiple modules / units / sub-units. Alternatively, at least part of the functions of one or more of these modules / units / sub-units can be combined with at least part of the functions of other modules / units / sub-units and implemented in one module / unit / sub-unit. According to an embodiment of the present disclosure, at least one of the code determination module 610, the information generation module 620, and the result analysis module 630 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware or in a suitable combination of any of them. Alternatively, at least one of the code determination module 610 , the information generation module 620 , and the result analysis module 630 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be performed.

[0212] It should be noted that the data processing system part in the embodiments of the present disclosure corresponds to the data processing method part in the embodiments of the present disclosure. The description of the data processing system part specifically refers to the data processing method part, which will not be repeated here.

[0213] Figure 7 A block diagram of an electronic device suitable for implementing the above-described fault analysis method according to an embodiment of the present disclosure is schematically shown. Figure 7 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0214] like Figure 7 As shown, the electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 to a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include an onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0215] In RAM 703, various programs and data required for the operation of electronic device 700 are stored. Processor 701, ROM 702 and RAM 703 are connected to each other via bus 704. Processor 701 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 702 and / or RAM 703. It should be noted that the program can also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.

[0216] According to an embodiment of the present disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to the bus 704. The system 700 may further include one or more of the following components connected to the input / output (I / O) interface 705: an input portion 706 including a keyboard, a mouse, etc.; an output portion 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 708 including a hard disk, etc.; and a communication portion 709 including a network interface card such as a LAN card, a modem, etc. The communication portion 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the input / output (I / O) interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage portion 708 as needed.

[0217] According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0218] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0219] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

[0220] For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 702 and / or the RAM 703 described above and / or one or more memories other than the ROM 702 and the RAM 703 .

[0221] An embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method provided by the embodiment of the present disclosure. When the computer program product runs on an electronic device, the program code is used to enable the electronic device to implement the fault analysis method provided by the embodiment of the present disclosure.

[0222] When the computer program is executed by the processor 701, the above functions defined in the system / device of the embodiment of the present disclosure are executed. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0223] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 709, and / or installed from the removable medium 711. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0224] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0225] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It can be understood by those skilled in the art that the features recorded in the various embodiments and / or claims of the present disclosure can be combined and / or combined in a variety of ways, even if such a combination or combination is not explicitly recorded in the present disclosure. In particular, without departing from the spirit and teaching of the present disclosure, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0226] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A fault analysis method, comprising: In response to receiving trigger information indicating that a target service has a fault, determining, based on the trigger information, from a code database an operating code related to the fault; Generate prompt information based on the running code, the trigger information and the prompt template; as well as The prompt information is processed using a large language model to obtain a target analysis result.

2. The method according to claim 1, wherein: The determining, based on the trigger information, from a code database, an operating code related to the generation of the fault comprises: The running code is determined from the code database based on a code identifier related to the fault in the trigger information.

3. The method according to claim 1 or 2, further comprising: The code identifier is determined from the trigger information in a determination manner that matches the information type of the trigger information.

4. The method according to claim 3, wherein: The determining the code identifier from the trigger information in a determination manner that matches the information type of the trigger information includes: determining a target field that matches the information type of the trigger information; and The code identifier is determined based on the field value of the target field.

5. The method according to claim 2, wherein: The code identification includes stack information; The determining the running code from the code database based on the code identifier related to the fault in the trigger information includes: The running code matching the vector data of the code identifier is determined from the code database, wherein the code database includes the running code after vector conversion.

6. The method according to claim 2, wherein: The code identifier includes an interface identifier; The determining the running code from the code database based on the code identifier related to the fault in the trigger information includes: Based on the interface identifier, determining a code block corresponding to the interface identifier from the code database; Determining, from the code block, an associated interface identifier associated with the interface identifier; Determining from the code database an associated code block corresponding to the associated interface identifier; and The running code is obtained based on the code block and the associated code block.

7. The method according to claim 1 or 5, further comprising: Splitting the running code for processing the target business according to the splitting granularity of the code blocks to obtain a set of code blocks, wherein the target business includes multiple business operations and the code blocks include the running code for processing a single business operation; and Based on the code block set, the code database is determined.

8. The method of claim 1, wherein: The generating prompt information based on the running code, the trigger information and the prompt template includes: Determining the prompt template that matches the information type of the trigger information from a plurality of predetermined prompt templates; and The running code and the trigger information are added to the preset fields of the prompt template to obtain the prompt information.

9. The method according to claim 1, wherein: The using of the large language model to process the prompt information to obtain a target analysis result includes: Processing the prompt information using the large language model to obtain a fault cause analysis result and a fault repair suggestion result; and Based on the fault cause analysis result and the fault repair suggestion result, the target analysis result is obtained.

10. A fault analysis device, comprising: A code determination module, configured to, in response to receiving trigger information indicating that a target service has a fault, determine, based on the trigger information, from a code database an operation code associated with the fault; An information generation module, used to generate prompt information based on the running code, the trigger information and the prompt template; as well as The result analysis module is used to process the prompt information using a large language model to obtain a target analysis result.

11. An electronic device, comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the method according to any one of claims 1 to 9.

13. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 9.

Citation Information

Cited By

  • System exception positioning notification method and device, computer equipment and storage medium

    CN119621549A

  • System anomaly positioning notification method and device, computer device, and storage medium

    CN119621549B