Method, device and system for generating fault drilling report and electronic equipment

Abstract

The embodiment of the invention discloses a fault drill report generation method, device and system and electronic equipment, and is used for automatically and quickly generating fault drill reports in batches, so that the report generation time is shortened, the labor cost is reduced, and the accuracy of the fault drill reports is improved. The method comprises the steps that report configuration information of fault drilling tasks in a current task set is acquired, the current task set comprises the fault drilling tasks currently injected into a service system, and the report configuration information comprises report time information and task identification; based on the report time information, selecting a target fault drilling task meeting a preset report generation condition from the current task set; based on the task identifier of the target fault drilling task, obtaining a task execution record of the target fault drilling task and packaging the task execution record into a report entity object; and generating a drilling report of the target fault drilling task based on the report entity object.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular to a method, device, system and electronic device for generating a fault drill report. Background Art

[0002] As businesses continue to grow and their systems become increasingly complex, maintaining business continuity remains a top priority. In this context, proactively discovering weaknesses in business systems through external fault injection is becoming increasingly essential.

[0003] Currently, the performance of business systems in fault drills is primarily assessed manually. This means that after each fault drill is completed, a manual report must be generated. This approach is not only time-consuming and labor-intensive, but also relies heavily on human experience, making the report inaccurate. Summary of the Invention

[0004] The purpose of the embodiments of this specification is to provide a method, device, system and electronic device for generating fault drill reports, which are used to automatically and quickly generate fault drill reports in batches, thereby shortening report generation time, reducing labor costs, and improving the accuracy of fault drill reports.

[0005] In order to achieve the above objectives, the embodiments of this specification adopt the following technical solutions:

[0006] In a first aspect, a method for generating a fault drill report is provided, comprising:

[0007] Acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier;

[0008] Based on the report time information, selecting a target fault drill task that meets a preset report generation condition from the current task set;

[0009] Based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object;

[0010] A drill report for the target fault drill task is generated based on the report entity object.

[0011] In a second aspect, a system for generating a fault drill report is provided, comprising: a producer, a consumer, and a local cache queue;

[0012] The producer is configured to obtain report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill tasks currently injected into the business system, and the report configuration information includes report time information and a task identifier;

[0013] The producer is further configured to select, from the current task set, a target fault drill task that meets a preset report generation condition based on the report time information, and, based on the task identifier of the target fault drill task, obtain the task execution record of the target fault drill task, encapsulate the record into a report entity object, and then send the result to the local cache queue;

[0014] The consumer is used to consume the local cache queue and generate a drill report for the target fault drill task based on the acquired entity report object.

[0015] In a third aspect, a device for generating a fault drill report is provided, comprising:

[0016] A first acquiring unit is configured to acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier;

[0017] A second acquiring unit is configured to select, based on the report time information, a target fault drill task that meets a preset report generation condition from the current task set;

[0018] A third acquiring unit is configured to acquire, based on the task identifier of the target fault drill task, the task execution record of the target fault drill task and encapsulate the record into a report entity object;

[0019] A generating unit is configured to generate a drill report for the target fault drill task based on the report entity object.

[0020] In a fourth aspect, an electronic device is provided, including:

[0021] processor; and

[0022] a memory arranged to store computer-executable instructions which, when executed, cause the processor to:

[0023] Acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier;

[0024] Based on the report time information, selecting a target fault drill task that meets a preset report generation condition from the current task set;

[0025] Based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object;

[0026] A drill report for the target fault drill task is generated based on the report entity object.

[0027] According to a fifth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores one or more programs. When the one or more programs are executed by an electronic device including a plurality of application programs, the electronic device performs the following operations:

[0028] Acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier;

[0029] Based on the report time information, selecting a target fault drill task that meets a preset report generation condition from the current task set;

[0030] Based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object;

[0031] A drill report for the target fault drill task is generated based on the report entity object.

[0032] The solution of the embodiment of this specification configures the corresponding report time information and task identifier in the report configuration information of each fault drill task; based on the report event information, the target fault drill tasks that meet the requirements are screened out from the fault drill tasks currently injected into the business system, and the task execution record of the target fault drill task is obtained based on the task identifier; because the task execution record reflects the execution status of the target fault drill task, the task execution record is encapsulated as a report entity object for generating a report, and then based on the report entity object, a drill report for the target fault drill task is automatically generated. It can be seen that the generation process of the fault drill report does not require human intervention, has the advantages of saving time and labor, improving report accuracy, and is suitable for batch generation of fault drill reports. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The drawings described herein are used to provide a further understanding of this specification and constitute a part of this specification. The exemplary embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation of this specification. In the drawings:

