Methods, devices, electronic equipment and storage media for improving the resilience of business systems

Abstract

This application proposes a method, apparatus, electronic device, and storage medium for improving the resilience of a business system. The method includes: automatically obtaining a fault case library of the target business system based on the fault review document of the target business system; automatically determining a hardening strategy for hardening the business module by combining the fault case set in the fault case library corresponding to the business module of the target business system; and hardening the business module based on the hardening strategy, thereby helping to improve the resilience of the business system.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to methods, apparatuses, electronic devices and storage media for improving the resilience of business systems. Background Technology

[0002] Currently, in scenarios involving enhancing the resilience of business systems, the common approach involves manually analyzing fault debriefing documents of the target business system. Based on the analysis results, operations or development personnel manually harden the corresponding business modules within the system to enhance the overall fault tolerance and recovery capabilities. However, this manual approach suffers from inefficiency, slow response times, and the potential to overlook critical risks. Furthermore, it is limited by personnel experience and subjective judgment, making it difficult to effectively improve the resilience of business systems. Summary of the Invention

[0003] This application proposes a method, apparatus, electronic device, and storage medium for improving the resilience of a business system.

[0004] One embodiment of this application proposes a method for improving the resilience of a business system. The method includes: determining a fault case library for the target business system based on fault review documents; for any business module in the target business system, obtaining a set of candidate fault cases corresponding to the business module from the fault case library; clustering the fault cases in the candidate fault case set to obtain multiple fault case clusters; for any fault case cluster among the multiple fault case clusters, determining the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode; if the target fault root cause type matches one of the preset fault root cause types, determining a hardening strategy corresponding to the fault mode based on the target fault root cause type; and hardening the business module according to the hardening strategy.

[0005] The business system resilience enhancement method of this application embodiment determines a fault case library for the target business system based on the fault review document of the target business system; for any business module in the target business system, a set of candidate fault cases corresponding to the business module is obtained from the fault case library; the fault cases in the candidate fault case sets are clustered to obtain multiple fault case clusters; for any fault case cluster, the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode are determined; if the target fault root cause type matches one of the preset fault root cause types, a hardening strategy corresponding to the fault mode is determined based on the target fault root cause type; and the business module is hardened according to the hardening strategy. Thus, based on the fault review document of the target business system, a fault case library for the target business system is automatically obtained, and a hardening strategy for hardening the business module is automatically determined by combining the set of fault cases in the fault case library corresponding to the business module of the target business system, and the business module is hardened according to the hardening strategy, thereby helping to improve the resilience of the business system.

[0006] Another embodiment of this application proposes a business system resilience enhancement device, the device comprising: a first determining module, configured to determine a fault case library of the target business system based on fault review documents of the target business system; a first obtaining module, configured to obtain a set of candidate fault cases corresponding to any business module in the target business system from the fault case library; a clustering processing module, configured to perform clustering processing on the fault cases in the set of candidate fault cases to obtain multiple fault case clusters; a second determining module, configured to determine a fault mode corresponding to any fault case cluster and a target fault root cause type corresponding to the fault mode for any fault case cluster among the multiple fault case clusters; a third determining module, configured to determine a hardening strategy corresponding to the fault mode based on the target fault root cause type if the target fault root cause type matches one of the preset fault root cause types; and a hardening processing module, configured to harden the business module according to the hardening strategy.

[0007] The business system resilience enhancement device of this application embodiment determines a fault case library for the target business system based on the fault review document of the target business system; for any business module in the target business system, it obtains a set of candidate fault cases corresponding to the business module from the fault case library; it performs clustering processing on the fault cases in the candidate fault case sets to obtain multiple fault case clusters; for any fault case cluster among the multiple fault case clusters, it determines the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode; if the target fault root cause type matches one of the preset fault root cause types, it determines the hardening strategy corresponding to the fault mode based on the target fault root cause type; and it hardens the business module according to the hardening strategy. Thus, based on the fault review document of the target business system, the fault case library of the target business system is automatically obtained, and combined with the set of fault cases in the fault case library corresponding to the business modules of the target business system, a hardening strategy for hardening the business module is automatically determined, and the business module is hardened based on the hardening strategy, thereby helping to improve the resilience of the business system.

