Fault result display method and device

Abstract

The present invention relates to the field of computer technology, and discloses a method and device for displaying fault results. The method comprises: acquiring fault data; determining fault process information corresponding to the fault data according to the fault data; wherein the fault process information indicates the processing state of the fault data at each current stage; if the current stage is the first target stage, and the first processing state of the fault data corresponding to the current stage is in the first preset state, determining the fault completion time corresponding to each current stage; inputting the fault process information and the fault completion time into a preset replay architecture, obtaining the fault result, and displaying the fault result.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, computer equipment, storage medium and program product for displaying fault results. Background Art

[0002] As information and digital transformation accelerates, enterprises have higher and higher requirements for operation and maintenance efficiency and accuracy. As a key link to ensure the stable operation of the system, the efficiency and quality of the traditional operation and maintenance process directly affect the continuity of business and user experience. However, traditional operation and maintenance methods, especially fault reporting and handling, often rely on offline verbal communication and manual data collection. This method is not only inefficient, but also prone to human errors, affecting the accuracy and timeliness of operation and maintenance. Summary of the invention

[0003] In view of this, the present invention provides a method, apparatus, computer equipment, storage medium and program product for displaying fault results.

[0004] In a first aspect, the present invention provides a method for displaying fault results, the method comprising: acquiring fault data; determining fault process information corresponding to the fault data based on the fault data; wherein the fault process information indicates a processing status of the fault data in each current stage; if the current stage is the first target stage, and the first processing status of the fault data corresponding to the current stage is in a first preset state, determining the fault completion time corresponding to each current stage; inputting the fault process information and the fault completion time into a preset replay architecture to obtain the fault result, and displaying the fault result.

[0005] The method for displaying fault results provided in this embodiment captures abnormal data, i.e., fault data, in the system or application in real time. This avoids the inefficient method of relying on offline verbal communication and improves the timeliness of fault discovery. In addition, based on the captured fault data, the state of the fault at each processing stage is automatically analyzed and determined to form fault process information. This process reduces manual intervention and improves the accuracy and efficiency of data processing.

[0006] At the same time, in the fault process, when the current stage reaches the first target stage and the fault data of this stage is in the first preset state, the system automatically calculates the fault completion time of each stage. This automated process reduces errors in human judgment and data collection and improves the accuracy of operation and maintenance. The fault process information and fault completion time are input into the preset replay architecture, which can automatically generate fault result reports based on standardized data processing and analysis processes. This avoids the subjectivity of human analysis and ensures the consistency and traceability of the fault handling process.

[0007] In addition, by displaying the fault results, including fault process information and fault completion time, the operation and maintenance team can clearly understand the entire process of fault handling. This helps to achieve information sharing and collaborative work between operation and maintenance personnel of different professions and reduce communication barriers.

[0008] In one possible implementation, before determining the fault process information corresponding to the fault data based on the fault data, the method also includes: determining the priority corresponding to the fault data, and detecting whether there is fault data being processed in the storage queue; if there is no fault data being processed in the storage queue, and the priority corresponding to the fault data is greater than the priority of the fault data in the storage queue, executing the step of determining the fault process information corresponding to the fault data based on the fault data.

[0009] The method for displaying fault results provided in this embodiment can ensure that high-priority faults are processed first by determining the priority of fault data. This helps to quickly respond to faults of key services or important equipment and reduce the service interruption time caused by faults. In addition, when there is no fault data being processed in the storage queue, high-priority faults can immediately enter the processing flow without waiting for the processing of other low-priority faults. This reduces the waiting time for fault processing and improves the overall processing efficiency.

[0010] In a possible implementation, the method also includes: if the second processing state of the fault data of the second target stage is not in the second preset state, and the time duration that the second processing state of the fault data of the second target stage is not in the second preset state is not less than the preset time duration, raising the initial level of the second processing state of the fault data of the second target stage to the target level; wherein the second target stage is any one of the stages; and according to the target level, giving priority to processing the fault data of the second target stage.

[0011] In the method for displaying fault results provided in this embodiment, when the fault data of a certain stage fails to reach the preset processing state for a long time, it indicates that the fault may be more complicated or have a greater impact. By improving the processing level of these fault data, it can be ensured that they are responded to and processed faster, thereby shortening the fault recovery time.

[0012] At the same time, by giving priority to handling critical faults, problems in the system can be resolved more quickly, reducing business interruption time caused by faults, thereby improving overall operation and maintenance efficiency.

[0013] In a possible implementation, displaying the fault result includes: generating a copy document corresponding to the fault result according to the fault result and a preset copy template, and displaying the copy document.