[0034] Figure 1A flowchart of a method for generating a fault drill report provided in one embodiment of this specification;

[0035] Figure 2 A flowchart of a method for generating a fault drill report provided in another embodiment of this specification;

[0036] Figure 3 A structural block diagram of a system for generating a fault drill report provided in one embodiment of this specification;

[0037] Figure 4 A schematic diagram of a process for generating a fault drill report by a fault drill report generation system provided in one embodiment of this specification;

[0038] Figure 5 A structural block diagram of a device for generating a fault drill report provided in one embodiment of this specification;

[0039] Figure 6 The present invention provides a schematic structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0040] To make the purpose, technical solutions, and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in conjunction with the specific embodiments of this specification and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this document.

[0041] The terms "first," "second," and the like in this specification and claims are used to distinguish similar objects and are not intended to describe a particular order or precedence. It should be understood that such terms are interchangeable, where appropriate, so that the embodiments of this specification may be practiced in an order other than that illustrated or described herein. Furthermore, the term "and / or" in this specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the connected objects are in an "or" relationship.

[0042] In order to solve the problem that the manual method of generating fault drill reports is time-consuming and labor-intensive and cannot guarantee the accuracy of the reports, the embodiment of this specification proposes a method for generating fault drill reports, which configures the corresponding report time information and task identifier in the report configuration information of each fault drill task; based on the report event information, the target fault drill tasks that meet the requirements are screened out from the fault drill tasks currently injected into the business system, and the task execution record of the target fault drill task is obtained based on the task identifier; since the task execution record reflects the execution status of the target fault drill task, the task execution record is encapsulated as a report entity object for generating the report, and then based on the report entity object, the drill report of the target fault drill task is automatically generated. It can be seen that the generation process of the fault drill report does not require manual intervention, has the advantages of saving time and labor, improving the accuracy of the report, and is suitable for batch generation of fault drill reports.

[0043] It should be understood that the method for generating a fault drill report provided in the embodiments of this specification can be executed by an electronic device or by software installed in the electronic device, specifically by a terminal device or a server device.

[0044] The technical solutions provided by the embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0045] Please refer to Figure 1 , is a flowchart of a method for generating a fault drill report provided in one embodiment of this specification. The method may include:

[0046] S102: Obtain report configuration information of the fault drill task in the current task set.

[0047] The task collection includes fault drill tasks currently injected into the business system. These tasks contain information about potential faults that may occur during business operations, such as the fault name, fault type, and the faulty component in the business system. By injecting fault drill tasks into the business system and having the system execute them, the system's operational state can be simulated, effectively performing a fault drill for the business system.

[0048] In practice, the fault drill tasks injected into the business system are constantly updated. To this end, a scheduled task can be used to periodically retrieve the fault drill tasks currently injected into the business system to obtain the current task set. As an example, a scheduled task can poll the fault drill tasks injected into the business system every 10 minutes.

[0049] Each fault drill task has corresponding report configuration information. The report configuration information is used to configure the task of automatically generating a drill report, and the specific information it contains can be set according to actual needs, and the embodiments of this specification do not limit this. As an example, the report configuration information includes the report time information and task identifier of the fault drill task to which it belongs. Among them, the report time information is used to represent the time-related parameters for generating a drill report, which may, for example, include but is not limited to the report generation time, etc.; the task identifier is used to uniquely identify the fault drill task to which the report configuration information belongs. As another example, the report configuration information may also include other more information, such as at least one of the report name, report status, report execution identifier, fault drill conclusion, creator, report type, business systems involved, and drill goal overview.

[0050] S104: Based on the report time information, a target fault drill task that meets a preset report generation condition is selected from the current task set.

[0051] The preset report generation conditions are used to indicate the conditions for generating a drill report, and can be set according to actual needs, and the embodiments of this specification do not limit this.

[0052] In one embodiment, to ensure timely generation of corresponding drill reports for recently injected and completed fault drill tasks, the preset report generation conditions include: the report generation time is close to the current time, and the interval between the task end time and the current time is a certain length. In this case, the above S104 includes the following steps: selecting fault drill tasks from the current task set whose interval between the report generation time and the current time is less than or equal to a first preset length, to obtain a task subset; based on the task identifiers of the fault drill tasks in the task subset, obtaining the task end time of the fault drill tasks in the task subset; and selecting from the task subset fault drill tasks whose interval between the task end time and the current time is greater than a second preset length as the target fault drill tasks that meet the preset report generation conditions.