[0008] Another embodiment of this application proposes an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the business system resilience enhancement method of this application embodiment.

[0009] Another embodiment of this application proposes a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the business system resilience enhancement method disclosed in the embodiments of this application.

[0010] Another embodiment of this application proposes a computer program product, including a computer program that, when executed by a processor, implements the business system resilience enhancement method of this application.

[0011] Other effects of the above-mentioned alternative methods will be described below in conjunction with specific embodiments. Attached Figure Description

[0012] The accompanying drawings are provided for a better understanding of this solution and do not constitute a limitation of this application. Wherein:

[0013] Figure 1 This is a flowchart illustrating a method for enhancing the resilience of a business system according to an embodiment of this application.

[0014] Figure 2 This is a flowchart illustrating a business system resilience enhancement method according to another embodiment of this application.

[0015] Figure 3This is a flowchart illustrating a method for enhancing the resilience of a business system according to another embodiment of this application.

[0016] Figure 4 This is a schematic diagram of the structure of a business system resilience enhancement device according to an embodiment of this application.

[0017] Figure 5 This is a block diagram of an electronic device according to an embodiment of the present application. Detailed Implementation

[0018] Embodiments of the present invention are described in detail below. Examples of these embodiments are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0019] The following description, with reference to the accompanying drawings, outlines a method, apparatus, electronic device, and storage medium for enhancing the resilience of business systems according to embodiments of this application.

[0020] Figure 1 This is a flowchart illustrating a business system resilience enhancement method according to an embodiment of this application. It should be noted that the execution entity of the business system resilience enhancement method provided in this embodiment is a business system resilience enhancement device, which can be implemented by software and / or hardware. In this embodiment, the business system resilience enhancement device can be an electronic device, or it can be configured in an electronic device to enable the electronic device to have business system resilience enhancement functionality. It should also be noted that the electronic device in this embodiment can also be configured with a target business system. The target business system in this embodiment can be any type of business system; for example, the target business system can be an e-commerce platform system. This embodiment does not specifically limit the target business system.

[0021] In this embodiment, the electronic device may include, but is not limited to, terminal devices and servers, etc. This embodiment does not specifically limit the electronic device.

[0022] like Figure 1 As shown, the method for improving the resilience of this business system may include: Step 101: Based on the fault review documents of the target business system, determine the fault case library of the target business system.

[0023] In some embodiments, key information can be extracted from the fault review documents of the target business system, and structured information of corresponding fault cases can be formed based on the extracted key information. Based on the structured information of the fault cases, a fault case library of the target business system can be constructed.

[0024] In some embodiments, a trained Natural Language Processing (NLP) model can be used to extract key information from the fault review documents of the target business system, and structured information of the corresponding fault cases can be formed based on the extracted key information. Based on the structured information of the fault cases, a fault case library of the target business system can be constructed.

[0025] In other embodiments, a rule engine can be used to extract key information from the fault review documents of the target business system and form structured information of fault cases based on the extracted key information.

[0026] The structured information may include: basic fault information, fault problem description information, detailed fault root cause information, fault root cause type, fault handling process, and fault solution.

[0027] The basic fault information may include, but is not limited to, fault identification information, fault duration, fault level, and the business module in which the fault occurs.

[0028] Among them, the root cause types of failures may include, but are not limited to: code defect root cause types, configuration error root cause types, dependency failure root cause types, data problem root cause types, process vulnerability root cause types, performance bottleneck root cause types, and monitoring blind spot root cause types.

[0029] Among them, the monitoring blind spot root cause type refers to a type of fault root cause where, due to the failure to pre-configure effective monitoring probes for specific business logic, component interfaces, or operating status during the system design, deployment, or operation and maintenance phases, the relevant faults cannot be detected, recorded, or alarmed in a timely manner when they occur, thus the root cause of such faults can be attributed to the lack of monitoring coverage.

