CN118260110A

CN118260110A - Fault exercise method, device, computer equipment, storage medium and program product

Info

Publication number: CN118260110A
Application number: CN202410286949.6A
Authority: CN
Inventors: 张海锋
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2024-03-13
Filing date: 2024-03-13
Publication date: 2024-06-28

Abstract

The application relates to the technical field of intelligent data analysis, and particularly discloses a fault drilling method, a fault drilling device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: responding to a plan creation event, and acquiring fault scene information and fault disposal measures corresponding to a plan identifier indicated by the plan creation event from a pre-established plan fault scene library; the scheme fault scene library is established according to fault scene information and fault disposal measures corresponding to the historical scheme; creating a target plan according to fault scene information and fault handling measures corresponding to the plan identification; responding to a fault exercise event aiming at a target plan, and acquiring fault scene information and fault disposal measures corresponding to the target plan from a plan fault scene library according to a plan identification of the target plan; and performing fault exercise based on fault scene information and fault handling measures corresponding to the target plan. By adopting the method, the exercise efficiency can be improved.

Description

Fault exercise method, device, computer equipment, storage medium and program product

Technical Field

The present application relates to the field of intelligent data analysis technology, and in particular, to a fault drilling method, apparatus, computer device, storage medium, and computer program product.

Background

The service continuity management refers to the risk prevention capability of ensuring that the service is normal and effective and can be continuously carried out under the condition of coping with various fault scenes. In the current business continuity management system, online management is mainly carried out through two sub-modules, namely planning and drilling. The plan module is mainly used for maintaining plan information such as system basic information, fault information, disposal methods, emergency contacts and the like; the drilling module is mainly used for regularly developing drilling aiming at a preset scheme, making drilling schemes, submitting drilling reports, result information and the like.

At present, whether a plan or a exercise module is adopted, the function design is single, the initiation of related tasks is actively triggered by service personnel, for example, when the plan is created, the service personnel is required to input the plan information, and when the plan exercise is carried out, the service personnel is required to input the plan information for the second time.

However, this approach requires a large number of redundant repeated operations by the service personnel, resulting in inefficiency of the fault exercise.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a fault exercise method, apparatus, computer device, computer readable storage medium, and computer program product that can improve exercise efficiency.

In a first aspect, the present application provides a fault exercise method, including:

Responding to a plan creation event, and acquiring fault scene information and fault disposal measures corresponding to a plan identifier indicated by the plan creation event from a pre-established plan fault scene library; the plan fault scene library is established according to fault scene information and fault treatment measures corresponding to the historical plan;

creating a target plan according to the fault scene information and fault handling measures corresponding to the plan identification;

Responding to a fault exercise event aiming at the target plan, and acquiring fault scene information and fault treatment measures corresponding to the target plan from the plan fault scene library according to the plan identification of the target plan;

and performing fault exercise based on the fault scene information and fault handling measures corresponding to the target plan.

In one embodiment, the method further comprises:

Responding to a fault scene selection event, and acquiring public fault scene information indicated by the fault scene selection event and fault treatment measures corresponding to the public fault scene information from a public fault scene library which is built in advance;

The creating a target plan according to the fault scene information and the fault handling measures corresponding to the plan identification comprises the following steps:

and creating a target plan according to the public fault scene information, fault handling measures corresponding to the public fault scene information, fault scene information corresponding to the plan identification and the fault handling measures.

In one embodiment, the method further comprises:

Establishing an association relationship between the public fault scene information and the plan identifier in the public fault scene library;

according to the plan identification of the target plan, public fault scene information corresponding to the target plan and fault disposal measures corresponding to the public fault scene information are obtained from the public fault scene library;

The performing fault exercise based on the fault scenario information and fault handling measures corresponding to the target plan includes:

And performing fault exercise based on the fault scene information corresponding to the target plan, the fault handling measures, the public fault scene information corresponding to the target plan and the fault handling measures corresponding to the public fault scene information.

In one embodiment, the common fault scenario library is created by a database creation step, the database creation step comprising:

acquiring a history plan set, wherein each plan in the history plan set comprises fault scene information and fault treatment measures;

Acquiring a preset quantity parameter value, and clustering the history plan set according to the quantity parameter value to acquire a plurality of clustering clusters;

for each cluster, a common fault scenario library is created based on fault scenario information and fault handling measures contained in each history plan in the cluster.

In one embodiment, the method further comprises:

determining exercise object attribute information corresponding to the target plan;

Acquiring a pre-established association relationship between exercise object attribute information and plan reinspection frequency;

Determining the reinspection frequency corresponding to the target plan based on the exercise object attribute information corresponding to the target plan and the association relation;

And creating a re-inspection task corresponding to the target plan according to the re-inspection frequency, wherein the re-inspection task is used for indicating to check and correct fault handling measures of the target plan.

In one embodiment, in response to a fault exercise event for the target plan, according to a plan identifier of the target plan, obtaining fault scenario information and fault handling measures corresponding to the target plan from the plan fault scenario library, including:

determining an exercise frequency for the target protocol in response to an exercise frequency configuration event for the target protocol;

According to the drilling frequency, a fault drilling task of the target plan is established;

Responding to a fault exercise event triggered by aiming at the fault exercise task, and acquiring fault scene information and fault disposal measures corresponding to the target plan from the plan fault scene library according to the plan identification indicated by the fault exercise task.