[0053] For example, the first preset duration is two days, and the second preset duration is 10 minutes. If the current task set includes fault drill task 1, fault drill task 2, and fault drill task 3, and the report generation times for the three are 19:00 on December 12, 19:00 on December 14, and 19:00 on December 15, respectively, and the current time is 19:00 on December 15, then the task subset determined from the current task set includes: fault drill task 2 and fault drill task 3; further, based on the task identifiers of each fault drill task in the task subset, the task end time of fault drill task 2 is obtained as 18:40 on December 14, and the task end time of fault drill task 3 is obtained as 18:56 on December 15, then fault drill task 3 is selected as the target fault drill task.

[0054] The examples of this specification illustrate one implementation of S104. Of course, it should be understood that S104 can also be implemented in other ways. For example, a task subset is obtained by selecting from the current task set the interval between the report generation time and the current time that is less than or equal to a first preset time; then, a fault drill task with a task status of completed and a report status of ungenerated is selected from the task subset as the target fault drill task that meets the preset report generation conditions.

[0055] S106 , based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object.

[0056] In the embodiments of this specification, each fault drill task has a corresponding task execution record. The task execution record and task identifier can be associated and recorded in the fault drill log of the business system. Thus, by parsing and querying the fault drill log based on the task identifier of the target fault drill task, the task execution record of the target fault drill task can be obtained.

[0057] The task execution record includes n items of task-related information associated with the fault drill task, where n is a positive integer. To ensure that the generated drill report more comprehensively and objectively reflects the problems encountered during the execution of the target fault drill task, the n items of task-related information include, but are not limited to, basic report information, basic task information, drill scenario information, network performance indicators of the business system, alarm information, and business operation information of the data center where the business system resides.

[0058] Among them, the basic report information is used to describe the basic situation of the drill report, including but not limited to at least one of the following information: report name, report status, report execution identifier, fault drill conclusion, creator, report type, business systems involved, and drill goal overview. The basic task information is used to describe the basic situation of the fault drill task, including but not limited to the task name and status of the fault drill task, task start time, task end time, drill scenario name, drill scenario identifier, alarm team, report generation team, fault drill team, etc. The drill scenario information is used to describe the business scenario simulated by the fault drill task, including but not limited to the drill scenario name, drill scenario source, network address, machine description, fault instruction, instruction parameters, task start time, task end time, fault identification result, fault prevention result, etc. The network performance indicator information is used to describe the network performance of the business system, including but not limited to the indicator name, network address, indicator value before injection, indicator value during injection, indicator value after injection, fault duration, indicator source, and other service level agreement (SLA) information. Alarm information describes alarm conditions generated by the business system during the fault drill. This information may include, but is not limited to, the Internet Data Center (IDC) issuing the alarm, the application name, the data center's network address, the application identifier, the error code, the alarm content, and the time the alarm content was collected. Data center service operation information describes the data center's service operation status. This information may include, but is not limited to, the service success rate.

[0059] In one embodiment, the above-mentioned n task-related information can be obtained in the following manner: based on the task identifier, obtain the report basic information and task basic information from the fault drill log of the business system; obtain the drill scenario identifier of the target fault drill task from the task basic information, and based on the drill scenario identifier, obtain the drill scenario information from the fault drill log; obtain the network address of the business system from the drill scenario information, and based on the network address, query the network performance indicator information during the execution of the target fault drill task from the fault drill log; obtain the task start time and task end time of the target fault drill task from the drill scenario information, and based on the task start time and task end time, query the alarm information during the execution of the target fault drill task from the fault drill log, and obtain the business operation information of the data center during the execution of the target fault drill task from the data center.

[0060] Through this implementation, by combining the external feedback of the business system and the fault drill tasks of the business system itself for query, the relevant information of the above n tasks can be obtained quickly and accurately to avoid omissions.

[0061] In the embodiments of this specification, a report entity object refers to an entity object used to generate a corresponding drill report. Encapsulating the aforementioned task execution records as entity objects facilitates rapid generation of drill reports. In practical applications, various methods can be used to encapsulate task execution records as entity objects, and the specific method chosen is not limited in this embodiment.

[0062] In order to ensure that the generated report entity object can include the above-mentioned task execution records and improve the encapsulation efficiency, in one embodiment, the above-mentioned task execution records are encapsulated into a report entity object in the following manner: n task-related information are encapsulated separately to obtain n sub-entity objects, and the n sub-entity objects correspond one-to-one to the n task-related information, wherein each sub-entity object refers to an entity object used to generate a drill report and to describe the corresponding task-related information; the n sub-entity objects are combined to obtain a report entity object for generating a drill report, and a report identifier is added to the report entity object, and the report identifier is used to indicate that the report entity object belongs to the target fault drill task.

