CN115062966A

CN115062966A - Method, device, equipment and storage medium for determining deployment check items

Info

Publication number: CN115062966A
Application number: CN202210673433.8A
Authority: CN
Inventors: 吕婧; 陈存利
Original assignee: Du Xiaoman Technology Beijing Co Ltd
Current assignee: Du Xiaoman Technology Beijing Co Ltd
Priority date: 2022-06-14
Filing date: 2022-06-14
Publication date: 2022-09-16

Abstract

The application provides a method, a device, equipment and a storage medium for determining a deployment check item. The method comprises the following steps: implanting a corresponding simulated entity fault into any entity in a service system to be deployed; monitoring the index performance of each entity in the business system after the entity has a deployment fault so as to determine the fault association index of the entity; and determining the deployment check item of the entity online according to the fault association index of the entity. According to the method and the device, before the business system to be deployed executes real service deployment operation, the corresponding simulated entity fault is implanted into any entity in the business system, the advance configuration of the deployment inspection item of any entity in the business system is realized, the passive mode of analyzing the fault afterwards is changed into the mode of actively implanting the simulated entity fault in advance, the fault trigger condition of the deployment inspection item is increased, the comprehensiveness and the fineness of the deployment inspection item are ensured, and the interception accuracy when the deployment fault occurs to one entity in the business system is further improved.

Description

Method, device, equipment and storage medium for determining deployment check items

Technical Field

The embodiment of the application relates to the technical field of data processing, in particular to a method, a device, equipment and a storage medium for determining a deployment check item.

Background

With the comprehensive development of business service functions, it is usually necessary to continuously deploy each developed service in a business system, that is, to distribute the service hierarchically to each entity in the business system. In the service deployment process, if a certain entity in the service system fails, the user request cannot be correctly processed according to the expected effect after the service deployment, and further the service operation is interrupted. Therefore, in order to ensure the stable accuracy of service deployment, it is usually necessary to check the deployment inspection items of each entity in the service system in real time to analyze the system operating state, so that the deployment process can be intercepted and fused in time when a deployment fault occurs, thereby reducing the influence of the deployment fault on the user request.

At present, the deployment check items of each entity in the service system are manually listed and enumerated according to the historical fault condition of the system and the existing fault processing experience. Then, after the deployment is completed, the corresponding deployment check item is updated through the deployment failure which has occurred in the copy.

However, because risk factors causing deployment failures widely exist, potential deployment inspection items cannot be effectively identified according to the historical failure condition of the system and the existing failure processing experience, and certain defects exist in the deployment inspection items. Moreover, the manually configured deployment inspection items cannot be refined to lower-layer abstract indexes, so that the refinement degree of the deployment inspection items is low, and the problem that the deployment process is excessively intercepted or overlooked due to mistaken identification of deployment faults exists.

Disclosure of Invention

The application provides a method, a device, equipment and a storage medium for determining a deployment inspection item, which are used for realizing the advanced configuration of the deployment inspection item of any entity in a service system to be deployed, ensuring the comprehensiveness and fineness of the deployment inspection item and improving the interception accuracy when a certain entity in the service system has a deployment fault.

In a first aspect, an embodiment of the present application provides a method for determining a deployed inspection item, where the method includes:

implanting a corresponding simulated entity fault into any entity in a service system to be deployed;

monitoring the index performance of each entity in the business system after the entity has a deployment fault so as to determine the fault association index of the entity;

and determining the deployment check item of the entity online according to the fault association index of the entity.

In a second aspect, an embodiment of the present application provides an apparatus for determining a deployed inspection item, including:

the simulated fault implantation module is used for implanting a corresponding simulated entity fault into any entity in the service system to be deployed;

the index monitoring module is used for monitoring the index performance of each entity in the business system after the entity has a deployment fault so as to determine the fault associated index of the entity;

and the inspection item determining module is used for determining the deployment inspection items of the entity online according to the fault association index of the entity.

In a third aspect, an embodiment of the present application provides an electronic device, including:

a processor and a memory, the memory being configured to store a computer program, the processor being configured to call and run the computer program stored in the memory to perform the method for determining a deployment check item provided in the first aspect of the present application.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program makes a computer execute the method for determining a deployment check item as provided in the first aspect of the present application.

In a fifth aspect, the present application provides a computer program product, which includes a computer program/instruction, and is characterized in that the computer program/instruction, when executed by a processor, implements the method for determining a deployment check item as provided in the first aspect of the present application.