In one embodiment, the plan identifiers in the plan fault scene library are respectively associated with the plan types to which the identified plans belong;

According to the plan identification of the target plan, obtaining fault scenario information and fault handling measures corresponding to the target plan from the plan fault scenario library, including:

determining a plan type of the target plan according to the plan identification of the target plan;

screening a plan identification set associated with the plan type from the plan fault scene library, and determining fault scene information and fault treatment measures respectively corresponding to each plan identification;

and acquiring fault scene information and fault treatment measures corresponding to the plan identification of the target plan from the fault scene information and fault treatment measures corresponding to the plan identifications respectively.

In a second aspect, the present application also provides a fault exercise device, including:

The first scene information acquisition module is used for responding to a plan creation event and acquiring fault scene information and fault treatment measures corresponding to a plan identifier indicated by the plan creation event from a pre-established plan fault scene library; the plan fault scene library is established according to fault scene information and fault treatment measures corresponding to the historical plan;

the plan creating module is used for creating a target plan according to the fault scene information and the fault handling measures corresponding to the plan identification;

The second scene information acquisition module is used for responding to a fault exercise event aiming at the target plan and acquiring fault scene information and fault treatment measures corresponding to the target plan from the plan fault scene library according to the plan identification of the target plan;

And the fault exercise module is used for performing fault exercise based on the fault scene information and fault handling measures corresponding to the target plan.

In one embodiment, the apparatus further comprises:

The first public fault acquisition module is used for responding to a fault scene selection event and acquiring public fault scene information indicated by the fault scene selection event and fault treatment measures corresponding to the public fault scene information from a public fault scene library which is established in advance;

The plan creation module is further configured to create a target plan according to the public fault scenario information, fault handling measures corresponding to the public fault scenario information, fault scenario information corresponding to the plan identifier, and fault handling measures.

In one embodiment, the apparatus further comprises:

the association relation establishing module is used for establishing association relation between the public fault scene information and the plan identifier in the public fault scene library;

The second public fault acquisition module is used for acquiring public fault scene information corresponding to the target plan and fault treatment measures corresponding to the public fault scene information from the public fault scene library according to the plan identification of the target plan;

and the fault exercise module is also used for performing fault exercise based on the fault scene information corresponding to the target plan, the fault handling measures, the public fault scene information corresponding to the target plan and the fault handling measures corresponding to the public fault scene information.

In one embodiment, the apparatus further comprises: the scene library creating module is used for acquiring a history plan set, wherein each plan in the history plan set comprises fault scene information and fault treatment measures; acquiring a preset quantity parameter value, and clustering the history plan set according to the quantity parameter value to acquire a plurality of clustering clusters; for each cluster, a common fault scenario library is created based on fault scenario information and fault handling measures contained in each history plan in the cluster.

In one embodiment, the apparatus further comprises: the reinspection task creation module is used for determining exercise object attribute information corresponding to the target plan; acquiring a pre-established association relationship between exercise object attribute information and plan reinspection frequency; determining the reinspection frequency corresponding to the target plan based on the exercise object attribute information corresponding to the target plan and the association relation; and creating a re-inspection task corresponding to the target plan according to the re-inspection frequency, wherein the re-inspection task is used for indicating to check and correct fault handling measures of the target plan.

In one embodiment, the second scene information obtaining module is further configured to: determining an exercise frequency for the target protocol in response to an exercise frequency configuration event for the target protocol; according to the drilling frequency, a fault drilling task of the target plan is established; responding to a fault exercise event triggered by aiming at the fault exercise task, and acquiring fault scene information and fault disposal measures corresponding to the target plan from the plan fault scene library according to the plan identification indicated by the fault exercise task.

In one embodiment, the plan identifiers in the plan fault scene library are respectively associated with the plan types to which the identified plans belong; the second scene information acquisition module is further configured to: determining a plan type of the target plan according to the plan identification of the target plan; screening a plan identification set associated with the plan type from the plan fault scene library, and determining fault scene information and fault treatment measures respectively corresponding to each plan identification; and acquiring fault scene information and fault treatment measures corresponding to the plan identification of the target plan from the fault scene information and fault treatment measures corresponding to the plan identifications respectively.

In a third aspect, the present application also provides a computer device comprising a memory storing a computer program and a processor implementing the above-mentioned steps of fault exercise when executing the computer program.

In a fourth aspect, the present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of fault drilling described above.

In a fifth aspect, the application also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of fault drilling described above.

According to the fault exercise method, the device, the computer equipment, the storage medium and the computer program product, as the pre-established plan fault scene library exists, and the plan fault scene library is established according to the fault scene information and the fault treatment measures corresponding to the historical plan, the fault scene that the history stage needs to be exercised to realize system risk prevention can be reflected, so that when the plan needs to be newly established, the fault scene information and the fault treatment measures corresponding to the plan identification indicated by the plan creation event can be acquired from the plan fault scene library in response to the plan creation event, and the target plan is created according to the fault scene information and the fault treatment measures corresponding to the plan identification, thereby avoiding the inefficiency caused by the requirement of manual information input of service personnel when the plan is created. Further, when performing fault exercise for the created plan, fault scene information and fault handling measures corresponding to the target plan can be obtained from a plan fault scene library according to the plan identification of the target plan in response to the fault exercise event for the target plan, and fault exercise is performed based on the fault scene information and the fault handling measures corresponding to the target plan, so that the fault scene information of the plan can be obtained from the plan fault scene library according to the plan identification of the plan for which the exercise is performed in the exercise process, on one hand, low exercise efficiency caused by secondary input of the fault scene information in the exercise process can be avoided, and on the other hand, due to exercise and plan sharing data, data consistency of the exercise and the plan process can be ensured, and the accuracy of the fault exercise is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the related art, the drawings that are required to be used in the embodiments or the related technical descriptions will be briefly described, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.