[0063] In practical applications, an electronic device can employ n functional modules, each corresponding to n task-related information. Each functional module is used to encapsulate the corresponding task-related information. In this case, the n functional modules can run in parallel, thereby enabling the parallel encapsulation of the information related to the n tasks, which helps improve encapsulation efficiency.

[0064] In another embodiment, in order to ensure that a drill report can be accurately generated based on the reporting entity object, before combining the n sub-entity objects, the above S106 also includes: performing accuracy verification on the n sub-entity objects respectively; accordingly, if the n sub-entity objects are combined to obtain the reporting entity object for generating the drill report, it includes: if the n sub-entity objects all pass the accuracy verification, then the n sub-entity objects are combined to obtain the reporting entity object for generating the drill report.

[0065] In practical applications, the accuracy verification of each sub-entity object can be implemented using various verification methods commonly used in the art. The specific method can be selected based on actual needs and is not limited in this embodiment of the present invention. For example, for each sub-entity object, the information contained in the sub-entity object is compared with the corresponding task-related information. If they are consistent, the sub-entity object is determined to have passed the accuracy verification; otherwise, the sub-entity object is determined to have failed the accuracy verification. In this case, the corresponding task-related information can be repackaged.

[0066] S108: Generate a drill report for the target fault drill task based on the report entity object.

[0067] For example, the report entity object includes the task execution record of the target fault drill task, the function method for generating the drill report, etc. By calling the function method, a drill report for describing the task execution record can be generated.

[0068] In one embodiment, the above S108 may include the following steps: storing the reporting entity object through a local cache queue; consuming the local cache queue and locking the obtained reporting entity object; after locking the reporting entity object, generating a drill report for the target fault drill task based on the reporting entity object.

[0069] By using a message queue to store report entity objects, it is possible to achieve decoupling and asynchronous execution of the encapsulation process of the task execution record and the drill report generation process, as well as peak shaving processing under high-concurrency target fault drill tasks; on this basis, each time a report entity object is consumed, the report entity object is locked and a corresponding drill task is generated, which ensures that only one thread can perform read and write operations on the entity report object at the same time, so as to avoid data inconsistency problems caused by multi-threaded concurrent operations. Of course, it should be understood that after the corresponding drill task is generated for the currently consumed report entity object, the report entity object is unlocked and the next report entity object is consumed. In actual applications, the local cache queue can use various message middleware, such as kafka, redis and other commonly used message middleware in this field, or it can also use independently developed message middleware, etc., and the embodiments of this specification do not limit this.

[0070] The embodiment of this specification shows an implementation of the above S108. Of course, it should be understood that the above S108 can also be implemented in other ways, such as not using a local cache queue.

[0071] In another embodiment of this specification, in order to avoid wasting resources and reducing report generation efficiency by repeatedly generating drill reports, before S108, the method for generating the fault drill report may further include: querying the database based on the report identifier of the report entity object to determine whether a drill report for the target fault drill task exists; if a drill report exists in the database, outputting a prompt message, the prompt message being used to indicate that the drill report already exists in the database. The database is used to store drill reports. The prompt message may be in various appropriate forms, including but not limited to text, voice, light, vibration, etc.

[0072] Of course, if the drill report does not exist in the database, S108 is executed.

[0073] For ease of understanding, the following Figure 2 The method for generating the fault drill report described in the above embodiment is described. Figure 2, is a flow chart of a method for generating a fault drill report provided in another embodiment of this specification, the method comprising the following steps:

[0074] First, the current task set is periodically obtained through the pre-deployed scheduled tasks. The current task set includes the fault drill tasks that have been injected into the business system.

[0075] Then, the current task set is polled to obtain the report configuration information of the fault drill task currently polled, including the report generation time and task ID of the fault drill task.

[0076] Further, determine whether the report generation time of the currently polled fault drill task meets the preset report generation execution conditions, such as whether the interval between the report generation time and the current time is less than or equal to the first preset time, etc., and determine whether the task end time of the fault drill task meets the preset report generation conditions, such as whether the interval between the task end time and the current time is greater than the second preset time.

[0077] If both meet the preset report generation conditions, the currently polled fault drill task is used as the target fault drill task, and it is determined whether a drill report for the fault drill task already exists in the database.

[0078] If the drill report already exists in the database, a prompt message is output; if the drill report does not exist in the database, the task execution record of the target fault drill task is obtained from the fault drill log of the business system based on the task identifier of the target fault drill task, including but not limited to basic report information, basic task information, drill scenario information, network performance indicator information of the business system, alarm information, business operation information of the data center, etc.