The method, apparatus, device and storage medium for determining a deployment check item provided in the embodiments of the present application, before a business system to be deployed performs a real service deployment operation, first implant a corresponding simulated entity fault into any entity in the business system to monitor an index performance of each entity in the business system after the entity has a deployment fault, so as to determine a fault-related index of the entity from each entity index, and then determining the deployment inspection item on line of the entity according to the fault association index of the entity, thereby realizing the advanced configuration of the deployment inspection item of any entity in the service system before the real deployment, converting a passive mode of analyzing faults afterwards into a mode of actively implanting simulation entity faults in advance, increasing the fault trigger condition of the deployment inspection item, ensuring the comprehensiveness and fineness of the deployment inspection item, and further improving the interception accuracy when a certain entity in the service system has deployment faults.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic diagram illustrating a principle of hierarchical publishing of a service in a business system to be deployed according to an embodiment of the present application;

FIG. 2 is a flow chart illustrating a method for determining a deployment check item according to an embodiment of the present application;

FIG. 3 is a flowchart illustrating another method for determining a deployment check item according to an embodiment of the present application;

FIG. 4 is a flowchart of a method for implanting a corresponding simulated entity fault procedure into any entity according to an embodiment of the present disclosure;

FIG. 5 is a schematic block diagram illustrating an apparatus for determining a deployed inspection item according to an embodiment of the present application;

fig. 6 is a schematic block diagram of an electronic device shown in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Before introducing the technical solution of the present application, a complete deployment process for hierarchically publishing a certain service in a business system to be deployed is described below:

fig. 1 is a schematic diagram illustrating a principle of hierarchical publishing of a service in a business system to be deployed according to an embodiment of the present application.

Specifically, the deployment platform has a corresponding deployment release authority for the service system to be deployed, and after being checked by a necessary deployment process, the deployment platform supports an operator to initiate a deployment operation signal of a certain service to the service system in the deployment platform, so that the service system starts to run a deployment program of the service.

The services To be deployed in the present application are mainly services facing external users, mainly end user (To Customer, abbreviated as ToC) facing types, and are generally deployed in a computer hardware medium.

Then, the deployment platform pushes the current service deployment event to the event dashboard so as to record and store the event details of the service deployment event. And the deployment platform notifies, audits, records and the like the whole process node of the service deployment event.

Meanwhile, after receiving a deployment operation signal of a certain service initiated by the deployment platform, the service system reads a preset hierarchical release template. Then, according to the levels of the small flow entity- > single room entity- > full volume entity in the hierarchical publishing template, gradually publishing and diffusing the baseline version of the service in the production system at each level, thereby realizing the hierarchical publishing of the service in the business system. Where each level may be treated as a deployment phase.

After the release of one deployment phase is completed, the next deployment phase is not immediately entered for release. Instead, an automatic check request is initiated to the fault detection platform, and the fault detection platform monitors the operation state of the service system in the deployment stage through the monitoring indexes of the monitoring system. That is, the deployed check items configured by each entity in the deployment phase are called by the fault detection platform to perform item-by-item check to determine whether a deployment fault exists in a certain entity in the deployment phase. And further, the fault detection platform asynchronously returns the item-by-item inspection results of the deployment inspection items to the service system.

The deployment check item in the application is denoted as Checklist, and may include actual data items of monitoring indexes of each entity, normal and abnormal ranges of the data items, and or and nor logic judgment policies after a plurality of data items are combined, and the like.

Furthermore, after receiving the inspection result of the deployment inspection item of each entity in any deployment stage, the service system can judge whether an entity deployment fault exists in the deployment stage by lighting. If the detection result in the deployment phase is abnormal, which indicates that entity deployment failure exists in the deployment phase, the current deployment process of the business system is fused and intercepted. However, if the inspection result in the deployment phase is normal, which indicates that there is no entity deployment fault in the deployment phase, the deployment operation execution of the next deployment phase is automatically performed until the service deployment on the entire entities in all the deployment phases is completed.

For an exception handling branch when a deployment fault exists in any deployment phase: receiving a light-up alarm sent by a service system through a loss stopping decision unit, and then starting to execute the following loss stopping intervention process:

and firstly, performing fusing interception on the deployment process of the business system in the deployment phase.