[0030] In some embodiments, the fault debriefing document may also include: multiple core fault debriefing questions for the fault in the fault case and the corresponding answers to each of the multiple core fault debriefing questions. Correspondingly, the root cause type of the fault in the fault case can be determined based on the multiple core fault debriefing questions and their corresponding answers.

[0031] It should be noted that the document format of the fault review document in this embodiment is Word, PDF, etc., but this embodiment does not make specific limitations on the document format of the fault review document.

[0032] Step 102: For any business module in the target business system, obtain the set of candidate fault cases corresponding to the business module from the fault case library.

[0033] In this embodiment, the target business system may include multiple business modules. For any business module, fault cases matching the business module can be obtained from the fault case library, and a set of candidate fault cases corresponding to the business module can be obtained based on the obtained fault cases.

[0034] Step 103: Cluster the fault cases in the candidate fault case set to obtain multiple fault case clusters.

[0035] In some embodiments, a possible implementation of clustering fault cases in the candidate fault case set to obtain multiple fault case clusters is as follows: determine the structured information of each fault case in the candidate fault case set from the fault case library; determine the case representation features of each fault case in the candidate fault case set based on the structured information; and cluster the fault cases in the candidate fault case set based on the case representation features to obtain multiple fault case clusters.

[0036] Among them, the similarity between the case representation features of any two fault cases in the fault case cluster is greater than or equal to a preset similarity threshold.

[0037] The preset similarity threshold is a similarity threshold set in advance according to actual needs, and this embodiment does not specifically limit it.

[0038] In some embodiments, a trained text encoder can be used to vectorize the structured information of each fault case in the candidate fault case set to obtain the case representation features of each fault case in the candidate fault case set.

[0039] Step 104: For any one of the multiple fault case clusters, determine the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode.

[0040] In some embodiments, common feature analysis can be performed on the fault cases included in the fault case cluster to obtain the common feature analysis results; based on the common feature analysis results, the fault mode corresponding to the fault case cluster can be determined; and the target fault root cause type corresponding to the fault mode can be determined.

[0041] In some embodiments, the target root cause type corresponding to the fault mode can be determined based on a pre-saved correspondence between fault modes and root cause types.

[0042] In other embodiments, the target fault root cause type corresponding to the fault mode can be determined using a trained fault root cause classification model. Thus, the target fault root cause type corresponding to the fault mode is conveniently and accurately obtained through the fault root cause classification model.

[0043] Step 105: If the target fault root cause type matches one of the preset fault root cause types, determine the hardening strategy corresponding to the fault mode based on the target fault root cause type.

[0044] In some embodiments, based on the correspondence between the root cause type, the fault mode, and the hardening strategy, if the target root cause type matches one of the preset root cause types, the hardening strategy corresponding to the fault mode can be determined according to the target root cause type.

[0045] The preset root cause types of failures may include, but are not limited to: code defect root cause type, process vulnerability root cause type, monitoring blind spot root cause type, performance bottleneck root cause type, and configuration error root cause type.

[0046] Step 106: Strengthen the business modules according to the strengthening strategy.

[0047] In some embodiments, when the target root cause type of the failure mode is a code defect root cause type, the hardening strategy is used to instruct the determination of corresponding test cases for failure cases in the failure case cluster and to execute the test cases to test the business module.

[0048] In other embodiments, when the target root cause type of the failure mode is a process vulnerability root cause type, the hardening strategy is used to instruct the business module to be enhanced based on the failure cases in the failure case cluster.

[0049] In other embodiments, when the target root cause type of the fault mode is a monitoring blind spot root cause type, the hardening strategy is used to indicate the recommended monitoring indicators and alarm rules for the business module based on the fault cases in the fault case cluster.