[0079] Furthermore, the obtained task execution record is encapsulated into a report entity object, and a drill report is generated based on the report entity object.

[0080] If the report generation time or task end time of the currently polled fault drill task does not meet the preset report generation conditions, the next fault drill task will continue to be polled.

[0081] Repeat the above steps until all fault drill tasks in the current task set are polled.

[0082] One or more embodiments of this specification provide a method for generating a fault drill report, which configures corresponding report time information and task identifiers in the report configuration information of each fault drill task; based on the report event information, screens out target fault drill tasks that meet the requirements from the fault drill tasks currently injected into the business system, and obtains the task execution record of the target fault drill task based on the task identifier; because the task execution record reflects the execution status of the target fault drill task, the task execution record is encapsulated as a report entity object for generating a report, and then based on the report entity object, a drill report for the target fault drill task is automatically generated. It can be seen that the generation process of the fault drill report does not require manual intervention, has the advantages of saving time and effort, improving report accuracy, and is suitable for batch generation of fault drill reports.

[0083] Based on the same inventive concept, the embodiment of this specification also provides a system for generating a fault drill report. Figure 3 , is a structural block diagram of a fault drill report generation system provided in an embodiment of this specification, the system including a producer 310, a local cache queue 320 and a consumer 330.

[0084] The producer 310 is used to obtain report configuration information of the fault drill task in the current task set, where the current task set includes the fault drill tasks currently injected into the business system, and the report configuration information includes report time information and a task identifier.

[0085] The producer 310 is also used to select a target fault drill task that meets the preset report generation conditions from the current task set based on the report time information, and based on the task identifier of the target fault drill task, obtain the task execution record of the target fault drill task and encapsulate it into a report entity object and send it to the local cache queue 320.

[0086] The consumer 330 is used to consume the local cache queue 320 and generate a drill report for the target fault drill task based on the acquired entity report object.

[0087] In one embodiment, the report time information includes a report generation time;

[0088] The producer selects a target fault drill task that meets the preset report generation conditions from the current task set in the following manner:

[0089] Selecting, from the current task set, fault drill tasks whose interval between report generation time and current time is less than or equal to a first preset time, to obtain a task subset;

[0090] Based on the task identifier of the fault drill task in the task subset, obtaining the task end time of the fault drill task in the task subset;

[0091] A fault drill task whose interval between the task end time and the current time is greater than a second preset time is selected from the task subset as a target fault drill task that meets the preset report generation condition.

[0092] In one embodiment, the task execution record includes n task-related information related to the target fault drill task, where n is a positive integer;

[0093] The task execution record is encapsulated as a report entity object in the following way:

[0094] Encapsulating the n task-related information respectively to obtain n sub-entity objects, wherein the n sub-entity objects correspond one-to-one to the n task-related information;

[0095] The n sub-entity objects are combined to obtain a report entity object for generating a drill report, and a report identifier is added to the report entity object, where the report identifier is used to indicate that the report entity object belongs to the target fault drill task.

[0096] In one embodiment, the producer is further configured to:

[0097] Before combining the n sub-entity objects, respectively performing accuracy checks on the n sub-entity objects;

[0098] The producer combines the n sub-entity objects to obtain a report entity object for generating a drill report, including:

[0099] If the n sub-entity objects all pass the accuracy check, the n sub-entity objects are combined to obtain a report entity object for generating a drill report.

[0100] In one embodiment, the n task-related information includes: basic report information, basic task information, drill scenario information, network performance indicator information of the business system, alarm information, and business operation information of the data center where the business system is located;

[0101] The producer obtains the task execution record of the target fault drill task and encapsulates it into a report entity object in the following manner:

[0102] Based on the task identifier, obtaining the report basic information and the task basic information from the fault drill log of the business system;

[0103] Acquire a drill scenario identifier of the target fault drill task from the task basic information, and acquire the drill scenario information from the fault drill log based on the drill scenario identifier;

[0104] Acquire the network address of the business system from the drill scenario information, and query the network performance indicator information during the execution of the target fault drill task from the fault drill log based on the network address;

[0105] The task start time and task end time of the target fault drill task are obtained from the drill scenario information, and based on the task start time and the task end time, the alarm information during the execution of the target fault drill task is queried from the fault drill log, and the business operation information of the data center during the execution of the target fault drill task is obtained from the data center.

[0106] In one embodiment, the consumer generates a drill report for the target fault drill task in the following manner:

[0107] Storing the reporting entity object in a local cache queue;

