Fault playback method, device and electronic equipment

Abstract

The present application provides a fault playback method, device and electronic device, which belongs to the field of computers. The fault playback method of an embodiment of the present application includes: responding to a fault playback instruction for a target historical fault event, obtaining saved fault data corresponding to the target historical fault event; sending a call request to the emergency system, the call request including the fault data and a playback identifier corresponding to the target historical fault event; obtaining a fault playback result obtained by the emergency system in the isolated environment based on the fault data for fault recovery, so that the saved real fault data can be used when performing fault playback, and online capabilities, including environment, link, strategy, configuration, etc., can be reused to truly reflect the feedback of the current actual emergency system and avoid affecting the online environment.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and specifically relates to a fault playback method, device and electronic equipment. Background Art

[0002] There are two main methods for replaying related faults. The first method is to set the fault replay time and circle the affected people. The monitoring platform will replay part of the monitoring data when the fault event occurs at the current time, and the circled people can see the historical fault data of the specified monitoring at the current time point. The second method is to simulate the fault in a grayscale or simulated environment.

[0003] The above two methods have the following disadvantages: For the first method, the fault data at the time of the fault event is displayed at the current time point, which will affect the normal viewing of the current time monitoring data by the designated person; only one fault can be played back at the same time, and multiple faults cannot be played back at the same time; it simply displays the monitoring data performance when the fault event occurs. For the second method, due to the use of simulation, its environmental simulation, emergency decision-making simulation and fault resolution simulation are all different from the actual situation.

[0004] In summary, the relevant fault playback methods cannot truly reflect the feedback of the current actual emergency system. Summary of the invention

[0005] In view of this, the present application provides a fault playback method, device and electronic device, which are used to solve the problem that the emergency system cannot be verified through fault playback.

[0006] Specifically, the present application is implemented through the following technical solutions:

[0007] In a first aspect, a fault playback method is provided, which is applied to a fault playback system, wherein the fault playback system stores fault data corresponding to historical fault events triggered on an emergency system connected to the fault playback system, and the method includes:

[0008] In response to a fault playback instruction for a target historical fault event, acquiring stored fault data corresponding to the target historical fault event;

[0009] Sending a call request to the emergency system; wherein the call request includes fault data corresponding to the target historical fault event and a playback identifier, and the playback identifier is used to instruct the emergency system to perform fault recovery based on the fault data in an isolated environment to complete the fault playback corresponding to the target historical fault event;

[0010] A fault replay result obtained by the emergency system performing fault recovery based on the fault data in the isolated environment is obtained.

[0011] Optionally, the method further includes: in response to a fault event triggered on the emergency system, acquiring fault data corresponding to the fault event from the emergency system, and storing the acquired fault data locally.

[0012] Optionally, the emergency system includes a fault location system and a fault self-healing system;

[0013] The fault scenarios corresponding to the fault event include:

[0014] An emergency scenario, wherein the emergency scenario is a scenario related to the fault location capability of the fault location system; correspondingly, the fault event is an emergency event related to the fault location triggered by the fault location system;

[0015] The self-healing scenario is a scenario related to the fault self-healing capability of the fault self-healing system; correspondingly, the fault event is a warning event related to the fault self-healing triggered by the fault self-healing system.

[0016] Optionally, the fault playback system is connected to a business platform; the fault location system includes a basic service platform with service anomaly location capability that provides basic services to the business platform; the fault self-healing system includes a self-healing platform that provides fault self-healing services to the business platform.

[0017] Optionally, in response to a fault event triggered on the emergency system, acquiring fault data corresponding to the fault event from the emergency system includes:

[0018] If the fault event is an emergency event under the emergency scenario, monitor the emergency event triggered on the fault location system, and in response to the monitored emergency event triggered on the fault location system, obtain context data corresponding to the fault location processing related to the emergency event from the fault location system as the fault data corresponding to the emergency event;

[0019] If the fault event is a warning event in the self-healing scenario, monitor the warning event triggered on the fault self-healing system, and in response to the monitored warning event triggered on the fault self-healing system, obtain warning information corresponding to the fault self-healing processing related to the warning event from the fault self-healing system as the fault data corresponding to the warning event.