[0014] The method for displaying fault results provided in this embodiment can automatically fill the fault results into the template through the preset copy template to generate a complete copy document. This process does not require manual intervention, which greatly improves the efficiency of document generation. In addition, the preset copy template usually contains standardized formats and styles, such as the title, body, conclusion and other parts. By using this template, it can be ensured that the generated copy document has a consistent format and style, improving the readability and professionalism of the document.

[0015] In a possible implementation, the method further includes: generating a replay document corresponding to the fault result according to the fault result, and sending the replay document to a user corresponding to the fault process information.

[0016] The display method of the fault result provided in this embodiment records the discovery, handling process, handling results and lessons learned of the fault in detail in the replay document, which helps the user to fully understand the fault situation. At the same time, by sending the replay document to the user, the user can timely understand the progress and results of the fault handling.

[0017] In a possible implementation, when there are multiple types of fault data, the method also includes: obtaining associated fault data of the fault data; determining fault process information corresponding to the associated fault data based on the associated fault data; if the stage corresponding to the associated fault data is the third target stage, the third processing state corresponding to the third target stage is in the third preset state, and the current stage is the first target stage, the first processing state of the fault data corresponding to the current stage is in the first preset state, updating the current state of the fault data to a resolved state.

[0018] The method for displaying fault results provided in this embodiment can perform a more comprehensive and in-depth analysis of faults by obtaining associated fault data. This helps to discover potential connections and common causes between faults, thereby formulating more effective solutions. At the same time, when processing multiple types of fault data, it is easy to overlook certain related faults. Through association analysis, it can be ensured that all related faults are properly handled to avoid omissions.

[0019] In a second aspect, the present invention provides a device for displaying fault results, the device comprising: an acquisition module for acquiring fault data; a first determination module for determining fault process information corresponding to the fault data based on the fault data; wherein the fault process information indicates a processing status of the fault data in each current stage; a second determination module for determining the fault completion time corresponding to each current stage if the current stage is the first target stage and the first processing status of the fault data corresponding to the current stage is in a first preset state; a determination display module for inputting the fault process information and the fault completion time into a preset replay architecture to obtain the fault result, and display the fault result.

[0020] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, computer instructions being stored in the memory, and the processor executing the method for displaying fault results of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0021] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method for displaying fault results of the first aspect or any corresponding embodiment thereof.

[0022] In a fifth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the method for displaying fault results of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 is a flow chart of a method for displaying fault results according to an embodiment of the present invention;

[0025] Figure 2 is a schematic diagram of a replay architecture provided according to an embodiment of the present invention;

[0026] Figure 3 It is a schematic diagram of notification in the replay architecture provided according to an embodiment of the present invention;

[0027] Figure 4 is a schematic diagram of a timeline of a replay progress in a replay architecture provided according to an embodiment of the present invention;

[0028] Figure 5 is a schematic diagram of a method for displaying fault results according to an embodiment of the present invention;

[0029] Figure 6 is a structural block diagram of a device for displaying fault results according to an embodiment of the present invention;

[0030] Figure 7 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0032] Based on the relevant technical content, it can be seen that with the increasingly accelerated informatization and digital transformation, enterprises have higher and higher requirements for operation and maintenance efficiency and accuracy. The efficiency and quality of the traditional operation and maintenance process, as a key link to ensure the stable operation of the system, directly affect the continuity of business and user experience. However, the traditional operation and maintenance methods, especially the fault reporting and handling links, often rely on offline verbal communication and manual data collection. This method is not only inefficient, but also prone to human errors, affecting the accuracy and timeliness of operation and maintenance.

[0033] Based on this, the present invention provides a method for displaying fault results, which captures abnormal data in the system or application in real time, namely, fault data. This avoids the inefficient way of relying on offline verbal communication and improves the timeliness of fault discovery. And based on the captured fault data, the state of the fault at each processing stage is automatically analyzed and determined to form fault process information. This process reduces manual intervention and improves the accuracy and efficiency of data processing.

[0034] At the same time, in the fault process, when the current stage reaches the first target stage and the fault data of this stage is in the first preset state, the system automatically calculates the fault completion time of each stage. This automated process reduces errors in human judgment and data collection and improves the accuracy of operation and maintenance. The fault process information and fault completion time are input into the preset replay architecture, which can automatically generate fault result reports based on standardized data processing and analysis processes. This avoids the subjectivity of human analysis and ensures the consistency and traceability of the fault handling process.