And step two, automatically executing a corresponding loss stopping plan for the deployment faults which conform to the known faults, namely the deployment faults with the plan processing flow.

And thirdly, directly contacting the personnel on duty for unknown deployment faults or unsuccessfully loss-stopped deployment faults, and performing manual intervention.

And fourthly, notifying key time points of the whole service deployment event, such as the deployment starting time, the fault monitoring time and the like, in a text message mode.

In summary, when a deployment fault exists in an entity in a service system, the accuracy of performing fusing interception on a deployment process is mainly related to the following: when the deployment inspection items of each entity are inspected item by item, whether the deployment fault can be accurately judged. Therefore, in order to ensure excessive interception or missed interception when deployment faults occur in the deployment process, certain requirements exist for the comprehensiveness and the fineness of the deployment check items of each entity.

Considering that the deployment inspection items of each entity in the current business system are usually manually listed and enumerated according to the historical failure condition of the system and the existing failure processing experience, and are correspondingly updated by replying the deployment failures which have occurred. Therefore, the existing deployment inspection items are determined in a passive mode of analyzing faults afterwards, so that the deployment inspection items have the problems of certain loss and low refinement degree.

In order to solve the above problems, the present application designs a new deployment check item determination scheme, before the business system to be deployed performs the actual service deployment operation, by implanting corresponding simulated entity faults into any entity in the service system in advance, the index performance of each entity in the service system after the entity has a deployment fault is monitored, and further determine the fault correlation index of the entity from the indexes of each entity so as to actively determine the deployment check item on line of the entity before the actual service deployment operation, therefore, the deployment inspection item of any entity in the service system is configured in advance before real deployment, a passive mode of analyzing faults afterwards is changed into a mode of actively implanting simulated entity faults in advance, fault triggering conditions of the deployment inspection item are increased, comprehensiveness and fineness of the deployment inspection item are ensured, and interception accuracy of a certain entity in the service system when the deployment fault occurs is improved.

The following will explain in detail a specific technical solution for determining the deployment check items of each entity in the service system to be deployed in the present application:

fig. 2 is a flowchart illustrating a determination method for deploying an inspection item according to an embodiment of the present application. Referring to fig. 2, the method may specifically include the following steps:

s210, implanting a corresponding simulation entity fault into any entity in the service system to be deployed.

It is considered that the business system is composed of a plurality of entities representing system function objects and relationships between the entities, and the specific functions performed by different entities in the business system are different. Then different entities will have different types of failures for the system functions that are provided.

In the application, in order to avoid the problem that deployment check items are incomplete and not fine when the deployment check items of each entity are updated through a failure recovery disk after a failure occurs, each type of deployment failure that may exist in a deployment process of each entity in a business system is analyzed in advance. Then, in order to comprehensively evaluate the deployment fault condition that may occur in each entity in the service deployment process, the present application simulates the deployment fault of the corresponding type for each entity, so as to obtain the simulated entity fault of any entity in the present application.

According to one or more embodiments of the present application, before performing a real service deployment operation on each entity in a business system, a preset fault of each corresponding simulated entity is implanted into any entity in the business system, so as to perform simulation analysis on various deployment faults that may occur to the entity in advance, that is, a deployment check item of the entity can be determined in advance.

By covering all entities in the service system, and continuously and repeatedly implanting corresponding simulated entity faults into each entity, the deployment check items of each entity can be determined in advance before the real service deployment operation is executed.

Moreover, since a simulated entity failure that is proactively implanted into any entity can involve deployment failure scenarios of various types that may occur with that entity. Therefore, various deployment faults which may occur to the entity can be comprehensively simulated and analyzed in advance, so that the comprehensiveness of the deployment inspection items of the various entities is ensured by increasing the fault triggering conditions of the deployment inspection items.

It should be understood that, in order to ensure that the service system is still available after the fault simulation, a fault of a corresponding simulation entity is implanted into any entity on the premise that the service system stops damage deployment and is controllable.

IT should be noted that, considering that each entity in the business system is mainly an abstract representation of each functional component in the system, any business system usually employs a Configuration Management DataBase (CMDB) to manage all relevant information of information system components used by various Internet Technology (IT) services under the business system and relationships between these components. Therefore, the method and the system can determine the full-amount entity list in the business system by utilizing the configuration management database of the business system.