[0020] Optionally, after obtaining a fault playback result from a system related to the fault scenario, the method further includes:

[0021] Verify whether the fault playback result meets expectations, and label the fault playback result according to the verification result.

[0022] In a second aspect, a fault playback device is provided, comprising:

[0023] A data storage module, configured to obtain stored fault data corresponding to a target historical fault event in response to a fault playback instruction for the target historical fault event;

[0024] A fault playback module, used to send a call request to the emergency system; wherein the call request includes fault data corresponding to the target historical fault event and a playback identifier, and the playback identifier is used to instruct the emergency system to perform fault recovery based on the fault data in an isolated environment to complete the fault playback corresponding to the target historical fault event;

[0025] The conclusion processing module is used to obtain the fault playback result obtained by the emergency system performing fault recovery based on the fault data in the isolated environment.

[0026] Optionally, the data saving module is further used to respond to a fault event triggered on the emergency system, obtain fault data corresponding to the fault event from the emergency system, and save the obtained fault data locally.

[0027] Optionally, the emergency system includes a fault location system and a fault self-healing system;

[0028] The fault scenarios corresponding to the fault event include:

[0029] An emergency scenario, wherein the emergency scenario is a scenario related to the fault location capability of the fault location system; correspondingly, the fault event is an emergency event related to the fault location triggered by the fault location system;

[0030] The self-healing scenario is a scenario related to the fault self-healing capability of the fault self-healing system; correspondingly, the fault event is a warning event related to the fault self-healing triggered by the fault self-healing system.

[0031] According to a third aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the steps of the method according to the first aspect are implemented.

[0032] In a fourth aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in the first aspect when executing the program.

[0033] The embodiment of the present application obtains the saved fault data corresponding to the target historical fault event by responding to the fault replay instruction for the target historical fault event; sends a call request to the emergency system, the call request including the fault data and the replay identifier corresponding to the target historical fault event; obtains the fault replay result obtained by the emergency system in the isolated environment based on the fault data for fault recovery, so that the saved real fault data can be used during fault replay, and online capabilities, including environment, links, policies, configurations, etc., can be reused to truly reflect the feedback of the current actual emergency system and avoid affecting the online environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 It is a flowchart of a fault playback method shown in an exemplary embodiment of the present application;

[0035] Figure 2 is a system framework diagram shown in an exemplary embodiment of the present application;

[0036] Figure 3 is a flowchart of another fault playback method shown in an exemplary embodiment of the present application;

[0037] Figure 4 It is a structural schematic diagram of a fault playback device shown in an exemplary embodiment of the present application;

[0038] Figure 5 It is a structural schematic diagram of a computer device shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0039] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0040] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0041] It should be understood that although the terms first, second, third, etc. may be used in the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0042] Figure 1 A fault playback method provided in an embodiment of the present application is shown, which is applied to a fault playback system, wherein the fault playback system stores fault data corresponding to historical fault events triggered on an emergency system connected to the fault playback system.

[0043] In one embodiment, in response to a fault event triggered on the emergency system, fault data corresponding to the fault event is obtained from the emergency system, and the obtained fault data is saved locally to ensure that the on-site data is saved as soon as the fault event occurs.

[0044] Fault data can include all data involved in the fault event, mainly including monitoring data, change data, log data, etc., which are mainly divided into three types of data:

[0045] Time series data: refers to data with timestamps, such as monitoring data and log data. Permanent storage capabilities are required for this type of data.

[0046] Status data: data indicating the status of the machine. This type of data can be converted into time-stamped data and stored permanently with the help of the RMC high-availability data base;

[0047] Real-time data: This type of data does not need to be saved and can be directly accessed to the latest data.

[0048] The fault playback method comprises the following steps.

[0049] S110 . In response to a fault playback instruction for a target historical fault event, obtain stored fault data corresponding to the target historical fault event.

[0050] The fault playback instruction may be an instruction triggered by a manual playback operation, or an instruction automatically triggered by the system, and is used to instruct the fault playback system to trigger a fault playback for a target historical fault event.