[0050] In other embodiments, when the target root cause type of the failure mode is a configuration error root cause type, the hardening strategy is used to instruct the configuration information of the service module to be checked periodically at a first time interval, and when the configuration check result indicates that there is an error in the configuration information, a prompt message is sent to the person in charge of the service module, wherein the prompt message is used to indicate that there is an error in the configuration information.

[0051] In other embodiments, when the target root cause type of the failure mode is a performance bottleneck root cause type, the hardening strategy is used to instruct the service module to undergo periodic performance testing at a second time interval.

[0052] The first time interval and the second time interval can be the same time interval or different time intervals; this embodiment does not specifically limit this.

[0053] The business system resilience enhancement method provided in this application involves: determining a fault case library for the target business system based on its fault review documents; obtaining a set of candidate fault cases corresponding to any business module in the target business system from the fault case library; clustering the fault cases in the candidate fault case sets to obtain multiple fault case clusters; determining the fault mode corresponding to any fault case cluster and the target fault root cause type corresponding to the fault mode for any fault case cluster; determining a hardening strategy corresponding to the fault mode based on the target fault root cause type when the target fault root cause type matches one of the preset fault root cause types; and hardening the business module according to the hardening strategy. Thus, based on the fault review documents of the target business system, a fault case library for the target business system is automatically obtained, and a hardening strategy for hardening the business module is automatically determined by combining the set of fault cases corresponding to the business modules in the fault case library, and the business module is hardened based on the hardening strategy, thereby helping to improve the resilience of the business system.

[0054] Based on the above embodiments, in order to enable relevant personnel to easily obtain information on the fault risk of the business functions of the target business system, the following describes the determination of the fault risk value of the business module by combining a set of candidate fault cases. Then, based on the fault risk values ​​of each business module in the target business system, the business modules in the target business system are sorted, and the sorting results are output. To clearly understand this process, the following describes... Figure 2 The process is described exemplarily.

[0055] Figure 2 This is a flowchart illustrating a business system resilience enhancement method according to another embodiment of this application.

[0056] like Figure 2 As shown, the method also includes: Step 201: Based on the root cause type of each fault case in the candidate fault case set, group the candidate fault case set to obtain multiple fault case groups, where the fault cases in the fault case group correspond to the same root cause type.

[0057] Step 202: For any fault case group, determine the first fault risk value corresponding to the fault case group based on the number of fault cases in the fault case group and the fault root cause type corresponding to the fault case group.

[0058] In some embodiments, for any fault case group, the number of fault cases in the fault case group is counted to obtain the number of fault cases in the fault case group.

[0059] In some embodiments, a corresponding fault risk calculation formula can be obtained based on the fault root cause type corresponding to the fault case group, and a first fault risk value corresponding to the fault case group can be determined by the fault risk calculation formula and the number of fault cases.

[0060] Step 203: Determine the second fault risk value of the business module based on the first fault risk value corresponding to each fault case group.

[0061] In some embodiments, the first fault risk values ​​corresponding to each fault case group can be summed to obtain the second fault risk value of the business module.

[0062] It should be noted that a higher second fault risk value indicates a higher risk of failure for that business module, and vice versa.

[0063] Step 204: Sort the business modules in the target business system according to the second fault risk value of each business module from high to low, and obtain the sorting result.

[0064] Step 205: Obtain the top N business modules from the sorting results and output the top N business modules, where N is an integer greater than 1.

[0065] In some embodiments, the sorting results can be output in a display manner, for example, by displaying the sorting results in a Kanban panel, or in other ways. This embodiment does not specifically limit the way the sorting results are output.

[0066] In some embodiments, to facilitate relevant personnel in knowing the number of failure cases under various root cause types in any business module in the sorting results, the number of failure cases under various root cause types in that business module can also be output.

[0067] Based on the above embodiments, in order to enable relevant personnel to know about business modules that lack effective monitoring, when it is determined that there are fault cases in the candidate fault case set that are of the type of monitoring blind spot root cause, the business modules are marked with preset tags and the marked business modules are output. The preset tags are used to indicate that the business modules lack effective monitoring.