[0035] In addition, by displaying the fault results, including fault process information and fault completion time, the operation and maintenance team can clearly understand the entire process of fault handling. This helps to achieve information sharing and collaborative work between operation and maintenance personnel of different professions and reduce communication barriers.

[0036] According to an embodiment of the present invention, an embodiment of a method for displaying fault results is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0037] In this embodiment, a method for displaying fault results is provided, which can be used in computer devices, such as computers, servers, etc. Figure 1 FIG. 1 is a flow chart of a method for displaying fault results according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0038] Step S101, acquiring fault data.

[0039] Fault data may refer to relevant data generated when a fault occurs in a device, system or process, including but not limited to error codes, log information, sensor readings, etc. Specifically, data related to the fault is collected from the device, system or process.

[0040] As an example, fault data is automatically recorded and transmitted through built-in sensors, logging systems, etc.

[0041] As one example, fault data and the like are manually recorded and entered by an operator.

[0042] Step S102, determining fault process information corresponding to the fault data according to the fault data; wherein the fault process information indicates a processing state of the fault data at each current stage.

[0043] Fault process information indicates the processing status of fault data at each current stage, that is, fault process information can characterize the processing status of each stage (such as detection, analysis, repair, etc.) in the entire process from fault data discovery to resolution. Among them, fault process information may include: the business line where the fault occurs, the application to which the fault data belongs, the person responsible for the fault data, the person who reported the fault, and determine the person in charge of each link in the fault resolution process.

[0044] As an example, if a system in the payment center business line fails, the failure process information involves the general manager of the business line confirming the fault ownership, the person responsible for the fault (may be the backend, frontend, or backend and frontend jointly) handling and solving the problem, the tester retesting the fault and returning to the core function, the product manager accepting the solution, and the fault feedback person verifying that there is no problem and closing the fault state. In this order, the fault resolution process is edited and entered in the fault review system.

[0045] Step S103: if the current stage is the first target stage, and the first processing state of the fault data corresponding to the current stage is in the first preset state, determine the fault completion time corresponding to each current stage.

[0046] The current stage can represent the stage where the fault is being processed. The current stage can be the stage where the tester is testing, or it can be the stage where the fault feedback person is verifying, etc., which is not specifically limited here. The first target stage can be used to represent the stage where the fault process is completed. The first processing state can represent the processing state of the fault data at the current stage. The first preset state can represent the state where the fault data execution at the current stage is completed. For example: the current stage is the stage where the tester is testing, the first processing state can be the state where the fault data is being tested, and the first preset state can be the state where the fault data test is fault-free.

[0047] Specifically, if the current stage is the first target stage, and the first processing state of the fault data corresponding to the current stage is in the first preset state, it indicates that the fault data is in the stage where the fault process is completed and the execution is completed, that is, the entire fault process is finished, and the fault completion time corresponding to each current stage can be determined. In other words, the time when the fault processing of each stage is finished during the flow of fault data in each stage is determined.

[0048] For example, during the troubleshooting process, if the troubleshooting process information changes, the fault system will obtain it in real time, and at the same time, improve the information of the troubleshooting timeline in the troubleshooting review. Node 1: Xiao Zhang, the person in charge of the business line, completed the confirmation of the person responsible for the bug at 2024 / 10 / 22 10:00:00; Node 2: Xiao Li, the person responsible for the system backend bug, completed the backend bug repair at 2024 / 10 / 22 10:30:00, etc.

[0049] Step S104, input the fault process information and the fault completion time into the preset replay architecture, obtain the fault result, and display the fault result.

[0050] The preset replay architecture can be set manually. Specifically, the replay architecture can be built in the system in advance, and basic information can be filled in the replay architecture. Then the fault process information and fault completion time are input into the corresponding position of the preset replay architecture to obtain the fault result. Then the fault result is displayed.

[0051] Please refer to Figure 2 , Figure 2 is a schematic diagram of a replay architecture provided according to an embodiment of the present invention. In one possible implementation, Figure 2The basic information recorded in the report may include: affected user scope, affected data scope, affected system scope, caused losses / consequences, solutions, responsible department for the fault, person responsible for the fault, person who recorded the fault, review timeline, JIRA number, fault review status, fault resolution status, fault title, fault application, person in charge of the fault, fault start time, fault troubleshooting time, impact duration, fault discovery time, fault location time, fault recovery time, fault cause, fault level, fault type and whether it has been notified.