FIG. 1 is an application environment diagram of a fault drill method in one embodiment;

FIG. 2 is a flow chart of a fault exercise method in one embodiment;

FIG. 3 is a flow chart of a fault exercise method according to another embodiment;

FIG. 4 is a flow chart of database creation steps in another embodiment;

FIG. 5 is a flow chart of a protocol review step in one embodiment;

FIG. 6 is a flow chart of the processing steps in response to a plan drill event in one embodiment;

FIG. 7 is a flow chart illustrating the steps of obtaining data from a pre-project fault scene library in one embodiment;

FIG. 8 is a schematic overall flow chart of a fault exercise method in one embodiment;

FIG. 9 is a block diagram of a fault exercise device in one embodiment;

FIG. 10 is an internal block diagram of a computer device in one embodiment;

Fig. 11 is an internal structural view of a computer device in another embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are both information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to meet the related regulations.

The fault drilling method provided by the embodiment of the application can be applied to an application environment shown in figure 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligence platforms, and the like.

The fault drilling method of the application can be executed by a computer device, and the computer device can be a terminal in fig. 1, a server in fig. 1 or a system formed by the terminal and the server in fig. 1 and is realized through interaction between the terminal and the server. Taking the independent execution of the terminal as an example, the terminal can respond to a plan creation event and acquire fault scene information and fault treatment measures corresponding to a plan identifier indicated by the plan creation event from a pre-established plan fault scene library, wherein the plan fault scene library is established according to the fault scene information and the fault treatment measures corresponding to a historical plan; creating a target plan according to fault scene information and fault handling measures corresponding to the plan identification; responding to a fault exercise event aiming at a target plan, and acquiring fault scene information and fault disposal measures corresponding to the target plan from a plan fault scene library according to a plan identification of the target plan; and performing fault exercise based on fault scene information and fault handling measures corresponding to the target plan.

In an exemplary embodiment, as shown in fig. 2, a fault exercise method is provided, which is illustrated by taking an example that the method is applied to the terminal 102 in fig. 1, and includes the following steps 202 to 208. Wherein:

step 202, responding to a plan creation event, and acquiring fault scene information and fault treatment measures corresponding to a plan identifier indicated by the plan creation event from a pre-established plan fault scene library.

Wherein, the system is aimed at the relevant emergency treatment measure scheme formulated in advance of various fault scenes. The plan fault scene library is established according to fault scene information and fault disposal measures corresponding to the historical plan. The failure scenario information is information for describing a scenario in which a failure occurs, and the failure handling measure is a scheme for performing emergency processing when the failure occurs. In the plan fault scene library, the historical plans are uniquely identified by the plan identification, and the plan identification of each historical plan is stored in association with fault scene information and fault disposal measures corresponding to the historical plans. The protocol identification may be a protocol name or a protocol number.

Specifically, the service personnel can trigger a plan creation event at the terminal and input basic information of the plan, including plan names, plan types, plan related systems, contacts and other plan information, so that the terminal can determine a plan identifier indicated by the plan creation event according to the plan information input by the user, for example, the plan names can be determined as the plan identifiers, and further a pre-established plan fault scene library can be queried according to the plan identifiers, so that fault scene information and fault disposal measures corresponding to the plan identifiers can be obtained.

In an exemplary embodiment, when the terminal does not query the corresponding fault scene information and fault handling measures according to the plan identifier indicated by the plan creation event, the terminal may prompt the service personnel to enter information, and after the service personnel records the fault scene information and the fault handling measures, the terminal may synchronously store the fault scene information and the fault handling process corresponding to the plan identifier to the plan fault scene library, so as to ensure that the fault scene can be directly introduced for performing the subsequent fault exercise.

In an exemplary embodiment, a training sample may be generated according to the plan information, the fault scenario information and the fault handling measures of the historical plan, the generated training sample is used to train a fault handling measure prediction model, the input of the fault handling measure prediction model is the plan information and the fault scenario information, the output is the fault handling measure, further when the terminal does not query the corresponding fault scenario information and the fault handling measure according to the plan identifier indicated by the plan creation event, the terminal may prompt the service personnel to perform information entry, after the service personnel records the fault scenario information, the terminal may predict the fault handling measure corresponding to the plan according to the plan information and the fault scenario information recorded by the service personnel, and recommend the fault handling measure to the service personnel, and the service personnel may directly adopt the recommended fault handling measure to generate the plan, or perform certain modification on the recommended fault handling measure to generate the plan.

Step 204, creating a target plan according to the fault scene information and the fault handling measures corresponding to the plan identification.

Specifically, when the terminal acquires fault scene information and fault handling measures corresponding to the plan identifier, a target plan can be created according to the plan information recorded by service personnel, the acquired fault scene information and fault handling measures and the like.