[0068] For example, marked business modules can be displayed through a dashboard panel, allowing relevant personnel to identify the lack of effective monitoring of a particular business module by using preset markings.

[0069] In other embodiments, in order to enable relevant personnel to easily identify the weak links in the development process of the target business system, after obtaining the fault case library of the target business system, for any fault case in the fault case library, the target link corresponding to the fault case can be obtained from the fault case library, wherein the target link is the link in the development process in which the fault case was not found to be faulty; based on the target link corresponding to each fault case in the fault case library, the failure rate of each link in the development process is determined.

[0070] The failure rate of this stage is the ratio of the number of first cases corresponding to this stage to the total number of failure cases in the failure case library. The number of first cases is the number of first target failure cases in the failure case library, where the failure in the first target failure case was not detected by this stage.

[0071] It can be understood that if any fault case in the fault case library is not detected by this step, then the fault case is called the first target fault case.

[0072] The R&D process in this embodiment may include multiple stages, including but not limited to: code review, testing, and online acceptance.

[0073] To ensure a clear understanding of this application, the following will be combined with... Figure 3 The method of this embodiment is described by way of example.

[0074] Figure 3 This is a flowchart illustrating a method for enhancing the resilience of a business system according to another embodiment of this application.

[0075] like Figure 3 As shown, it may include: Step 301: Obtain the fault review document of the target business system.

[0076] Step 302: Construct a fault case library for the target business system based on the fault review document.

[0077] In some embodiments, the field values ​​corresponding to the fault problem description field and the fault impact duration field can be extracted from the fault review document through a rule engine, and the fault review document can be named entity recognition through an NLP model. Based on the named entity recognition results and the results extracted by the rule engine, a fault case library of the target business system can be constructed.

[0078] Step 303: For any business module in the target business system, obtain the set of candidate fault cases corresponding to the business module and the structured information of each fault case in the set of candidate fault cases from the fault case library.

[0079] Step 304: Perform vector representation on the structured information of each fault case in the candidate fault case set to obtain the case representation features of each fault case in the candidate fault case set.

[0080] Step 305: Based on the case representation features, cluster the fault cases in the candidate fault case set to obtain multiple case clusters, and determine the fault mode corresponding to each case cluster and the target fault root cause type corresponding to the fault mode.

[0081] Step 306: If the target fault root cause type matches one of the preset fault root cause types, determine the hardening strategy corresponding to the fault mode according to the target fault root cause type, and harden the business module according to the hardening strategy.

[0082] Step 307: Based on the candidate fault case set, determine the second fault risk value of the business module, and sort the business modules in the target business system according to the second fault risk value of each business module in the target business system from high to low, obtain the sorting result, and output the top N business modules in the sorting result.

[0083] Corresponding to the business system resilience enhancement methods provided in the above embodiments, one embodiment of this application also provides a business system resilience enhancement device. Since the business system resilience enhancement device provided in this application corresponds to the business system resilience enhancement methods provided in the above embodiments, the implementation methods of the business system resilience enhancement methods are also applicable to the business system resilience enhancement device provided in this embodiment, and will not be described in detail in this embodiment.

[0084] Figure 4 This is a schematic diagram of the structure of a business system resilience enhancement device according to an embodiment of this application.

[0085] like Figure 4 As shown, the business system resilience enhancement device 400 includes: a first determination module 401, a first acquisition module 402, a clustering processing module 403, a second determination module 404, a third determination module 405, and a reinforcement processing module 406, wherein: The first determination module 401 is used to determine the fault case library of the target business system based on the fault review documents of the target business system.

[0086] The first acquisition module 402 is used to acquire a set of candidate fault cases corresponding to any business module in the target business system from the fault case library.

[0087] Clustering module 403 is used to cluster fault cases in the candidate fault case set to obtain multiple fault case clusters.

[0088] The second determining module 404 is used to determine the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode for any one of the multiple fault case clusters.