[0051] S120. Send a call request to the emergency system; wherein the call request includes fault data and a playback identifier corresponding to the target historical fault event, and the playback identifier is used to instruct the emergency system to perform fault recovery based on the fault data in an isolated environment to complete the fault playback corresponding to the target historical fault event.

[0052] Once the emergency system recognizes the playback identifier, it needs to perform online security isolation. For example, a secure area built by software and hardware methods can be built to perform fault playback, such as a trusted execution environment (TEE).

[0053] S130: Obtain a fault playback result obtained by the emergency system performing fault recovery based on the fault data in the isolated environment.

[0054] The emergency system sends the fault playback results back to the fault playback system, which assembles and displays the fault playback results and can verify the emergency system based on the fault playback results.

[0055] In one embodiment, after step S130, the method further includes:

[0056] Verify whether the fault playback result meets expectations, and label the fault playback result according to the verification result. Subsequently, the fault playback system can notify the staff and groups involved in the playback of the result.

[0057] It can be seen from the technical solutions of the above embodiments that the embodiments of the present application obtain the saved fault data corresponding to the target historical fault event by responding to the fault replay instruction for the target historical fault event; send a call request to the emergency system, the call request including the fault data and replay identifier corresponding to the target historical fault event; obtain the fault replay result obtained by the emergency system in the isolated environment based on the fault data for fault recovery, so that the saved real fault data can be used when performing fault replay, and online capabilities, including environment, links, policies, configurations, etc., can be reused to truly reflect the feedback of the current actual emergency system and avoid affecting the online environment.

[0058] Based on the above embodiments, in one implementation, the emergency system includes a fault location system and a fault self-healing system, and the fault location system and the fault self-healing system respectively serve as two types of trigger sources for the entire emergency system, namely, a location capability trigger source and a self-healing capability trigger source.

[0059] The fault scenarios corresponding to the fault event include: emergency scenarios and self-healing scenarios.

[0060] The emergency scenario is a scenario related to the fault location capability of the fault location system; correspondingly, the fault event is an emergency event related to the fault location triggered by the fault location system;

[0061] The self-healing scenario is a scenario related to the fault self-healing capability of the fault self-healing system; correspondingly, the fault event is a warning event related to the fault self-healing triggered by the fault self-healing system.

[0062] Correspondingly, the fault playback instruction for the target historical fault event in step S110 may be to perform a fault playback for the emergency event or warning event corresponding to the target historical fault event, that is, to perform a fault playback for the emergency scenario or self-healing scenario.

[0063] In one embodiment, in response to a fault event triggered on the emergency system, obtaining fault data corresponding to the fault event from the emergency system includes:

[0064] If the fault event is an emergency event under the emergency scenario, monitor the emergency event triggered on the fault location system, and in response to the monitored emergency event triggered on the fault location system, obtain context data corresponding to the fault location processing related to the emergency event from the fault location system as the fault data corresponding to the emergency event;

[0065] If the fault event is a warning event in the self-healing scenario, monitor the warning event triggered on the fault self-healing system, and in response to the monitored warning event triggered on the fault self-healing system, obtain warning information corresponding to the fault self-healing processing related to the warning event from the fault self-healing system as the fault data corresponding to the warning event.

[0066] In one embodiment, the fault playback system is connected to a business platform; the fault location system includes a basic service platform with service anomaly location capability that provides basic services to the business platform; the fault self-healing system includes a self-healing platform that provides fault self-healing services to the business platform.

[0067] It can be seen from the technical solutions of the above embodiments that the embodiments of the present application divide the fault scenarios corresponding to the fault events into emergency scenarios and self-healing scenarios through a fault location system and a fault self-healing system, thereby better multiplexing the emergency capabilities on the line.

[0068] Based on the above embodiments, Figure 2As shown, the embodiment of the present application also provides a system framework diagram for executing the above-mentioned fault playback method, including: a fault playback system 20, a business system 21, a fault location system 22, a fault self-healing system 23, a monitoring system 24 and a message center 25. Among them, the monitoring system 24 is used to monitor emergency events triggered on the fault location system and early warning events triggered on the fault self-healing system. The message center 25 is used to record early warning information.