[0052] As an example, the fault title is E-commerce platform payment system fault handling and replay report. The faulty application is the core payment system of the e-commerce platform, which is used to process user payment requests and order settlement. The fault started at 10:00 am on October 10, 2023, when the payment system began to show abnormalities. The troubleshooting time was 3:00 pm on October 10, 2023. After the technical staff repaired it, the payment system resumed normal operation. The department responsible for the fault is the technical operation and maintenance department, which is responsible for the daily maintenance and fault handling of the payment system. The person responsible for the fault is the head of the technical operation and maintenance department, who failed to discover and solve the system vulnerabilities in time, resulting in the failure of the payment system. The person who recorded the fault is Xiao Zhang from the technical support team, who is responsible for recording the entire process of the occurrence, handling and resolution of the fault. The replay timeline is within one week after the fault occurs, and the technical team is organized to conduct a replay to analyze the cause of the fault, the handling process and the improvement measures. The jira number is JIRA-12345, which is used to track and manage the related tasks of this fault handling in the Jira system.

[0053] The affected users are registered users in the North China region of the e-commerce platform. About 5 million users are affected by the payment system failure. The affected data range is the transaction data involving the payment system, including order information, payment records, etc. Some data may not be updated or queried in real time during the failure. The affected system range is the payment system of the e-commerce platform, including payment gateway, order processing, account balance management and other modules.

[0054] The loss / result is that due to the failure of the payment system, a large number of orders could not be paid, resulting in a loss of sales of about RMB M, and a decline in user experience. Some users chose to refund or switch to competitor platforms. The solution is to immediately launch the emergency plan and activate the backup payment system; organize technical personnel to troubleshoot and repair the failure; strengthen system monitoring and early warning mechanisms to prevent similar failures from happening again.

[0055] The fault replay status is completed, and the replay report has been submitted to relevant departments and leaders. The fault resolution status is resolved, the payment system has resumed normal operation, and users can perform payment operations normally.

[0056] During this period, the duration of the fault was 5 hours, which had a serious impact on the e-commerce platform. The fault discovery time was within 10 minutes after the fault occurred. Xiao Zhang from the technical support team found that the payment system was abnormal. The fault location time was 30 minutes after the technical personnel analyzed it, and it was determined that there was a problem with the payment gateway module. The fault recovery time was from fault location to complete recovery, and the entire recovery process took 2 hours. The cause of the fault was a vulnerability in the payment gateway module, which led to performance bottlenecks and crashes under high concurrency. The fault level was rated as "major" based on the scope of impact and degree of loss of the fault. The fault type is a system fault, which belongs to the scope of technical operation and maintenance. The e-commerce platform has issued fault notices and subsequent processing measures to users through official websites, social media and other channels to ensure users' right to know.

[0057] In one possible implementation, when a fault occurs, the system will automatically issue a fault notification on the work communication software to inform relevant business personnel to avoid panic. At the same time, the database updates the status of the fault notification to notified, and adds a fault notification module to the review information.

[0058] Please refer to Figure 3 , Figure 3 It is a schematic diagram of notification in the replay architecture provided according to an embodiment of the present invention.

[0059] During the fault notification process, the fault can be notified based on the fault warning title, estimated resolution time, fault description, fault level, fault cause, business impact, and recipients of the email copy.

[0060] The method for displaying fault results provided in this embodiment captures abnormal data, i.e., fault data, in the system or application in real time. This avoids the inefficient method of relying on offline verbal communication and improves the timeliness of fault discovery. In addition, based on the captured fault data, the state of the fault at each processing stage is automatically analyzed and determined to form fault process information. This process reduces manual intervention and improves the accuracy and efficiency of data processing.

[0061] At the same time, in the fault process, when the current stage reaches the first target stage and the fault data of this stage is in the first preset state, the system automatically calculates the fault completion time of each stage. This automated process reduces errors in human judgment and data collection and improves the accuracy of operation and maintenance. The fault process information and fault completion time are input into the preset replay architecture, which can automatically generate fault result reports based on standardized data processing and analysis processes. This avoids the subjectivity of human analysis and ensures the consistency and traceability of the fault handling process.

[0062] In addition, by displaying the fault results, including fault process information and fault completion time, the operation and maintenance team can clearly understand the entire process of fault handling. This helps to achieve information sharing and collaborative work between operation and maintenance personnel of different professions and reduce communication barriers.

[0063] In a possible implementation, before the above step S102, the above method further includes:

[0064] Step a1, determining the priority corresponding to the fault data, and detecting whether there is any fault data being processed in the storage queue.

[0065] After acquiring the fault data, it is necessary to determine the priority corresponding to the fault data, for example, the priority corresponding to the fault data A1 is T1, and the priority corresponding to the fault data A2 is T2. It is also necessary to detect whether there is any fault data being processed in the storage queue.