[0089] The third determination module 405 is used to determine the hardening strategy corresponding to the fault mode based on the target fault root cause type when the target fault root cause type matches one of the preset fault root cause types.

[0090] The hardening module 406 is used to harden the business modules according to the hardening strategy.

[0091] In one embodiment of this application, the clustering processing module 403 is specifically used to: determine the structured information of each fault case in the candidate fault case set from the fault case library; determine the case representation features of each fault case in the candidate fault case set according to the structured information; and cluster the fault cases in the candidate fault case set according to the case representation features to obtain multiple fault case clusters.

[0092] In one embodiment of this application, the second determining module 404 is specifically used for: performing common feature analysis on the fault cases included in the fault case cluster to obtain common feature analysis results; determining the fault mode corresponding to the fault case cluster based on the common feature analysis results; and determining the target fault root cause type corresponding to the fault mode.

[0093] In one embodiment of this application, the device may further include: The risk analysis module is used to group the candidate failure case set according to the root cause type of each failure case in the candidate failure case set to obtain multiple failure case groups, where failure cases in a failure case group correspond to the same root cause type. For any failure case group, a first failure risk value is determined based on the number of failure cases in the failure case group and the corresponding root cause type. A second failure risk value is determined based on the first failure risk value of each failure case group. The business modules in the target business system are sorted in descending order of their second failure risk values ​​to obtain a sorting result. The top N business modules are obtained from the sorting result and output, where N is an integer greater than 1.

[0094] In one embodiment of this application, the device may further include: The marking processing module is used to mark the business module with a preset mark when it is determined that there is a failure case in the candidate failure case set whose failure root cause type is the monitoring blind spot root cause type, and output the marked business module. The preset mark is used to indicate that the business module lacks effective monitoring.

[0095] In one embodiment of this application, the device may further include: The case output module is used to output a set of candidate failure cases when the second failure risk value of a business module exceeds a preset risk threshold and a code editing operation for the business module is received.

[0096] In one embodiment of this application, when the target fault root cause type is a code defect type, the hardening strategy is used to instruct the determination of corresponding test cases for fault cases in the fault case cluster, and to execute the test cases to test the business module.

[0097] The business system resilience enhancement device of this application embodiment determines a fault case library for the target business system based on the fault review document of the target business system; for any business module in the target business system, it obtains a set of candidate fault cases corresponding to the business module from the fault case library; it performs clustering processing on the fault cases in the candidate fault case sets to obtain multiple fault case clusters; for any fault case cluster among the multiple fault case clusters, it determines the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode; if the target fault root cause type matches one of the preset fault root cause types, it determines the hardening strategy corresponding to the fault mode based on the target fault root cause type; and it performs hardening processing on the business module according to the hardening strategy. Thus, based on the fault review document of the target business system, the fault case library of the target business system is automatically obtained, and combined with the set of fault cases in the fault case library corresponding to the business modules of the target business system, a hardening strategy for hardening the business module is automatically determined, and the business module is hardened based on the hardening strategy, thereby helping to improve the resilience of the business system.

[0098] According to embodiments of this application, this application also provides an electronic device.

[0099] Figure 5 This is a block diagram of an electronic device according to an embodiment of the present application.

[0100] like Figure 5 As shown, the electronic device includes: The memory 501, the processor 502, and the computer instructions stored in the memory 501 and executable on the processor 502.

[0101] When processor 502 executes instructions, it implements the business system resilience enhancement method provided in the above embodiments.

[0102] Furthermore, electronic devices also include: Communication interface 503 is used for communication between memory 501 and processor 502.

[0103] Memory 501 is used to store computer instructions that can be executed on processor 502.

[0104] Memory 501 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0105] The processor 502 is used to implement the business system resilience enhancement method of the above embodiments when executing the program.

[0106] If the memory 501, processor 502, and communication interface 503 are implemented independently, then the communication interface 503, memory 501, and processor 502 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0107] Optionally, in a specific implementation, if the memory 501, processor 502, and communication interface 503 are integrated on a single chip, then the memory 501, processor 502, and communication interface 503 can communicate with each other through an internal interface.