[0108] Consume the local cache queue and lock the acquired report entity object;

[0109] After the reporting entity object is locked, a drill report for the target fault drill task is generated based on the reporting entity object.

[0110] In one embodiment, the consumer is further configured to:

[0111] Before generating a drill report for the target fault drill task based on the reporting entity object, querying a database based on a report identifier of the reporting entity object whether there is a drill report for the target fault drill task;

[0112] If the drill report exists in the database, a prompt message is output, where the prompt message is used to prompt that the drill report exists in the database.

[0113] Obviously, the generation system of the fault drill report in the embodiment of this specification can be used as the above Figure 1 The execution subject of the fault drill report generation method shown in FIG can realize the fault drill report generation method in Figure 1 Since the principle is the same, the functions realized are not described here.

[0114] In order to facilitate those skilled in the art to understand the generation system of the fault drill report provided in the embodiment of this specification, Figure 4, the process of generating a fault drill report by the fault drill report generation system is explained.

[0115] like Figure 4 As shown, first, the producer periodically obtains the current task set through the pre-deployed scheduled tasks. The current task set includes the fault drill tasks that have been injected into the business system.

[0116] Then, the producer 310 polls the current task set and obtains the report configuration information of the fault drill task currently polled, including the report generation time and task ID of the fault drill task.

[0117] Further, the producer 310 determines whether the report generation time of the currently polled fault drill task meets the preset report generation execution conditions, such as whether the interval between the report generation time and the current time is less than or equal to the first preset time, etc., and determines whether the task end time of the fault drill task meets the preset report generation conditions, such as whether the interval between the task end time and the current time is greater than the second preset time, etc.

[0118] If both meet the preset report generation conditions, the producer 310 takes the currently polled fault drill task as the target fault drill task and determines whether a drill report for the fault drill task already exists in the database.

[0119] If the drill report already exists in the database, producer 310 outputs a prompt message; if the drill report does not exist in the database, producer 310 obtains the task execution record of the target fault drill task from the fault drill log of the business system based on the task identifier of the target fault drill task, including but not limited to basic report information, basic task information, drill scenario information, network performance indicator information of the business system, alarm information, business operation information of the data center, etc.

[0120] Furthermore, the producer 310 encapsulates the acquired task execution record into a report entity object and sends it to the local cache queue 320 .

[0121] Consumer 330 subscribes to a report entity object from local cache queue 320. If the subscribed report entity object exists in local cache queue 320, the report entity object is verified for accuracy. If the verification passes, consumer 330 queries database 340 to see if a corresponding drill report already exists. If so, a prompt message is output; if not, a drill report is generated based on the report entity object and stored in database 340. Database 340 can be a component of the fault drill report generation system, or it can be independent of the fault drill report generation system.

[0122] If the report generation time or task end time of the currently polled fault drill task does not meet the preset report generation condition, the producer 310 continues to poll the next fault drill task.

[0123] Repeat the above steps until all fault drill tasks in the current task set are polled.

[0124] Based on the same inventive concept, an embodiment of this specification also provides a device for generating a fault drill report. Figure 5 5 is a structural block diagram of a fault drill report generation device 500 provided in an embodiment of this specification, including: a first acquisition unit 510, a second acquisition unit 520, a third acquisition unit 530 and a generation unit 540.

[0125] The first acquisition unit 510 is used to acquire report configuration information of a fault drill task in a current task set, where the current task set includes the fault drill tasks currently injected into the business system, and the report configuration information includes report time information and a task identifier.

[0126] The second acquiring unit 520 is configured to select, based on the report time information, a target fault drill task that meets a preset report generation condition from the current task set.

[0127] The third acquiring unit 530 is configured to acquire the task execution record of the target fault drill task based on the task identifier of the target fault drill task and encapsulate the record into a report entity object.

[0128] The generating unit 540 is configured to generate a drill report for the target fault drill task based on the report entity object.

[0129] In one embodiment, the report time information includes a report generation time;

[0130] The second acquiring unit 520 is specifically configured to:

[0131] Selecting, from the current task set, fault drill tasks whose interval between report generation time and current time is less than or equal to a first preset time, to obtain a task subset;

[0132] Based on the task identifier of the fault drill task in the task subset, obtaining the task end time of the fault drill task in the task subset;

[0133] A fault drill task whose interval between the task end time and the current time is greater than a second preset time is selected from the task subset as a target fault drill task that meets the preset report generation condition.

[0134] In one embodiment, the task execution record includes n task-related information related to the target fault drill task, where n is a positive integer;

[0135] The task execution record is encapsulated as a report entity object in the following way:

[0136] Encapsulating the n task-related information respectively to obtain n sub-entity objects, wherein the n sub-entity objects correspond one-to-one to the n task-related information;

[0137] The n sub-entity objects are combined to obtain a report entity object for generating a drill report, and a report identifier is added to the report entity object, where the report identifier is used to indicate that the report entity object belongs to the target fault drill task.

[0138] In one embodiment, the third obtaining unit is further configured to:

[0139] Before combining the n sub-entity objects, respectively performing accuracy checks on the n sub-entity objects;

[0140] When the third acquisition unit combines the n sub-entity objects to obtain the report entity object for generating the drill report, the third acquisition unit performs the following steps:

[0141] If the n sub-entity objects all pass the accuracy check, the n sub-entity objects are combined to obtain a report entity object for generating a drill report.

[0142] In one embodiment, the n task-related information includes: basic report information, basic task information, drill scenario information, network performance indicator information of the business system, alarm information, and business operation information of the data center where the business system is located;

[0143] The third acquiring unit acquires the task execution record of the target fault drill task in the following manner:

[0144] Based on the task identifier, obtaining the report basic information and the task basic information from the fault drill log of the business system;

[0145] Acquire a drill scenario identifier of the target fault drill task from the task basic information, and acquire the drill scenario information from the fault drill log based on the drill scenario identifier;

[0146] Acquire the network address of the business system from the drill scenario information, and query the network performance indicator information during the execution of the target fault drill task from the fault drill log based on the network address;

[0147] The task start time and task end time of the target fault drill task are obtained from the drill scenario information, and based on the task start time and the task end time, the alarm information during the execution of the target fault drill task is queried from the fault drill log, and the business operation information of the data center during the execution of the target fault drill task is obtained from the data center.

[0148] In one embodiment, the generating unit is specifically configured to:

[0149] Storing the reporting entity object in a local cache queue;

[0150] Consume the local cache queue and lock the acquired report entity object;

[0151] After the reporting entity object is locked, a drill report for the target fault drill task is generated based on the reporting entity object.

[0152] In one embodiment, the fault drill report generating device further includes:

[0153] A query unit, configured to query whether there is a drill report for the target fault drill task in a database based on a report identifier of the reporting entity object before the generating unit generates the drill report for the target fault drill task based on the reporting entity object;

[0154] The prompt unit is configured to output a prompt message if the drill report exists in the database, wherein the prompt message is used to prompt that the drill report exists in the database.

[0155] Obviously, the fault drill report generation device of the embodiment of this specification can be used as the above Figure 1 The execution subject of the fault drill report generation method shown in FIG can realize the fault drill report generation method in Figure 1 Since the principle is the same, the functions realized are not described here.

[0156] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this specification. Figure 6 At the hardware level, the electronic device includes a processor and, optionally, an internal bus, a network interface, and memory. The memory may include internal memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for its services.

[0157] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0158] The memory is used to store programs. Specifically, the program may include program code, which includes computer operating instructions. The memory may include internal memory and non-volatile memory, and provides instructions and data to the processor.

[0159] The processor reads the corresponding computer program from the non-volatile memory into the internal memory and then runs it, forming a device for generating a fault drill report at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0160] Acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier;

[0161] Based on the report time information, selecting a target fault drill task that meets a preset report generation condition from the current task set;

[0162] Based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object;

[0163] A drill report for the target fault drill task is generated based on the report entity object.

[0164] The above is as in this manual Figure 1The method performed by the apparatus for generating a fault drill report disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be performed by hardware integrated logic circuits in the processor or by software instructions. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of this specification can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of this specification can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0165] It should be understood that the electronic device of the embodiment of this specification can realize the generation device of the fault drill report in Figure 1 Since the principles are the same, the embodiments of this specification will not be described in detail here.

[0166] Of course, in addition to software implementation, the electronic device in this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0167] The embodiment of this specification also proposes a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by a portable electronic device including multiple application programs, can enable the portable electronic device to execute Figure 1 The method of the embodiment shown is specifically used to perform the following operations:

[0168] Acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier;

[0169] Based on the report time information, selecting a target fault drill task that meets a preset report generation condition from the current task set;

[0170] Based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object;

[0171] A drill report for the target fault drill task is generated based on the report entity object.

[0172] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0173] In short, the above description is only a preferred embodiment of this specification and is not intended to limit the scope of protection of this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of protection of this specification.

[0174] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0175] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0176] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0177] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

Claims

1. A method for generating a fault drill report, characterized in that: include: Acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier; Based on the report time information, selecting a target fault drill task that meets a preset report generation condition from the current task set; Based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object; A drill report for the target fault drill task is generated based on the report entity object.