[0066] It should be noted that when there is fault data being processed in the storage queue, it is often necessary to complete the processing of the fault data being processed before subsequent fault data can be executed according to priority.

[0067] Step a2: if the storage queue does not contain the fault data being processed, and the priority corresponding to the fault data is greater than the priority of the fault data in the storage queue, a step of determining the fault process information corresponding to the fault data is performed according to the fault data.

[0068] If there is no fault data being processed in the storage queue, and the priority corresponding to the fault data is greater than the priority of the fault data in the storage queue, that is, the acquired fault data needs to be processed first, then the above step S102 can be executed. Please refer to the above step S102 for details, and no further details will be given here.

[0069] As an example, there are fault data A3, A4, and A5 in the storage queue, and the priority of the currently acquired fault data is greater than that of A3, A4, and A5, so the processing of the currently acquired fault data can be performed preferentially.

[0070] The method for displaying fault results provided in this embodiment can ensure that high-priority faults are processed first by determining the priority of fault data. This helps to quickly respond to faults of key services or important equipment and reduce the service interruption time caused by faults. In addition, when there is no fault data being processed in the storage queue, high-priority faults can immediately enter the processing flow without waiting for the processing of other low-priority faults. This reduces the waiting time for fault processing and improves the overall processing efficiency.

[0071] The method for displaying fault results provided in this embodiment can ensure that high-priority faults are processed first by determining the priority of fault data. This helps to quickly respond to faults of key services or important equipment and reduce the service interruption time caused by faults. In addition, when there is no fault data being processed in the storage queue, high-priority faults can immediately enter the processing flow without waiting for the processing of other low-priority faults. This reduces the waiting time for fault processing and improves the overall processing efficiency.

[0072] In a possible implementation, the method further includes:

[0073] Step b1, if the second processing state of the fault data of the second target stage is not in the second preset state, and the time length that the second processing state of the fault data of the second target stage is not in the second preset state is not less than the preset time length, the initial level of the second processing state of the fault data of the second target stage is raised to the target level; wherein the second target stage is any one of the stages.

[0074] Step b2: Prioritize the fault data of the second target stage according to the target level.

[0075] The second processing state can represent the state corresponding to the fault data at the second target stage. The second preset state can represent the state of the fault data after the fault processing is completed at the second target stage. In the process of fault transfer, each node of the transfer can be used as the second target stage. In the second target stage, if the second processing state of the fault data is not in the second preset state, and the duration that the second processing state of the fault data in the second target stage is not in the second preset state is not less than the preset duration (such as 5 minutes, 6 minutes, etc.), it represents that the fault data has not been processed for a long time, which may have a greater impact on the entire system, then it is necessary to upgrade the level of the fault data, that is, to upgrade the initial level of the second processing state of the fault data in the second target stage to the target level. For example: upgrade the initial level Y1 to the target level Y2.

[0076] Please refer to Figure 4 , Figure 4 It is a schematic diagram of the review progress timeline in the review architecture provided according to an embodiment of the present invention. In a possible implementation, the review progress timeline may include: the start time of the fault, the end time of the fault, the status of each stage (node ​​status), the fault work content corresponding to each node, and the person in charge of the work content. When the fault is not repaired at the node for a certain period of time (such as 5 minutes) and cannot be resolved, the upgraded level is determined based on the initial value of the affected unit, the current value of the affected unit, the impact on the business or other factors, and then the fault is upgraded.

[0077] In the method for displaying fault results provided in this embodiment, when the fault data of a certain stage fails to reach the preset processing state for a long time, it indicates that the fault may be more complicated or have a greater impact. By improving the processing level of these fault data, it can be ensured that they are responded to and processed faster, thereby shortening the fault recovery time.

[0078] At the same time, by giving priority to handling critical faults, problems in the system can be resolved more quickly, reducing business interruption time caused by faults, thereby improving overall operation and maintenance efficiency.

[0079] In a possible implementation, the displaying of the fault result in the above step S104 includes: generating a copy document corresponding to the fault result according to the fault result and a preset copy template, and displaying the copy document.

[0080] After the fault is resolved, the system can automatically issue a notification that the fault has been resolved according to the copy template to avoid adverse effects caused by the continued fermentation of the incident. Specifically, detailed fault information can be collected from the fault handling results, including the time of fault occurrence, scope of impact, affected system, loss caused, solution, etc. And collect other data related to the fault, such as fault discovery time, fault location time, fault recovery time, fault cause, fault level, fault type, etc. Select a template suitable for the current fault situation from the preset copy templates. Make sure that the template contains key parts such as fault notification, handling results, follow-up measures, contact information, etc. Based on the collected fault information, fill in key details such as the time of fault occurrence, scope of impact, affected system, etc., and describe the fault discovery, location, recovery process, and solutions taken.