Step 206, responding to the fault exercise event aiming at the target plan, and acquiring fault scene information and fault disposal measures corresponding to the target plan from a plan fault scene library according to the plan identification of the target plan.

The fault exercise event refers to an event for triggering to perform fault exercise, for example, the fault exercise event may be an event triggered by a fault exercise triggering operation performed by a service person at a terminal for a target plan, and in other embodiments, the fault exercise event may also be an event triggered automatically according to a preset rule.

Specifically, the terminal may determine a plan identifier of the target plan according to the fault exercise event in response to the fault exercise event for the target plan, so that fault scenario information and fault handling measures associated with the plan identifier may be queried from a plan fault scenario library according to the plan identifier, thereby obtaining fault scenario information and fault handling measures corresponding to the target plan.

As an exemplary embodiment, the terminal may create an exercise task in response to an exercise task creation event for a target plan, and may further obtain, in response to a fault exercise event triggered for the exercise task, fault scenario information and fault handling measures corresponding to the target plan from a plan fault scenario library according to a plan identifier indicated by the fault exercise task.

And step 208, performing fault exercise based on the fault scene information and fault handling measures corresponding to the target plan.

The fault exercise is a practice following the principle of chaotic engineering, and various possible production faults and abnormal states are simulated in an exercise object such as a physical machine, a computer cluster and the like to observe the performance of the exercise object and perform corresponding design and optimization, so that the performance and fault tolerance of the exercise object are improved, and the disastrous consequences caused by real emergencies in time are avoided.

Specifically, the terminal may perform fault exercise based on fault scenario information and a fault handling procedure corresponding to the target plan. After fault exercise is completed, business personnel can input exercise result information and submit an exercise report to complete the process.

In the fault exercise method, because the pre-established plan fault scene library is provided and is established according to the fault scene information and the fault handling measures corresponding to the historical plan, the fault scene that needs to be exercised in the historical stage to realize system risk prevention can be reflected, so that when the plan needs to be newly established, the fault scene information and the fault handling measures corresponding to the plan identification indicated by the plan creation event can be acquired from the plan fault scene library in response to the plan creation event, and the target plan is created according to the fault scene information and the fault handling measures corresponding to the plan identification, thereby avoiding the inefficiency caused by the requirement of manually inputting information by service personnel when the plan is created. Further, when performing fault exercise for the created plan, fault scene information and fault handling measures corresponding to the target plan can be obtained from a plan fault scene library according to the plan identification of the target plan in response to the fault exercise event for the target plan, and fault exercise is performed based on the fault scene information and the fault handling measures corresponding to the target plan, so that the fault scene information of the plan can be obtained from the plan fault scene library according to the plan identification of the plan for which the exercise is performed in the exercise process, on one hand, low exercise efficiency caused by secondary input of the fault scene information in the exercise process can be avoided, and on the other hand, due to exercise and plan sharing data, data consistency of the exercise and the plan process can be ensured, and the accuracy of the fault exercise is improved.

In an exemplary embodiment, the fault exercise method of the present application further includes: responding to a fault scene selection event, and acquiring public fault scene information indicated by the fault scene selection event and fault disposal measures corresponding to the public fault scene information from a public fault scene library which is built in advance; creating a target plan according to fault scene information and fault handling measures corresponding to plan identification, wherein the method comprises the following steps: and creating a target plan according to the public fault scenario information, fault handling measures corresponding to the public fault scenario information, fault scenario information corresponding to the plan identification and the fault handling measures.

The public fault scene library stores public fault scene information and fault disposal measures corresponding to the public fault scene information. The public fault scene is mainly unified maintenance aiming at fault scenes which all plans need to be considered, and disposal measures and the like of the plans are the same, such as scene description, emergency disposal measures, emergency contact information and the like related to the fire fault scene. These fault scenarios need to be contained in the plans of the different systems, and the information such as emergency treatment measures should be unified. In order to avoid inconsistent results and tedious operation of the service caused by self-entry of each department, by maintaining a set of public fault scenes, each service can directly introduce relevant public fault scene information from the public fault scenes, thereby ensuring the consistency of the scenes and improving the service processing efficiency.

Specifically, in this embodiment, a public fault scenario library may be pre-established, and when a plan is established, a service person may further perform a fault scenario selection operation to trigger a fault scenario selection event, so that a terminal may obtain public fault scenario information indicated by the fault scenario selection event and a fault handling measure corresponding to the public fault scenario information from the pre-established public fault scenario library in response to the fault scenario selection event, and further when a target plan is established, the target plan may be established according to the public fault scenario information, the fault handling measure corresponding to the public fault scenario information, and the fault scenario information and the fault handling measure corresponding to the plan identifier.

In the above embodiment, since the common fault scenario library is created in advance, when the plan is created, the common fault information and the fault handling measures can be obtained from the common fault scenario library, thereby further improving the fault exercise efficiency.

In an exemplary embodiment, as shown in fig. 3, a fault exercise method is provided, which is illustrated by taking the terminal 102 in fig. 1 as an example, and includes the following steps 302 to 314. Wherein:

Step 302, responding to a plan creation event, and acquiring fault scene information and fault handling measures corresponding to a plan identifier indicated by the plan creation event from a pre-established plan fault scene library.