[0069] Based on the above system framework, such as Figure 3 As shown, the embodiment of the present application also provides a complete fault playback process, and the specific steps are mainly divided into three parts: data preservation, fault playback, and conclusion marking.

[0070] Data preservation: mainly saves all fault data and fault scenarios that the emergency system relies on. Among them, all fault data that the emergency system relies on can include monitoring, logs, changes and other data. Fault scenarios mainly refer to the fault data corresponding to the corresponding fault events. Only one data preservation is required for one fault event. Specifically, the following steps are included.

[0071] 1: The fault playback system obtains the fault event trigger and creates a fault scenario. If it is an emergency event, it associates the emergency event ID.

[0072] 2: Trigger the fault data saving to the monitoring system;

[0073] 3: The monitoring system saves fault data;

[0074] 4: The monitoring system returns the saved results to the fault playback system;

[0075] 5: For emergency events, request the business system to obtain the context data corresponding to the fault location processing related to the emergency event according to the emergency event ID;

[0076] 5.1: Get the return request result from the business system;

[0077] 6: Save the emergency scenario, that is, save the fault data corresponding to the emergency event;

[0078] 7: Corresponding to the warning event, request the fault self-healing system to obtain the corresponding context data of the fault self-healing process related to the warning event according to the time range;

[0079] 7.1: Get the return request result from the fault self-healing system;

[0080] 8: Save the self-healing scenario, that is, save the fault data corresponding to the warning event.

[0081] Fault playback:

[0082] 9: The fault playback system obtains the fault playback for the target historical fault event: emergency scenario;

[0083] 10: Triggering fault playback of emergency scenarios to the business system, including sending upper and lower data and playback identifiers corresponding to the fault location processing related to the emergency event to the business system;

[0084] 10.1: Business system generates emergency events;

[0085] 10.2: The business system triggers fault location to the fault location system;

[0086] 10.3: The fault location system performs fault location;

[0087] 10.3.1: The fault location system assembles the location conclusion;

[0088] 10.4: The fault location system returns the fault location conclusion to the business system;

[0089] 10.5: The business system returns the fault location conclusion to the fault playback system;

[0090] 12: The fault replay system obtains the fault replay for the target historical fault event: self-healing scenario;

[0091] 13: The fault playback system sends warning information to the message center;

[0092] 14: The fault self-healing system monitors and replays the warning information from the message center;

[0093] 14.1: The fault self-recovery system performs fault self-recovery operations;

[0094] 14.2: The fault self-healing system sends the fault self-healing result to the message center;

[0095] 14.3: The fault replay system asynchronously obtains the fault self-healing results from the message center.

[0096] Conclusion Marking:

[0097] 11: Request the business center to verify the fault location result to determine whether it meets expectations;

[0098] 11.1: The verification conclusion is returned from the business center, and the fault location result is labeled. Finally, the result of the fault playback is notified to the user.

[0099] Corresponding to the above-mentioned embodiment of the fault playback method, the present application also provides an embodiment of a fault playback device.

[0100] like Figure 4As shown, the fault playback device includes: a data storage module 401, a fault playback module 402 and a conclusion processing module 403.

[0101] The data saving module 401 is used to respond to a fault playback instruction for a target historical fault event, and obtain the saved fault data corresponding to the target historical fault event; the fault playback module 402 is used to send a call request to the emergency system; wherein the call request includes the fault data and a playback identifier corresponding to the target historical fault event, and the playback identifier is used to instruct the emergency system to perform fault recovery based on the fault data in an isolated environment to complete the fault playback corresponding to the target historical fault event; the conclusion processing module 403 is used to obtain the fault playback result obtained by the emergency system performing fault recovery based on the fault data in the isolated environment.

[0102] Optionally, the data saving module 401 is further configured to, in response to a fault event triggered on the emergency system, obtain fault data corresponding to the fault event from the emergency system, and save the obtained fault data locally.

[0103] Optionally, the conclusion processing module 403 is further used to verify whether the fault playback result meets expectations, and to label the fault playback result according to the verification result.