[0081] As an example, the failure notification and handling result announcement: To: Dear e-commerce platform users; Subject: E-commerce platform payment system failure handling and notification; Dear e-commerce platform users: Recently, we encountered a major failure in the e-commerce platform payment system, which has brought inconvenience to your shopping experience. We are deeply sorry for this. The failure situation, handling results and subsequent measures are now reported as follows:

[0082] 1. Fault condition:

[0083] Time of failure: 10:00 am on October 10, 2023.

[0084] Scope of impact of the failure: Approximately 5 million registered users in North China were affected by the payment system failure.

[0085] Systems affected by the failure: The payment system of the e-commerce platform, including payment gateway, order processing, account balance management and other modules.

[0086] Result of the failure: Due to the failure of the payment system, a large number of orders could not be paid, resulting in a loss of approximately RMB M million in sales, and some user experiences were affected.

[0087] 2. Processing results:

[0088] Discovery time: Within 10 minutes after the failure occurred, our technical support team quickly discovered the anomaly in the payment system.

[0089] Location time: After analysis by technical personnel, it was determined within 30 minutes that a vulnerability in the payment gateway module was the main cause of the failure.

[0090] Recovery time: From fault location to full recovery, the entire recovery process took 2 hours, and the payment system resumed normal operation at 3 pm on October 10, 2023.

[0091] Solution: We immediately launched an emergency plan, enabled a backup payment system, and organized technical personnel to fix the vulnerability. At the same time, we strengthened system monitoring and early warning mechanisms to prevent similar failures from happening again.

[0092] In a possible implementation, the document may be sent to each technician corresponding to the fault so that each technician can understand the fault at any time.

[0093] The method for displaying fault results provided in this embodiment can automatically fill the fault results into the template through the preset copy template to generate a complete copy document. This process does not require manual intervention, which greatly improves the efficiency of document generation. In addition, the preset copy template usually contains standardized formats and styles, such as the title, body, conclusion and other parts. By using this template, it can be ensured that the generated copy document has a consistent format and style, improving the readability and professionalism of the document.

[0094] In a possible implementation, the method further includes: generating a replay document corresponding to the fault result according to the fault result, and sending the replay document to a user corresponding to the fault process information.

[0095] After the fault is resolved, a replay document for the fault can be automatically generated based on all the replay information, including: basic replay information, fault escalation records, fault notification information, fault replay timeline, etc., and sent to the user (such as: relevant responsible persons and leaders are informed).

[0096] The display method of the fault result provided in this embodiment records the discovery, handling process, handling results and lessons learned of the fault in detail in the replay document, which helps the user to fully understand the fault situation. At the same time, by sending the replay document to the user, the user can timely understand the progress and results of the fault handling.

[0097] In a possible implementation, when there are multiple types of fault data, the method further includes:

[0098] Step c1, obtaining fault data associated with the fault data.

[0099] The associated fault data can characterize other fault data associated with the current fault data, and these associations may be based on time sequence, causal relationship, system component relationship, etc. Get other fault data associated with the current fault data. This can be achieved by analyzing the attributes of the fault data (such as timestamp, system component, fault type, etc.) to find other records related to the current fault data.

[0100] As an example, through SQL query or NoSQL query, related records are matched according to the attributes of the fault data, and rules can also be defined to identify related fault data, such as matching based on time windows, matching based on system components, etc.

[0101] Step c2: determining the fault process information corresponding to the associated fault data according to the associated fault data.

[0102] Based on the associated fault data, determine the various stages and states of the associated fault data in the fault process. This may require reference to the definition of the fault handling process, as well as the corresponding processing states and conditions at each stage.

[0103] As an example, a state machine can be used to describe the fault handling process, where each state corresponds to a processing stage and the transitions between states represent the progress of the processing process. A workflow engine or business process management system can also be used to manage and track the fault handling process.

[0104] Step c3, if the stage corresponding to the associated fault data is the third target stage, the third processing state corresponding to the third target stage is in the third preset state, the current stage is the first target stage, and the first processing state of the fault data corresponding to the current stage is in the first preset state, the current state of the updated fault data is the resolved state.