The scheme fault scene library is established according to fault scene information and fault treatment measures corresponding to the historical scheme.

Step 304, responding to the fault scene selection event, and acquiring public fault scene information indicated by the fault scene selection event and fault disposal measures corresponding to the public fault scene information from a public fault scene library which is established in advance.

Step 306, creating a target plan according to the public fault scenario information, fault handling measures corresponding to the public fault scenario information, fault scenario information corresponding to the plan identification and the fault handling measures.

In step 308, an association relationship between the public fault scenario information and the plan identifier is established in the public fault scenario library.

Specifically, when the target plan is created, in order to ensure that fault scene information does not need to be repeatedly input in the subsequent drilling process, an association relationship between the common fault scene information and the plan identification can be established in the common fault scene library, so that the common fault scene information and fault treatment measures of the target plan can be conveniently queried from the common fault scene library according to the plan identification of the target plan in the fault drilling process.

In step 310, in response to the fault exercise event for the target plan, according to the plan identification of the target plan, fault scenario information and fault handling measures corresponding to the target plan are obtained from the plan fault scenario library.

Step 312, according to the plan identification of the target plan, public fault scenario information corresponding to the target plan and fault handling measures corresponding to the public fault scenario information are obtained from the public fault scenario library.

Specifically, the terminal may query from the public fault scenario library according to the plan identifier corresponding to the target plan, so as to determine public fault scenario information corresponding to the plan identifier and fault handling measures corresponding to the public fault scenario information, and further obtain public fault scenario information corresponding to the target plan and fault handling measures corresponding to the public fault scenario information.

Step 314, performing fault exercise based on the fault scenario information corresponding to the target plan, the fault handling measures, the public fault scenario information corresponding to the target plan, and the fault handling measures corresponding to the public fault scenario information.

Specifically, after obtaining the fault scenario information, the fault handling measure, the public fault scenario information and the fault handling measure corresponding to the target plan, the terminal may perform fault exercise according to the fault scenario information, the fault handling measure, the public fault scenario information and the fault handling measure corresponding to the public fault scenario information.

In the above embodiment, in the fault exercise process, not only the characteristic fault scene information corresponding to the target plan can be obtained from the plan fault scene library, but also the public fault information can be obtained from the public fault scene library, so that the consistency of the plan and the exercise scene is ensured, and the service processing efficiency is improved.

In one exemplary embodiment, the common fault scenario library is created by a database creation step, referring to fig. 4, comprising:

step 402, a history plan set is obtained, wherein each plan in the history plan set contains fault scene information and fault handling measures.

Specifically, the history plan set includes a plurality of history plans, each of which includes fault scenario information and fault handling measures.

Step 404, obtaining a preset number parameter value, and clustering the history plan set according to the number parameter value to obtain a plurality of clusters.

Specifically, the number parameter value refers to a preset value for determining the number of clustering centers, the terminal may acquire the preset number parameter value, and then cluster the historical plan based on fault scene information and fault handling measures included in the historical plan according to the number parameter value by using a clustering algorithm, so as to obtain a plurality of cluster clusters, where the clustering algorithm may be, for example, a k-means algorithm, and the number of cluster clusters obtained by clustering is consistent with the preset number parameter value.

Step 406, for each cluster, creating a common fault scenario library based on fault scenario information and fault handling measures contained in each history plan in the cluster.

Specifically, for each cluster, the terminal may create a common fault scenario library based on fault scenario information and fault handling measures contained in each history plan in the cluster.

In an exemplary embodiment, for each cluster, the terminal may randomly select one history plan from the history plans in the cluster, and store the fault scenario information and the fault handling measures contained in the history plan in a common fault scenario library in an associated manner.

In another exemplary embodiment, for each cluster, the terminal may count occurrence frequencies of fault handling measures of each history plan in the cluster, and store, in a common fault scenario library, fault scenario information associated with the fault handling measure with the highest occurrence frequency in the cluster.

In an exemplary embodiment, the fault exercise method of the present application further includes a plan review step, and referring to fig. 5, the plan review step specifically includes:

Step 502, determining exercise object attribute information corresponding to the target plan.

Where the exercise object refers to a device, product, or system that needs to perform a fault exercise, the exercise object may be a cloud product (e.g., cloud host, block store, etc.), a distributed computer cluster (e.g., kubernetes cluster, abbreviated as K8S cluster), a physical machine, or a virtual machine. The exercise object attribute information may be, for example, an object classification, importance degree, or the number of times of occurrence of a fault of the exercise object.

Step 504, obtaining the pre-established association relationship between the exercise object attribute information and the plan review frequency.

Specifically, in the present application, the association relationship between the object attribute information and the plan review frequency is performed in advance and stored. For example, class a system protocols require a quarter review, class B a year, class C a year, etc.

Step 506, determining the review frequency corresponding to the target plan based on the exercise object attribute information and the association relation corresponding to the target plan.

And step 508, creating a rechecking task corresponding to the target plan according to the rechecking frequency, wherein the rechecking task is used for indicating to check and correct the fault handling measures of the target plan.

Specifically, the terminal may determine the rechecking frequency corresponding to the target plan based on the exercise object attribute information corresponding to the target plan and the pre-established association relationship, and then may create a rechecking task corresponding to the target plan according to the rechecking frequency, where the rechecking task is used to instruct to check and correct the fault handling measure of the target plan.