That is, a business system typically employs a configuration management database to manage the information about the various entities therein and the relationships between the entities. Then, all entities in the service system can be determined by searching the associated entity information in the configuration management database, so as to obtain the total entity list in the application. Then, aiming at each entity in the full entity list, by implanting the corresponding simulated entity fault into the entity, the simulation analysis can be performed on various deployment faults which may occur to the entity in advance.

S220, monitoring the index performance of each entity in the business system after the entity has a deployment fault so as to determine the fault correlation index of the entity.

In order to accurately observe the actual operation details of the business system, corresponding monitoring indexes are usually set for each entity in the business system, and the monitoring indexes may be operation data items of each entity under a specific type in the system operation process. At the moment, the real operation state of each entity can be judged by analyzing the overall change condition of each monitoring index under each entity in the operation process.

Furthermore, considering that the operation condition of other entities may be affected when a certain entity fails, the present application simulates that a certain deployment failure occurs in any entity in the business system after a corresponding simulation entity failure is implanted into the entity. Therefore, in the operation process of the service system, after the deployment fault occurs to the entity, the overall change condition of each monitoring index under each entity in the service system is monitored in real time, so that the index performance of each entity after the deployment fault occurs to the entity is obtained.

In the application, the index performance of each entity after the deployment fault occurs to the entity can indicate the specific operation deviation condition of each monitoring index after the deployment fault occurs to the entity and under the normal condition. Moreover, considering that the degree of influence of the entity on different monitoring indexes under each entity after the deployment fault occurs is different, the degree of deviation, which is expressed by the index performance of the different monitoring indexes and is in the normal condition, from the specific operation deviation under the normal condition is also different. Therefore, by analyzing the index performance of different monitoring indexes of each entity, the degree of influence of the entity on different monitoring indexes after a deployment fault occurs can be judged, and each monitoring index with high association degree with the entity is further determined to serve as a fault association index in the application.

The same steps are carried out on each entity in the service system, so that the fault association index of each entity in the service system can be determined.

And S230, determining a deployment check item on the entity according to the fault association index of the entity.

For the fault associated index of each entity in the business system, each fault associated index of the entity can be directly used as an index item to be checked when the entity deploys real services. That is, each fault association indicator for the entity may be configured directly as a deployment check entry when the entity comes online.

On the other hand, according to the association strength between each fault association index of each entity and the entity, the method and the device can screen out part of fault association indexes with higher association strength as index items to be checked when the entity deploys real services, so that the part of fault association indexes screened out by the entity is configured as deployment check items when the entity is online.

According to the technical scheme provided by the embodiment of the application, before the business system to be deployed executes real service deployment operation, a corresponding simulated entity fault is implanted into any entity in the business system to monitor the index performance of each entity in the business system after the entity has the deployment fault so as to determine the fault associated index of the entity from each entity index, and then determining the deployment inspection item on line of the entity according to the fault association index of the entity, thereby realizing the advanced configuration of the deployment inspection item of any entity in the service system before the real deployment, converting a passive mode of analyzing faults afterwards into a mode of actively implanting simulation entity faults in advance, increasing the fault trigger condition of the deployment inspection item, ensuring the comprehensiveness and fineness of the deployment inspection item, and further improving the interception accuracy when a certain entity in the service system has deployment faults.

As an optional implementation scheme in the present application, in order to ensure accuracy of a fault association index of any entity in a service system to be deployed, the present application analyzes a fault association coefficient between each index of the entity and each index of other entities through an index performance of each entity after a deployment fault occurs in any entity, so as to represent a degree of association between each index of the entity and each index of other entities when a deployment fault occurs in the entity. As shown in fig. 3, the present application explains in detail a specific process of determining a fault-related indicator of each entity in a business system through an indicator performance of the entity after a deployment fault occurs.

Fig. 3 is a flowchart of another method for determining a deployment inspection item according to an embodiment of the present application. Referring to fig. 3, the method may specifically include the following steps:

s310, implanting corresponding simulation entity faults into any entity in the service system to be deployed.

And S320, monitoring the index performance of each entity in the service system after the entity has deployment failure.

In order to comprehensively analyze the influence on the normal operation of other entities when a certain entity has a deployment fault, the method and the system can implant a corresponding simulation entity fault into any entity in the operation process of the service system, so that the overall change condition of each monitoring index under each entity in the service system is monitored in real time after the entity has the deployment fault. And then, according to the overall change condition of each monitoring index under each entity in the system operation process, the index performance of each entity after the entity has a deployment fault can be obtained.