[0104] It can be seen from the technical solutions of the above embodiments that the embodiments of the present application obtain the saved fault data corresponding to the target historical fault event by responding to the fault replay instruction for the target historical fault event; send a call request to the emergency system, the call request including the fault data and replay identifier corresponding to the target historical fault event; obtain the fault replay result obtained by the emergency system in the isolated environment based on the fault data for fault recovery, so that the saved real fault data can be used when performing fault replay, and online capabilities, including environment, links, policies, configurations, etc., can be reused to truly reflect the feedback of the current actual emergency system and avoid affecting the online environment.

[0105] Optionally, the emergency system includes a fault location system and a fault self-healing system;

[0106] The fault scenarios corresponding to the fault event include:

[0107] An emergency scenario, wherein the emergency scenario is a scenario related to the fault location capability of the fault location system; correspondingly, the fault event is an emergency event related to the fault location triggered by the fault location system;

[0108] The self-healing scenario is a scenario related to the fault self-healing capability of the fault self-healing system; correspondingly, the fault event is a warning event related to the fault self-healing triggered by the fault self-healing system.

[0109] Optionally, the fault playback system is connected to a business platform; the fault location system includes a basic service platform with service anomaly location capability that provides basic services to the business platform; the fault self-healing system includes a self-healing platform that provides fault self-healing services to the business platform.

[0110] Optionally, the data storage module 401 is used to:

[0111] If the fault event is an emergency event under the emergency scenario, monitor the emergency event triggered on the fault location system, and in response to the monitored emergency event triggered on the fault location system, obtain context data corresponding to the fault location processing related to the emergency event from the fault location system as the fault data corresponding to the emergency event;

[0112] If the fault event is a warning event in the self-healing scenario, monitor the warning event triggered on the fault self-healing system, and in response to the monitored warning event triggered on the fault self-healing system, obtain warning information corresponding to the fault self-healing processing related to the warning event from the fault self-healing system as the fault data corresponding to the warning event.

[0113] It can be seen from the technical solutions of the above embodiments that the embodiments of the present application divide the fault scenarios corresponding to the fault events into emergency scenarios and self-healing scenarios through a fault location system and a fault self-healing system, thereby better multiplexing the emergency capabilities on the line.

[0114] The embodiments of the fault playback device of the present application can be applied to computer devices. The device embodiments can be implemented by software, hardware, or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor of the computer device in which it is located reading the corresponding computer program instructions in the non-volatile memory into the memory and running them. From the hardware level, if Figure 5 As shown, it is a hardware structure diagram of the computer device where the fault playback device of the present application is located. Figure 5 In addition to the processor, memory, network interface, and non-volatile memory shown, the computer device where the apparatus in the embodiment is located may also include other hardware according to the actual function of the computer device, which will not be described in detail.

[0115] The implementation process of the functions and effects of each unit in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

[0116] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present application scheme. A person of ordinary skill in the art can understand and implement it without paying any creative work.

[0117] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the computer device method described above are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0118] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0119] The embodiments of the subject matter and functional operations described in this specification may be implemented in the following: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. The embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules in computer program instructions encoded on a tangible non-temporary program carrier to be executed by a data processing device or to control the operation of the data processing device. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal, such as a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information and transmit it to a suitable receiver device for execution by a data processing device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

[0120] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform corresponding functions by operating on input data and generating output. The processes and logic flows can also be performed by special purpose logic circuits, such as FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits), and the apparatus can also be implemented as special purpose logic circuits.

[0121] Computers suitable for executing computer programs include, for example, general and / or special microprocessors, or any other type of central processing unit. Typically, the central processing unit will receive instructions and data from a read-only memory and / or a random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, the computer will also include one or more large-capacity storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, or the computer will be operably coupled to this large-capacity storage device to receive data from it or to transmit data to it, or both. However, the computer does not necessarily have such a device. In addition, the computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0122] Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0123] Although this specification includes many specific implementation details, these should not be interpreted as limiting the scope of any invention or the scope of protection claimed, but are mainly used to describe the features of the specific embodiments of specific inventions. Certain features described in multiple embodiments in this specification may also be implemented in combination in a single embodiment. On the other hand, the various features described in a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although features may work in certain combinations as described above and even initially claim protection, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may point to a sub-combination or a variation of a sub-combination.