[0108] Processor 502 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0109] This application also proposes a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the business system resilience enhancement method disclosed in the embodiments of this application.

[0110] This application also proposes a computer program product, including a computer program that, when executed by a processor, implements the business system resilience enhancement method in the embodiments of this application.

[0111] It should be noted that the acquisition, transmission, storage, use, and processing of data in this application comply with the relevant provisions of laws and regulations.

[0112] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0113] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0114] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0115] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0116] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0117] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0118] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0119] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A method for improving the resilience of a business system, characterized in that, The method includes: Based on the fault review documents of the target business system, a fault case library for the target business system is determined; For any business module in the target business system, obtain a set of candidate fault cases corresponding to the business module from the fault case library; Clustering is performed on the fault cases in the candidate fault case set to obtain multiple fault case clusters; For any one of the multiple fault case clusters, determine the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode; If the target fault cause type matches one of the preset fault cause types, the hardening strategy corresponding to the fault mode is determined according to the target fault cause type. The business module is reinforced according to the reinforcement strategy.

2. The method as described in claim 1, characterized in that, The clustering process of the fault cases in the candidate fault case set yields multiple fault case clusters, including: From the fault case library, determine the structured information of each fault case in the candidate fault case set; Based on the structured information, the case representation features of each fault case in the candidate fault case set are determined respectively; Based on the case representation features, the fault cases in the candidate fault case set are clustered to obtain multiple fault case clusters.

3. The method as described in claim 1, characterized in that, Determining the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode includes: A common feature analysis is performed on the fault cases included in the fault case cluster to obtain the common feature analysis results; Based on the analysis results of the common features, the fault modes corresponding to the fault case clusters are determined; Determine the target root cause type corresponding to the fault mode.

4. The method as described in claim 1, characterized in that, The method further includes: Based on the root cause type of each fault case in the candidate fault case set, the candidate fault case set is grouped to obtain multiple fault case groups, wherein the fault cases in the fault case group correspond to the same root cause type. For any fault case group, a first fault risk value corresponding to the fault case group is determined based on the number of fault cases in the fault case group and the fault root cause type corresponding to the fault case group. Based on the first fault risk value corresponding to each fault case group, the second fault risk value of the business module is determined; Based on the second fault risk value of each business module in the target business system from high to low, sort the business modules in the target business system to obtain the sorting result; Obtain the top N business modules from the sorting results and output the top N business modules, where N is an integer greater than 1.

5. The method as described in claim 1, characterized in that, The method further includes: If it is determined that there is a fault case in the candidate fault case set that is a monitoring blind spot root cause type, the business module is marked with a preset tag and the marked business module is output. The preset tag is used to indicate that the business module lacks effective monitoring.

6. The method as described in claim 4, characterized in that, The method further includes: If the second fault risk value of the business module exceeds the preset risk threshold and a code editing operation is received for the business module, the candidate fault case set is output.

7. The method as described in claim 4, characterized in that, When the target fault root cause type is a code defect type, the hardening strategy is used to instruct the determination of corresponding test cases for fault cases in the fault case cluster, and to execute the test cases to test the business module.

8. A business system resilience enhancement device, characterized in that, The device includes: The first determining module is used to determine the fault case library of the target business system based on the fault review documents of the target business system. The first acquisition module is used to acquire, for any business module in the target business system, a set of candidate fault cases corresponding to the business module from the fault case library; The clustering processing module is used to cluster the fault cases in the candidate fault case set to obtain multiple fault case clusters; The second determining module is used to determine the fault mode corresponding to the fault case cluster and the target fault root cause type corresponding to the fault mode for any one of the plurality of fault case clusters. The third determining module is used to determine the hardening strategy corresponding to the fault mode based on the target fault root cause type when the target fault root cause type matches one of the preset fault root cause types. The hardening processing module is used to harden the business module according to the hardening strategy.

9. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-7.

Images