S330, calculating a fault association coefficient between the entity and each index according to the index performance.

As an optional implementation manner in the present application, the index performance of each index under each entity may be represented by an index change curve in the whole operation process.

Moreover, in order to accurately analyze the correlation between any entity and each index after a deployment fault occurs, a correlation analysis model is constructed in advance by using Statistical analysis software under a Statistical Product and Service Solutions (SPSS). The SPSS is a software product and related services for statistical analysis operations, data mining, predictive analysis, and decision support tasks.

Then, the index performance of each entity after any entity has a deployment fault is respectively input into the constructed correlation analysis model, so that the correlation analysis is performed on the index change condition of each index after the entity has the deployment fault, and then the correlation coefficient between the entity and each index, namely the fault correlation coefficient in the application is output.

It should be noted that, in order to uniformly represent the degree of association between the entity and each index after the deployment failure occurs, the present application may convert the failure association coefficient between the entity and each index into a uniform pearson correlation coefficient or a uniform spearman correlation level for representation.

In addition, the indexes can be sorted according to the degree of association represented by the fault association coefficient between the entity and each index. Furthermore, by performing regression analysis on the fault correlation coefficient between the entity and each index, accurate verification and fine adjustment of the correlation degree of the fault correlation coefficient between the entity and each index can be performed, so that the adjusted fault correlation coefficient is obtained.

S340, determining the fault association index of the entity according to the fault association coefficient.

For the change acceptance degree of the normal operation of the service system to the index performance of each entity after the deployment fault of the entity occurs, a correlation coefficient boundary value under the acceptable change can be set. Then, for each index sorted according to the height of the fault correlation coefficient, a part of indexes with the fault correlation coefficient larger than the boundary value of the correlation coefficient can be quickly found out. At this time, the correlation degree between the searched part of indexes and the entity after the deployment fault occurs is higher, so the searched part of indexes is determined as the fault correlation index of the entity.

S350, determining the deployment check item of the entity online according to the fault correlation index of the entity.

According to the technical scheme provided by the embodiment of the application, the fault correlation index of each entity in the service system is determined by analyzing the fault correlation of the index performance of each entity after any entity has a deployment fault, and then the deployment inspection item on line of the entity is determined according to the fault correlation index of the entity, so that the comprehensiveness and the fineness of the deployment inspection item are ensured, and the interception accuracy of one entity in the service system when the deployment fault occurs is further improved.

As an optional implementation scheme in the present application, when deployment faults of different types occur in any entity, the influence degrees on each monitoring index under other entities in the service system are different. Therefore, the fault association index of the entity can be comprehensively analyzed by covering all entities in the business system and implanting different types of simulated entity faults into each entity for multiple times. The specific process of implanting a corresponding simulated entity fault to any entity within the business system is explained in detail below with reference to fig. 4.

Fig. 4 is a flowchart illustrating a method for implanting a corresponding simulated entity failure process into any entity according to an embodiment of the present application. Referring to fig. 4, the method may specifically include the following steps:

s410, taking the first entity in the business system as the current entity, and implanting corresponding simulation entity faults into the current entity for multiple times to obtain the deployment check items of the current entity.

For the deployment fault types possibly existing in each entity in the service system, a plurality of different types of simulation entity faults can be preset for each entity. Moreover, to ensure the advanced configuration of deployment checkitems for each entity within the business system, all entities within the business system need to be covered to implant each entity with the corresponding simulated entity failures.

According to one or more embodiments of the present application, the entities may be ordered according to an operation order of the entities in the service system. Then, the first entity in the business system is taken as the current entity.

Furthermore, in order to comprehensively analyze the influence of the current entity on other entities under different deployment faults, corresponding simulated entity faults can be implanted into the current entity for multiple times, and the simulated entity faults implanted each time can be of different types. Then, after implanting a corresponding simulated entity fault into the current entity each time, the deployment check item determined by the entity after this implantation is obtained. Therefore, the deployment check items on the current entity are continuously updated by implanting the corresponding simulation entity faults into the current entity for multiple times.

As an optional implementation scheme in the present application, determining a deployment check item on a line of the entity according to the fault association index of the entity in the present application may specifically be: and combining the fault correlation indexes determined after the fault of the corresponding simulation entity is implanted into any entity every time to obtain the deployment inspection item on the entity.