In the embodiment, the rechecking frequency is configured through the plan attribute, and then the rechecking task is automatically initiated according to the frequency, so that the automatic establishment of the plan rechecking task can be realized, the manual redundant and repeated operation of service personnel is liberated, the operation risk of the system is reduced, and the availability and the friendliness of the system are improved.

In an exemplary embodiment, referring to fig. 6, in response to a fault exercise event for a target plan, according to a plan identification of the target plan, fault scenario information and fault handling measures corresponding to the target plan are obtained from a plan fault scenario library, including:

Step 602, determining a drill frequency of a target plan in response to a drill frequency configuration event for the target plan.

Specifically, the terminal may display a configuration page, and the service personnel may configure the exercise frequency for the target plan on the configuration page to trigger an exercise frequency configuration event for the target plan, and the terminal may determine the exercise frequency of the target plan in response to the exercise frequency configuration event.

Step 604, creating fault exercise tasks of the target plans according to the exercise frequency.

Step 606, in response to a fault exercise event triggered for the fault exercise task, according to the plan identifier indicated by the fault exercise task, obtaining fault scenario information and fault handling measures corresponding to the target plan from a plan fault scenario library.

Specifically, after the exercise frequency is configured, the terminal can create a fault exercise task of the target plan according to the exercise frequency, service personnel can start fault exercise through the created fault exercise task, specifically, service personnel can trigger aiming at the created fault exercise task, and then the terminal can respond to a fault exercise event triggered aiming at the fault exercise task, and according to a plan identification indicated by the fault exercise task, obtain fault scene information and fault treatment measures corresponding to the target plan from a plan fault scene library, so that fault exercise can be realized.

In the embodiment, by automatically creating the plan exercise task, the manual redundant and repeated operation of service personnel is liberated, the operation risk of the system is reduced, and the usability and the friendliness of the system are improved.

In an exemplary embodiment, referring to fig. 7, according to a plan identifier of a target plan, fault scenario information and fault handling measures corresponding to the target plan are obtained from a plan fault scenario library, including:

step 702, determining the plan type of the target plan according to the plan identification of the target plan.

Step 704, screening a plan identification set associated with the plan type from the plan fault scene library, and determining fault scene information and fault treatment measures respectively corresponding to each plan identification.

Step 706, obtaining fault scenario information and fault handling measures corresponding to the plan identification of the target plan from the fault scenario information and fault handling measures corresponding to the plan identifications.

Specifically, in the case fault scene library, the case identifications are respectively associated with the case types to which the identified case belongs, so that when the terminal needs to query the fault scene information and the fault handling measures corresponding to a certain case identification from the case fault scene library, the case types can be determined firstly through the case identifications, a case identification set associated with the case types is screened from the case fault scene library, and the fault scene information and the fault handling measures corresponding to each case identification in the case identification set are determined, thereby greatly reducing the data volume of case identification query, and finally, the fault scene information and the fault handling measures corresponding to the case identifications of the target case are obtained from the fault scene information and the fault handling measures corresponding to each case identification, thereby improving the data query efficiency and further improving the fault drilling efficiency.

In a specific embodiment, a fault exercise method is provided, and is specifically described below with reference to fig. 8:

1. Creating a fault scenario library

In order to realize sharing multiplexing of data, various types of plans and drilling information contents are generalized and refined in the embodiment provided by the application, the multiplexing part is extracted, and a fault scene library is independently created. According to different usage scenarios, the method can be further divided into two categories, namely a public fault scenario and a plan fault scenario.

1) Public fault scenario

The public fault scene is mainly unified maintenance aiming at fault scenes which all plans need to be considered, and disposal measures and the like of the plans are the same, such as scene description, emergency disposal measures, emergency contact information and the like related to the fire fault scene. These fault scenarios need to be contained in the plans of the different systems, and the information such as emergency treatment measures should be unified. In order to avoid inconsistent results and tedious operation of the service caused by self-entry of each department, by maintaining a set of public fault scenes, each service can directly introduce relevant public fault scene information from the public fault scenes, thereby ensuring the consistency of the scenes and improving the service processing efficiency.

2) Plan fault scenario

Aiming at some specific emergency fault scene information of different plans, special fault scene information maintenance can be independently carried out by taking the plans as units. After the special fault scene is maintained for a certain plan, the special fault scene can be automatically introduced in the next step of plan creation without repeated editing. In the subsequent exercise scheme formulation, the special fault scene can be directly selected from the position to perform exercise development, repeated input is avoided, data sharing multiplexing is improved, and the risk of manual operation is reduced.

2. Plan creation and review

After the fault scene library is maintained, the creation of the plan can be started. In the creation process of the plan, basic information of the plan (plan name, plan type, plan related system, contact person, etc.) and fault scene of plan maintenance and corresponding emergency treatment measures need to be entered. It should be noted that, due to the introduced fault scene library, when the fault scene related to the plan information is created, the fault scene library can be directly associated and selected preferentially, no repeated entry of business is needed, unless the fault scene library does not need to be used, a new fault scene of a self-running scene can be entered by self-definition, whether the fault scene is synchronous to the plan fault scene library is supported, if so, the fault scene can be directly introduced for exercise during subsequent exercise.