2. The method according to claim 1, wherein The report time information includes the report generation time; The selecting, based on the report time information, a target fault drill task that meets a preset report generation condition from the current task set includes: Selecting, from the current task set, fault drill tasks whose interval between report generation time and current time is less than or equal to a first preset time, to obtain a task subset; Based on the task identifier of the fault drill task in the task subset, obtaining the task end time of the fault drill task in the task subset; A fault drill task whose interval between the task end time and the current time is greater than a second preset time is selected from the task subset as a target fault drill task that meets the preset report generation condition.

3. The method according to claim 1, wherein The task execution record includes n task related information related to the target fault drill task, where n is a positive integer; The task execution record is encapsulated as a report entity object in the following way: Encapsulating the n task-related information respectively to obtain n sub-entity objects, wherein the n sub-entity objects correspond one-to-one to the n task-related information; The n sub-entity objects are combined to obtain a report entity object for generating a drill report, and a report identifier is added to the report entity object, where the report identifier is used to indicate that the report entity object belongs to the target fault drill task.

4. The method according to claim 3, wherein Before combining the n sub-entity objects, the method further includes: Performing accuracy checks on the n sub-entity objects respectively; The combining of the n sub-entity objects to obtain a report entity object for generating a drill report includes: If the n sub-entity objects all pass the accuracy check, the n sub-entity objects are combined to obtain a report entity object for generating a drill report.

5. The method according to claim 3, wherein The n task-related information includes: basic report information, basic task information, drill scenario information, network performance indicator information of the business system, alarm information, and business operation information of the data center where the business system is located; The acquiring of the task execution record of the target fault drill task based on the task identifier of the target fault drill task includes: Based on the task identifier, obtaining the report basic information and the task basic information from the fault drill log of the business system; Acquire a drill scenario identifier of the target fault drill task from the task basic information, and acquire the drill scenario information from the fault drill log based on the drill scenario identifier; Acquire the network address of the business system from the drill scenario information, and query the network performance indicator information during the execution of the target fault drill task from the fault drill log based on the network address; The task start time and task end time of the target fault drill task are obtained from the drill scenario information, and based on the task start time and the task end time, the alarm information during the execution of the target fault drill task is queried from the fault drill log, and the business operation information of the data center during the execution of the target fault drill task is obtained from the data center.

6. The method according to claim 1, wherein Generating a drill report for the target fault drill task based on the report entity object includes: Storing the reporting entity object in a local cache queue; Consume the local cache queue and lock the acquired report entity object; After the reporting entity object is locked, a drill report for the target fault drill task is generated based on the reporting entity object.

7. The method according to claim 1, wherein Before generating a drill report for the target fault drill task based on the report entity object, the method further includes: Based on the report identifier of the reporting entity object, querying whether there is a drill report for the target fault drill task in the database; If the drill report exists in the database, a prompt message is output, where the prompt message is used to prompt that the drill report exists in the database.

8. A system for generating a fault drill report, characterized in that: include: Producer, consumer, and local cache queues; The producer is configured to obtain report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill tasks currently injected into the business system, and the report configuration information includes report time information and a task identifier; The producer is further configured to select, from the current task set, a target fault drill task that meets a preset report generation condition based on the report time information, and, based on the task identifier of the target fault drill task, obtain the task execution record of the target fault drill task, encapsulate the record into a report entity object, and then send the result to the local cache queue; The consumer is used to consume the local cache queue and generate a drill report for the target fault drill task based on the acquired entity report object.

9. A device for generating a fault drill report, characterized in that: include: A first acquiring unit is configured to acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier; A second acquiring unit is configured to select, based on the report time information, a target fault drill task that meets a preset report generation condition from the current task set; A third acquiring unit is configured to acquire, based on the task identifier of the target fault drill task, the task execution record of the target fault drill task and encapsulate the record into a report entity object; A generating unit is configured to generate a drill report for the target fault drill task based on the report entity object.

10. An electronic device, characterized in that: include: processor; as well as a memory arranged to store computer-executable instructions which, when executed, cause the processor to: Acquire report configuration information of a fault drill task in a current task set, wherein the current task set includes the fault drill task currently injected into the business system, and the report configuration information includes report time information and a task identifier; Based on the report time information, selecting a target fault drill task that meets a preset report generation condition from the current task set; Based on the task identifier of the target fault drill task, obtaining the task execution record of the target fault drill task and encapsulating it into a report entity object; A drill report for the target fault drill task is generated based on the report entity object.

Images