That is, after a corresponding simulation entity fault is implanted into any entity each time, a fault-related index of the entity is determined according to the index performance of each entity after the simulation entity fault is implanted this time. Furthermore, the deployment check items on the entity can be continuously updated by combining the fault correlation indexes determined after the fault of the corresponding simulation entity is implanted into any entity every time.

And S420, after the deployment check items on the line of the current entity are not changed, taking the next entity of the current entity as a new current entity, and continuously implanting corresponding simulated entity faults into the new current entity for multiple times until the deployment check items on the line of each entity in the service system reach a preset deployment optimization target, so as to obtain the deployment check items on the line of each entity in the service system.

Specifically, implanting the corresponding simulation entity fault into the current entity for multiple times can continuously update the deployment check item on line of the current entity until the deployment check item on line of the current entity is not changed any more, which indicates that the deployment check item on line of the current entity tends to be stable and is relatively comprehensive, and the deployment check item does not need to be implanted to update the deployment check item. Therefore, the next entity of the current entity can be used as a new current entity, the corresponding simulated entity faults are continuously implanted into the new current entity for multiple times, so that the deployment check items on the new current entity are continuously updated, and the corresponding simulated entity faults can be implanted into all the entities in the service system for multiple times in sequence by the circulation, so that the comprehensiveness and the refinement of the deployment check items on all the entities in the service system are ensured.

Moreover, for the cyclic optimization of the deployment check items on the line of each entity in the service system, a deployment optimization target may be preset, for example, the preset deployment optimization target may be that the update frequency of the deployment check items of each entity in the service system has been reduced to below 20%. Then, after the deployment check items on line of each entity in the service system reach the preset deployment optimization target, the advanced configuration process of the deployment check items of each entity in the service system can be directly quitted, so that the deployment check items on line of each entity in the service system are obtained.

According to the technical scheme provided by the embodiment of the application, all entities in the service system are covered, and corresponding simulated entity faults are implanted into any entity for multiple times, so that the advanced configuration of the deployment inspection item of any entity in the service system before real deployment is ensured, and the comprehensiveness and the fineness of the deployment inspection item are further improved.

Fig. 5 is a schematic block diagram illustrating an apparatus for determining a deployment check item according to an embodiment of the present application. As shown in fig. 5, the apparatus 500 may include:

a simulated fault implantation module 510, configured to implant a corresponding simulated entity fault into any entity in the service system to be deployed;

an index monitoring module 520, configured to monitor an index performance of each entity in the service system after the entity has a deployment fault, so as to determine a fault-related index of the entity;

the inspection item determining module 530 is configured to determine a deployment inspection item on the line of the entity according to the fault association indicator of the entity.

According to one or more embodiments of the present disclosure, the index monitoring module 520 may be specifically configured to:

monitoring the index performance of each entity in the service system after the entity has a deployment fault;

calculating a fault association coefficient between the entity and each index according to the index performance;

and determining the fault association index of the entity according to the fault association coefficient.

According to one or more embodiments of the present application, the apparatus 500 for determining a deployment check item may further include:

and the correlation coefficient regression module is used for carrying out regression analysis on the fault correlation coefficient between the entity and each index to obtain the adjusted fault correlation coefficient.

According to one or more embodiments of the present application, the simulated fault implantation module 510 may be specifically configured to:

taking a first entity in the service system as a current entity, and implanting corresponding simulation entity faults into the current entity for multiple times to obtain a deployment check item on the current entity;

and after the online deployment check item of the current entity is not changed any more, taking the next entity of the current entity as a new current entity, and continuously implanting corresponding simulation entity faults into the new current entity for multiple times until the online deployment check item of each entity in the service system reaches a preset deployment optimization target, thereby obtaining the online deployment check item of each entity in the service system.

According to one or more embodiments of the present application, the check item determining module 530 may be specifically configured to:

and combining the fault correlation indexes determined after the fault of the corresponding simulation entity is implanted into any entity every time to obtain the deployment inspection item on the entity.

and the entity list determining module is used for determining a full entity list in the service system by utilizing the configuration management database of the service system.