After the plan is created and approved, periodic plan rechecking work is usually required to be carried out according to the importance degree of a plan association system. In this embodiment, the configuration of the rechecking frequency by the protocol attribute is supported, and then the rechecking task is automatically initiated according to the frequency. For example, after different review frequencies are configured according to importance categories related to the system in the protocol attribute, the system will automatically initiate the protocol review task according to the configured review batch. The review task is mainly to update the relevant content of the plan.

3. Drill creation and development

After creating the plan, emergency exercises of related fault scenes can be developed regularly aiming at the plan. The initiation of the emergency drilling task is supported by a newly added configuration management module when the service is initiated manually through a page, and the drilling task is initiated automatically at regular intervals after the service is configured through parameters. The configuration management module may configure task initiation frequency, create pick policies (polling, random, custom supplements), etc.

After the exercise task is created, business personnel can develop the exercise. Firstly, designating an exercise scheme, and recording basic information (exercise time, exercise site, exercise participators and the like) of exercise and exercise fault scene information. The fault scene to be exercised can be a brand new fault scene newly added by service customization, or can be one or more of fault scene information maintained by directly introducing the corresponding plan of the exercise. After the business completes fault exercise, the exercise result information is required to be input and submitted to an exercise report, and the process is completed.

In the above embodiment, based on the fault scene library, the sharing multiplexing of data is realized, and the configuration management module is newly added, so as to support the automatic initiation of the plan review task and the drilling task. In the planning and drilling maintenance process, the method supports direct introduction of fault scene shared library data in addition to the new addition of the self-defined fault scenes, reduces data redundancy and tedious data entry operation of service personnel under the condition of ensuring the integrity and uniformity of the data, and avoids the risk of manual operation. In the scheme rechecking and exercise creation flow, a configuration management module is added while the manual trigger task of a service person is reserved, and the scheme rechecking task and the exercise task are automatically created after the configuration of related attributes, so that the manual redundant and repeated operation of the service person is liberated, the operation risk of a system is reduced, the availability and the friendliness of the system are improved, and the fault exercise efficiency is improved.

It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a fault exercise device for realizing the fault exercise method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitations in one or more embodiments of the fault exercise device provided below may be referred to above for limitations of the fault exercise method, and will not be repeated here.

In one exemplary embodiment, as shown in fig. 9, there is provided a fault exercise apparatus 900 comprising:

a first scenario information obtaining module 902, configured to obtain, in response to a scenario creation event, fault scenario information and fault handling measures corresponding to a scenario identifier indicated by the scenario creation event from a pre-established scenario fault scenario library; the scheme fault scene library is established according to fault scene information and fault disposal measures corresponding to the historical scheme;

A plan creating module 904, configured to create a target plan according to fault scenario information and fault handling measures corresponding to the plan identifier;

a second scenario information obtaining module 906, configured to obtain, according to a plan identifier of the target plan, fault scenario information and fault handling measures corresponding to the target plan from a plan fault scenario library in response to a fault exercise event for the target plan;

the fault exercise module 908 is configured to perform fault exercise based on fault scenario information and fault handling measures corresponding to the target plan.

According to the fault exercise device, the pre-established plan fault scene library is established according to the fault scene information and the fault treatment measures corresponding to the historical plans, and the fault scene that needs to be exercised in the historical stage to realize system risk prevention can be reflected, so that when a new plan needs to be established, fault scene information and the fault treatment measures corresponding to the plan identification indicated by the plan creation event can be acquired from the plan fault scene library in response to the plan creation event, and a target plan is created according to the fault scene information and the fault treatment measures corresponding to the plan identification, so that inefficiency caused by manual information input of service personnel is avoided when the plan is created. Further, when performing fault exercise for the created plan, fault scene information and fault handling measures corresponding to the target plan can be obtained from a plan fault scene library according to the plan identification of the target plan in response to the fault exercise event for the target plan, and fault exercise is performed based on the fault scene information and the fault handling measures corresponding to the target plan, so that the fault scene information of the plan can be obtained from the plan fault scene library according to the plan identification of the plan for which the exercise is performed in the exercise process, on one hand, low exercise efficiency caused by secondary input of the fault scene information in the exercise process can be avoided, and on the other hand, due to exercise and plan sharing data, data consistency of the exercise and the plan process can be ensured, and the accuracy of the fault exercise is improved.

In an exemplary embodiment, the apparatus further comprises:

The first public fault acquisition module is used for responding to the fault scene selection event and acquiring public fault scene information indicated by the fault scene selection event and fault treatment measures corresponding to the public fault scene information from a public fault scene library which is established in advance;

The plan creation module is further configured to create a target plan according to the public fault scenario information, fault handling measures corresponding to the public fault scenario information, fault scenario information corresponding to the plan identifier, and the fault handling measures.

In an exemplary embodiment, the apparatus further comprises:

the fault exercise module is further used for performing fault exercise based on fault scene information corresponding to the target plan, fault handling measures, public fault scene information corresponding to the target plan and fault handling measures corresponding to the public fault scene information.

In an exemplary embodiment, the apparatus further comprises: the scene library creation module is used for acquiring a history plan set, wherein each plan in the history plan set comprises fault scene information and fault treatment measures; acquiring preset quantity parameter values, and clustering the history plan set according to the quantity parameter values to acquire a plurality of clusters; for each cluster, a common fault scenario library is created based on fault scenario information and fault handling measures contained in each history plan in the cluster.