[0124] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the particular order shown or performed sequentially, or requiring that all illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system modules and components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product, or packaged into multiple software products.

[0125] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In some implementations, multitasking and parallel processing may be advantageous.

[0126] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A fault playback method, characterized in that: Applied to a fault playback system, the fault playback system saves fault data corresponding to historical fault events triggered on an emergency system connected to the fault playback system, the method comprising: In response to a fault playback instruction for a target historical fault event, acquiring stored fault data corresponding to the target historical fault event; Sending a call request to the emergency system; wherein the call request includes fault data corresponding to the target historical fault event and a playback identifier, the playback identifier is used to instruct the emergency system to perform fault recovery based on the fault data in an isolated environment to complete the fault playback corresponding to the target historical fault event, the isolated environment is created by the emergency system; A fault replay result obtained by the emergency system performing fault recovery based on the fault data in the isolated environment is obtained.

2. The method according to claim 1, characterized in that The method further includes: in response to a fault event triggered on the emergency system, acquiring fault data corresponding to the fault event from the emergency system, and storing the acquired fault data locally.

3. The method according to claim 2, characterized in that The emergency system includes a fault location system and a fault self-healing system; The fault scenarios corresponding to the fault event include: An emergency scenario, wherein the emergency scenario is a scenario related to the fault location capability of the fault location system; correspondingly, the fault event is an emergency event related to the fault location triggered by the fault location system; The self-healing scenario is a scenario related to the fault self-healing capability of the fault self-healing system; correspondingly, the fault event is a warning event related to the fault self-healing triggered by the fault self-healing system.

4. The method according to claim 3, characterized in that The fault playback system is connected to the business platform; the fault location system includes a basic service platform with service anomaly location capability that provides basic services to the business platform; The fault self-healing system includes a self-healing platform that provides fault self-healing services for the business platform.

5. The method according to claim 3, characterized in that: The step of obtaining, in response to a fault event triggered on the emergency system, fault data corresponding to the fault event from the emergency system comprises: If the fault event is an emergency event under the emergency scenario, monitor the emergency event triggered on the fault location system, and in response to the monitored emergency event triggered on the fault location system, obtain context data corresponding to the fault location processing related to the emergency event from the fault location system as the fault data corresponding to the emergency event; If the fault event is a warning event in the self-healing scenario, monitor the warning event triggered on the fault self-healing system, and in response to the monitored warning event triggered on the fault self-healing system, obtain warning information corresponding to the fault self-healing processing related to the warning event from the fault self-healing system as the fault data corresponding to the warning event.

6. The method according to claim 1, characterized in that After obtaining a fault playback result from a system related to the fault scenario, the method further includes: Verify whether the fault playback result meets expectations, and label the fault playback result according to the verification result.

7. A fault playback device, characterized in that: include: A data storage module, configured to obtain stored fault data corresponding to a target historical fault event in response to a fault playback instruction for the target historical fault event; A fault playback module, used to send a call request to the emergency system; wherein the call request includes fault data corresponding to the target historical fault event and a playback identifier, and the playback identifier is used to instruct the emergency system to perform fault recovery based on the fault data in an isolated environment to complete the fault playback corresponding to the target historical fault event, and the isolated environment is created by the emergency system; The conclusion processing module is used to obtain the fault playback result obtained by the emergency system performing fault recovery based on the fault data in the isolated environment.

8. The device according to claim 7, characterized in that The data saving module is further used for acquiring fault data corresponding to the fault event from the emergency system in response to the fault event triggered on the emergency system, and storing the acquired fault data locally.

9. The device according to claim 8, characterized in that The emergency system includes a fault location system and a fault self-healing system; The fault scenarios corresponding to the fault event include: An emergency scenario, wherein the emergency scenario is a scenario related to the fault location capability of the fault location system; correspondingly, the fault event is an emergency event related to the fault location triggered by the fault location system; The self-healing scenario is a scenario related to the fault self-healing capability of the fault self-healing system; correspondingly, the fault event is a warning event related to the fault self-healing triggered by the fault self-healing system.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of any method described in claims 1-6 are implemented.

11. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the method according to any one of claims 1 to 6 are implemented.

Images