In the embodiment of the application, before the business system to be deployed executes the real service deployment operation, a corresponding simulated entity fault is implanted into any entity in the business system to monitor the index performance of each entity in the business system after the deployment fault occurs in the entity, so as to determine the fault associated index of the entity from each entity index, and then determining the deployment inspection item on line of the entity according to the fault association index of the entity, thereby realizing the advanced configuration of the deployment inspection item of any entity in the service system before the real deployment, converting a passive mode of analyzing faults afterwards into a mode of actively implanting simulation entity faults in advance, increasing the fault trigger condition of the deployment inspection item, ensuring the comprehensiveness and fineness of the deployment inspection item, and further improving the interception accuracy when a certain entity in the service system has deployment faults.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. To avoid repetition, further description is omitted here. Specifically, the apparatus 500 shown in fig. 5 may perform the method embodiment provided in the present application, and the foregoing and other operations and/or functions of each module in the apparatus 500 are respectively for implementing corresponding processes in each method of the embodiment of the present application, and are not described herein again for brevity.

The apparatus 500 of the present application is described above in connection with the drawings from the perspective of functional blocks. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps in the above method embodiments in combination with hardware thereof.

Fig. 6 is a schematic block diagram of an electronic device 600 shown in an embodiment of the present application.

As shown in fig. 6, the electronic device 600 may include:

a memory 610 and a processor 620, the memory 610 being configured to store a computer program and to transfer the program code to the processor 620. In other words, the processor 620 may call and execute a computer program from the memory 610 to implement the method in the embodiment of the present application.

For example, the processor 620 may be configured to perform the above-described method embodiments according to instructions in the computer program.

In some embodiments of the present application, the processor 620 may include, but is not limited to:

general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

In some embodiments of the present application, the memory 610 includes, but is not limited to:

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

In some embodiments of the present application, the computer program may be partitioned into one or more modules, which are stored in the memory 610 and executed by the processor 620 to perform the methods provided herein. The one or more modules may be a series of computer program instruction segments capable of performing certain functions, the instruction segments being used to describe the execution of the computer program in the electronic device.

As shown in fig. 6, the electronic device may further include:

a transceiver 630, the transceiver 630 may be connected to the processor 620 or the memory 610.

The processor 620 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

It should be understood that the various components in the electronic device are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

Embodiments of the present application also provide a computer storage medium having a computer program stored thereon, where the computer program, when executed by a computer, enables the computer to execute the method of the above method embodiments. In other words, the present application also provides a computer program product containing instructions, which when executed by a computer, cause the computer to execute the method of the above method embodiments.

When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application occur, in whole or in part, when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disc (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the module is merely a logical division, and other divisions may be realized in practice, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.

Modules described as separate parts may or may not be physically separate, and parts shown as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. For example, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of determining a deployment check item, comprising:

implanting a corresponding simulation entity fault into any entity in a service system to be deployed;

2. The method of claim 1, wherein the monitoring performance of indicators of each entity in the business system after a deployment failure of the entity to determine a failure-associated indicator of the entity comprises:

3. The method of claim 2, further comprising, after calculating a fault correlation coefficient between the entity and each metric based on the metric performance:

and carrying out regression analysis on the fault correlation coefficient between the entity and each index to obtain the adjusted fault correlation coefficient.

4. The method according to claim 1, wherein the implanting a corresponding simulated entity fault to any entity in the service system to be deployed comprises:

and after the deployment check items on the line of the current entity are not changed any more, taking the next entity of the current entity as a new current entity, and continuously implanting corresponding simulated entity faults into the new current entity for multiple times until the deployment check items on the line of each entity in the service system reach a preset deployment optimization target, so as to obtain the deployment check items on the line of each entity in the service system.

5. The method of claim 4, wherein determining a deployment check item for a presence on the entity according to the fault association indicator of the entity comprises:

6. The method of claim 1, further comprising:

and determining a full entity list in the service system by using a configuration management database of the service system.

7. A determining apparatus for deploying an inspection item, comprising:

and the inspection item determining module is used for determining the online deployment inspection item of the entity according to the fault association index of the entity.

8. An electronic device, comprising:

a processor and a memory, the memory for storing a computer program, the processor for calling and executing the computer program stored in the memory to perform the method of determining a deployment check item of any of claims 1-6.

9. A computer-readable storage medium for storing a computer program for causing a computer to execute the determination method of deploying check item according to any one of claims 1 to 6.

10. A computer program product comprising a computer program/instructions, characterized in that the computer program/instructions, when executed by a processor, implement the method of determining a deployment check item as defined in any of claims 1-6.