[0105] When certain conditions are met, the status of the current fault data is updated to the resolved status. These conditions include: the associated fault data reaches the third target stage and is in the third preset state (such as "repaired" or "verified"), and the current fault data is in the first target stage and is in the first preset state (such as "pending" or "processing"). That is, when the fault data and the associated fault data are both executed, the current status of the updated fault data is resolved.

[0106] The method for displaying fault results provided in this embodiment can perform a more comprehensive and in-depth analysis of faults by obtaining associated fault data. This helps to discover potential connections and common causes between faults, thereby formulating more effective solutions. At the same time, when processing multiple types of fault data, it is easy to overlook certain related faults. Through association analysis, it can be ensured that all related faults are properly handled to avoid omissions.

[0107] Please refer to Figure 5 , Figure 5 is a schematic diagram of a method for displaying fault results provided according to an embodiment of the present invention.

[0108] Create a fault replay and fill in the basic information of the replay attributes.

[0109] Record the fault resolution process. That is, after a fault occurs, determine the person in charge of each link in the fault resolution process through the business line where the fault occurs, the application to which it belongs, the person responsible for the specific bug, and the person who reported the fault.

[0110] For example, if a bug occurs in a system of the payment center business line, the troubleshooting process will involve the general manager of the business line confirming the ownership of the bug, the person responsible for the bug (may be the backend, frontend, or backend and frontend jointly) handling the problem, the tester retesting the bug and returning to the core function, the product manager accepting the solution, and the bug feedback person verifying that there is no problem and closing the bug status. In this order, edit and enter the troubleshooting process in the troubleshooting review system in turn, and associate the corresponding jira link;

[0111] Fault notification: When a fault occurs, the system will automatically issue a fault notification on the work communication software to inform relevant business personnel to avoid panic. At the same time, the database updates the status of the fault notification to notified, and adds a fault notification module to the review information.

[0112] Connect to jira to synchronize data in real time and determine whether the bug has been resolved. That is, after the process is generated, the system will automatically read the relevant bug status on jira at a fixed time to determine whether the fault has been resolved.

[0113] Specifically: When the fault is not resolved, you can use the following:

[0114] 1) One-click urging of fault resolution: If the bug is not resolved, you can urge it with one click on the system, and a reminder will be sent to the person responsible for the current link.

[0115] 2) Fault escalation: The fault escalation function can be used to escalate the fault to the target level and send notifications to relevant responsible persons and the general manager of the business line. By increasing the severity of the fault and raising the priority of fault resolution, the fault can be brought to the attention of relevant responsible persons.

[0116] Update the fault status after the fault is resolved: Only when all related bugs are resolved, the fault status will be updated to resolved. During this process, the system will update the fault status data in real time according to the obtained bug status; determine the next step of code logic based on the bug status obtained each time;

[0117] Complete the review information and generate a complete review timeline.

[0118] During the troubleshooting process, if the bug information on Jira changes, the fault system will obtain it in real time, and at the same time improve the information of the troubleshooting timeline in the troubleshooting review, such as:

[0119] Node 1: Xiao Zhang, the person in charge of the business line, completed the bug responsibility confirmation at 10:00:00 on 2024 / 10 / 22;

[0120] Node 2: Xiao Li, the person responsible for the system backend bug, completed the backend bug fixes at 2024 / 10 / 22 10:30:00.

[0121] This process continues until the last link in the process, when the bug reporter verifies that the bug has been resolved and confirms that there are no other abnormalities through observation, and closes the bug, thus forming a closed loop. The timeline is automatically generated, and the action of creating a replay is automatically added, so that a complete fault replay timeline is generated.

[0122] Fault notification: After the fault is resolved, the system automatically sends a notification that the fault has been resolved according to the copy template to avoid the adverse effects caused by the continued fermentation of the incident.

[0123] Automatically generate review documents: After the fault is resolved, the background will automatically generate a review document for the fault based on all the review information, including: basic review information, fault escalation records, fault notification information, fault review timeline, etc., and send it to relevant responsible persons and leaders for their information.

[0124] Update fault overview statistics and refresh bug carousel data: After the fault is resolved, the background will automatically update the fault-related data. By obtaining the latest JIRA data, the reports and charts on different statistical dimensions of the fault on the system homepage, as well as the real-time bug carousel display data, will be refreshed in real time.

[0125] The following example explains this in detail:

[0126] System A of the payment center business line has an online fault. Through communication, the complete list of personnel who solved the fault and the sequential processing process are confirmed. The relevant jira bugs corresponding to each link are entered into the fault system. According to the process, the system reads the bug resolution status regularly: if the bug is not resolved, you can choose to upgrade the fault or urge the fault with one click, and the person in charge of the corresponding link will receive a notification; if the bug has been resolved, the fault status is updated to a certain intermediate state, and a timeline for fault replay and resolution is generated at the same time, until all bugs are resolved, the fault status is resolved, and a complete replay timeline is generated. After the fault is resolved, a fault notification is automatically sent, a notification email is sent, and fault statistics (business line statistics) are updated. System users can view the details of all faults and leave messages in the discussion area to facilitate communication of faults and fault resolution ideas. Therefore, all information about an online fault, the basic information, cause, solution, resolution process, etc. can be viewed on the fault replay system, which can also serve as a reference and warning for each other.

[0127] In this embodiment, a display device for fault results is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0128] This embodiment provides a display device for fault results, such as Figure 6 As shown, it includes: an acquisition module 601, used to acquire fault data; a first determination module 602, used to determine the fault process information corresponding to the fault data according to the fault data; wherein the fault process information indicates the processing status of the fault data in each current stage; a second determination module 603, used to determine the fault completion time corresponding to each current stage if the current stage is the first target stage, and the first processing status of the fault data corresponding to the current stage is in the first preset state; a determination display module 604, used to input the fault process information and the fault completion time into the preset replay architecture, obtain the fault result, and display the fault result.

[0129] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0130] The display device of the fault result in this embodiment is presented in the form of a functional unit, where the functional unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0131] The embodiment of the present invention also provides a computer device having the above Figure 6 Display device showing the fault result.

[0132] See also Figure 7 , Figure 7 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 7 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.

[0133] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0134] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0135] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0136] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0137] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0138] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0139] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0140] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for displaying fault results, characterized in that: The method comprises: Get fault data; Determine the fault process information corresponding to the fault data according to the fault data; wherein the fault process information indicates the processing status of the fault data at each current stage; If the current stage is the first target stage, and the first processing state of the fault data corresponding to the current stage is in the first preset state, determining the fault completion time corresponding to each current stage; The fault process information and the fault completion time are input into a preset replay architecture to obtain a fault result, and the fault result is displayed.

2. The method for displaying fault results according to claim 1, characterized in that: Before determining the fault process information corresponding to the fault data according to the fault data, the method further includes: Determine the priority corresponding to the fault data, and detect whether there is any fault data being processed in the storage queue; If the storage queue does not contain any fault data being processed, and the priority corresponding to the fault data is greater than the priority of the fault data in the storage queue, a step of determining fault process information corresponding to the fault data according to the fault data is performed.

3. The method for displaying fault results according to claim 1, characterized in that: The method further comprises: If the second processing state of the fault data of the second target stage is not in the second preset state, and the duration for which the second processing state of the fault data of the second target stage is not in the second preset state is not less than the preset duration, the initial level of the second processing state of the fault data of the second target stage is raised to the target level; wherein the second target stage is any one of the stages; According to the target level, the fault data of the second target stage is processed preferentially.

4. The method for displaying fault results according to claim 1, characterized in that: The displaying of the fault result includes: Generate a copy document corresponding to the fault result according to the fault result and a preset copy template, and display the copy document.

5. The method for displaying fault results according to claim 1, characterized in that: The method further comprises: According to the failure result, a replay document corresponding to the failure result is generated, and the replay document is sent to the user corresponding to the failure process information.

6. The method for displaying fault results according to claim 1, characterized in that: When there are multiple types of fault data, the method further includes: Acquire fault data associated with the fault data; Determine the fault process information corresponding to the associated fault data according to the associated fault data; If the stage corresponding to the associated fault data is the third target stage, the third processing state corresponding to the third target stage is in the third preset state, the current stage is the first target stage, and the first processing state of the fault data corresponding to the current stage is in the first preset state, the current state of the fault data is updated to the resolved state.

7. A display device for fault results, characterized in that: The device comprises: An acquisition module, used for acquiring fault data; A first determination module is used to determine the fault process information corresponding to the fault data according to the fault data; wherein the fault process information indicates the processing status of the fault data at each current stage; A second determination module, configured to determine a fault completion time corresponding to each current stage if the current stage is the first target stage and the first processing state of the fault data corresponding to the current stage is in the first preset state; A display module is determined, which is used to input the fault process information and the fault completion time into a preset replay architecture, obtain a fault result, and display the fault result.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for displaying fault results according to any one of claims 1 to 6 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for displaying fault results according to any one of claims 1 to 6.

10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the method for displaying the fault result according to any one of claims 1 to 6.

Images