In an exemplary embodiment, the apparatus further comprises: the reinspection task creation module is used for determining exercise object attribute information corresponding to the target plan; acquiring a pre-established association relationship between exercise object attribute information and plan reinspection frequency; determining the reinspection frequency corresponding to the target plan based on the exercise object attribute information corresponding to the target plan and the association relation; and creating a re-inspection task corresponding to the target plan according to the re-inspection frequency, wherein the re-inspection task is used for indicating to check and correct fault handling measures of the target plan.

In an exemplary embodiment, the second scene information acquisition module is further configured to: determining a drill frequency of the target plan in response to a drill frequency configuration event for the target plan; according to the exercise frequency, creating a fault exercise task of the target plan; responding to a fault exercise event triggered by aiming at a fault exercise task, and acquiring fault scene information and fault treatment measures corresponding to a target plan from a plan fault scene library according to a plan identifier indicated by the fault exercise task.

In an exemplary embodiment, the plan identifications in the plan fault scene library are respectively associated with the plan types to which the identified plans belong; the second scene information acquisition module is further configured to: determining the plan type of the target plan according to the plan identification of the target plan; screening a plan identification set associated with a plan type from a plan fault scene library, and determining fault scene information and fault treatment measures corresponding to each plan identification; and acquiring fault scene information and fault treatment measures corresponding to the plan identification of the target plan from the fault scene information and fault treatment measures corresponding to the plan identifications respectively.

The various modules in the above-described fault exercise device may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one exemplary embodiment, a computer device is provided, which may be a server, and the internal structure thereof may be as shown in fig. 10. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer equipment is used for storing fault scene information, plan disposal measures and other data. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by the processor to implement a fault exercise method.

In an exemplary embodiment, a computer device, which may be a terminal, is provided, and an internal structure thereof may be as shown in fig. 11. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by the processor to implement a fault exercise method. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by persons skilled in the art that the structures shown in fig. 10 and 11 are merely block diagrams of partial structures related to the present application and do not constitute limitations of the computer device to which the present application is applied, and that a specific computer device may include more or fewer components than shown in the drawings, or may combine some components, or have different arrangements of components.

In an exemplary embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the fault exercise method of any of the embodiments described above when the computer program is executed.

In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, implements the steps of the fault exercise method of any of the embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the fault drill method of any of the embodiments described above.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1. A method of fault exercise, the method comprising:

2. The method according to claim 1, wherein the method further comprises:

3. The method according to claim 2, wherein the method further comprises:

4. The method of claim 2, wherein the common fault scenario library is created by a database creation step comprising:

5. The method according to claim 1, wherein the method further comprises:

6. The method according to any one of claims 1 to 4, wherein, in response to a fault exercise event for the target plan, according to a plan identification of the target plan, obtaining fault scenario information and fault handling measures corresponding to the target plan from the plan fault scenario library, includes:

7. The method of claim 5, wherein the protocol identifications in the protocol failure scenario library are respectively associated with protocol types to which the identified protocols belong;

8. A fault exercise device, the device comprising:

9. The apparatus of claim 8, wherein the apparatus further comprises:

10. The apparatus of claim 9, wherein the apparatus further comprises:

11. The apparatus of claim 9, wherein the apparatus further comprises: the scene library creating module is used for acquiring a history plan set, wherein each plan in the history plan set comprises fault scene information and fault treatment measures; acquiring a preset quantity parameter value, and clustering the history plan set according to the quantity parameter value to acquire a plurality of clustering clusters; for each cluster, a common fault scenario library is created based on fault scenario information and fault handling measures contained in each history plan in the cluster.

12. The apparatus of claim 8, wherein the apparatus further comprises: the reinspection task creation module is used for determining exercise object attribute information corresponding to the target plan; acquiring a pre-established association relationship between exercise object attribute information and plan reinspection frequency; determining the reinspection frequency corresponding to the target plan based on the exercise object attribute information corresponding to the target plan and the association relation; and creating a re-inspection task corresponding to the target plan according to the re-inspection frequency, wherein the re-inspection task is used for indicating to check and correct fault handling measures of the target plan.

13. The apparatus according to any one of claims 8 to 12, wherein the second scene information acquisition module is further configured to: determining an exercise frequency for the target protocol in response to an exercise frequency configuration event for the target protocol; according to the drilling frequency, a fault drilling task of the target plan is established; responding to a fault exercise event triggered by aiming at the fault exercise task, and acquiring fault scene information and fault disposal measures corresponding to the target plan from the plan fault scene library according to the plan identification indicated by the fault exercise task.

14. The apparatus of claim 13, wherein the protocol identifications in the protocol failure scenario library are respectively associated with protocol types to which the identified protocols belong; the second scene information acquisition module is further configured to: determining a plan type of the target plan according to the plan identification of the target plan; screening a plan identification set associated with the plan type from the plan fault scene library, and determining fault scene information and fault treatment measures respectively corresponding to each plan identification; and acquiring fault scene information and fault treatment measures corresponding to the plan identification of the target plan from the fault scene information and fault treatment measures corresponding to the plan identifications respectively.

15. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.

16. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.

17. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.