System fault feedback method, device and computer readable storage medium
By collecting and uploading fault site data, fault reproducing and type determination are carried out, and the corresponding subprocess processing is entered, the problem of inaccurate data in traditional fault feedback methods is solved, fast and efficient fault location and processing is achieved, and operation and maintenance efficiency is improved .
Patent Information
- Application Number
- CN202411118351.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-15
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-08-15
AI Technical Summary
Traditional system fault feedback methods rely on the memory and feelings of the parties involved, and cannot accurately reflect the fault site data, resulting in the R&D analysts needing to spend a lot of energy and time to conduct offline, discrete and fragmented fault analysis.
When the fault notification function is detected, the system fault site data is collected and the fault work ticket is submitted to the centralized work ticket system, the fault site data is packaged and uploaded, and the fault reproducibility and type determination are carried out based on the centralized work ticket system. The corresponding subprocess is processed, and the faulty work order is brought into the feedback process after the subprocess verification is completed.
It has realized the full process of solving the faults of the e-government software system online, helping R&D operation and maintenance personnel to quickly and efficiently locate the faults of the system, and improve work efficiency.
Smart Images

Figure CN118642882B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of system maintenance, and in particular to a system fault feedback method, device and computer-readable storage medium. Background Art
[0002] In the traditional operation and maintenance process, the parties usually report the fault to the application operation and maintenance personnel through screenshots or offline verbal methods. The application operation and maintenance personnel then collect quasi-on-site data information offline, make a preliminary and simple judgment on whether it is a complex operation and maintenance problem, and then report it to the corresponding professional operation and maintenance personnel for processing.
[0003] However, the above fault feedback methods only rely on the memory and feeling of the parties involved in the system fault feedback, which cannot accurately reflect the actual fault site data at the time. This means that research and operation analysts can only analyze faults through offline, discrete, fragmented, and historical on-site information, which consumes a lot of energy and time to solve the faults.
[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention
[0005] The main purpose of the present invention is to provide a system fault feedback method, device and computer-readable storage medium, aiming to solve the current fault feedback method, in which the feedback on system faults is based solely on the memory and feeling of the parties involved, and cannot actually and accurately reflect the fault site data at the time, so that research and operation analysts need to spend a lot of energy and time to solve the technical problems of the fault.
[0006] To achieve the above object, the present invention provides a system fault feedback method, which comprises the following steps:
[0007] When the fault reporting function is detected to be triggered, the fault site data of the system is collected and the fault work order is submitted to the centralized work order system;
[0008] Packing the fault site data as a work order attachment of the fault work order and uploading it to the centralized work order system;
[0009] Based on the centralized work order system, reproduce the fault and determine the fault type according to the fault work order and the work order attachments;
[0010] Based on the fault type, enter the corresponding sub-process for processing, and after the sub-process verification is completed, the fault work order is submitted to the feedback process.
[0011] Optionally, the step of collecting the fault site data of the system and submitting the fault work order to the centralized work order system includes:
[0012] A collection tool based on the front-end collection system collects front-end fault site data of the client of the system;
[0013] Sending instruction parameters to the back-end acquisition system based on the front-end acquisition system;
[0014] Based on the back-end acquisition system, the instruction parameters are transmitted to the application program interface of the management system to collect the back-end fault site data;
[0015] According to the fault page corresponding to the triggering of the fault reporting function, the fault work order is generated and submitted to the centralized work order system.
[0016] Optionally, the step of packaging the fault site data as a work order attachment of the fault work order and uploading it to the centralized work order system includes:
[0017] According to the fault information of the fault scene data, a corresponding application program interface and a fault management function are added to the fault scene data;
[0018] Packing the fault site data, the application program interface and the fault management function to generate the work order attachment;
[0019] Upload the work order attachment to the centralized work order system.
[0020] Optionally, the step of reproducing the fault and determining the fault type based on the centralized work order system and the fault work order and the work order attachments includes:
[0021] Parsing the work order attachment, and establishing a corresponding test environment according to the fault work order and the work order attachment;
[0022] Based on the test environment and the fault data in the work order attachment, simulate the fault site;
[0023] The fault type is determined according to the phenomena exhibited at the fault site.
[0024] Optionally, the step of entering a corresponding sub-process for processing based on the fault type includes:
[0025] If the fault type is an occasional fault, enter the occasional fault sub-process and perform fault analysis on the occasional fault;
[0026] Based on the analysis results of the fault analysis and the solution developed by the operation and maintenance personnel, correct the client or server configuration;
[0027] If the fault type is a secondary fault, determine whether the secondary fault is a complex secondary fault, and enter the sub-process of the corresponding processing personnel according to the determination result, so that the processing personnel can perform operation and maintenance on the secondary fault.
[0028] Optionally, before the step of entering a corresponding sub-process for processing based on the fault type, the method further includes:
[0029] Based on the fault type, determine the corresponding processing requirements and processing personnel;
[0030] According to the processing requirements and processing personnel, based on the unified process engine, a gate access to the sub-process is set, and the gate access is used for personnel verification.
[0031] Optionally, the step of submitting the fault work order to the feedback process after the sub-process verification is completed includes:
[0032] After the sub-process is verified by the processing personnel corresponding to the access control, the fault work order is returned to the application operation and maintenance personnel of the centralized work order system;
[0033] After detecting that the application operation and maintenance personnel have verified the sub-process and the system fault has been eliminated, the fault work order is submitted to the feedback process.
[0034] Optionally, after the step of entering a corresponding sub-process for processing based on the fault type and submitting the fault work order to a feedback process after the sub-process verification is completed, the process further includes:
[0035] Based on the centralized work order system, closing the fault work order and generating an evaluation questionnaire;
[0036] Sending the evaluation questionnaire to the system;
[0037] Based on the content written in the evaluation questionnaire, the system configuration is updated or upgraded.
[0038] In addition, to achieve the above-mentioned purpose, the present invention also provides a system fault feedback device, which includes: a memory, a processor, and a system fault feedback program stored in the memory and executable on the processor, and the system fault feedback program is configured to implement the steps of the system fault feedback method as described above.
[0039] In addition, to achieve the above-mentioned purpose, the present invention also provides a computer-readable storage medium, on which a system fault feedback program is stored, and when the system fault feedback program is executed by a processor, the steps of the system fault feedback method as described above are implemented.
[0040] The embodiment of the present invention provides a system fault feedback method. When it is detected that the fault reporting function is triggered, the fault site data of the system is collected and the fault work order is submitted to the centralized work order system. The collected fault site data is packaged as a work order attachment of the fault work order and uploaded to the centralized work order system at the same time. Based on the centralized work order system, the fault is reproduced and the fault type is determined according to the fault work order and the work order attachment. Then, according to the fault type, the corresponding sub-process is entered for processing, and after the sub-process verification is completed, the fault work order is submitted to the feedback process so that the corresponding R&D and operation and maintenance personnel can analyze and process it. Through the above method, the faults of the e-government software system can be solved online throughout the entire process, helping R&D and operation and maintenance personnel to quickly and efficiently locate system faults and improve work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] Figure 1 It is a flowchart of the first embodiment of the system fault feedback method of the present invention;
[0042] Figure 2 It is a flow chart of the second embodiment of the system fault feedback method of the present invention;
[0043] Figure 3 It is a flow chart of the third embodiment of the system fault feedback method of the present invention;
[0044] Figure 4 It is a schematic diagram of the overall execution flow of the system fault feedback method of the present invention;
[0045] Figure 5 It is a schematic diagram of the terminal structure of the hardware operating environment involved in the embodiment of the present invention.
[0046] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0047] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.
[0048] The embodiment of the present invention provides a system fault feedback method, referring to Figure 1 , Figure 1 The figure is a flow chart of a first embodiment of a method for system fault feedback according to the present invention.
[0049] In this embodiment, the system fault feedback method includes:
[0050] Step S10: When it is detected that the fault reporting function is triggered, the fault site data of the system is collected and the fault work order is submitted to the centralized work order system.
[0051] In this embodiment, when a party encounters a fault while using the E-government Software Application System (EgSAS for short), the party can trigger the one-click fault reporting function through the ASBCS (a system that automatically collects / collects EgSAS system fault bugs) front-end system on the fault page of the EgSAS system. When the ASBCS system detects that the fault reporting function is triggered, it further submits a fault ticket to the ITS (Issue Tracking System, centralized work order system). ITS can centrally collect and distribute fault tickets of the EgSAS system. Before submitting the fault ticket, the one-click fault reporting function of the ASBCS front-end system will also trigger a collection event. The ASBCS front-end collection system is responsible for collecting the client's fault site data information, such as: taking screenshots of the fault application page, collecting client terminal information, collecting browser terminal information, etc. Reference Figure 4 The ASBCS front-end collection system collects the client's fault site data information by calling the computer's local screenshot tool or the built-in screenshot tool, browser plug-in, and front-end collection system (installation is required for the first visit). In addition, the ASBCS front-end collection system will also send the command parameters that need to collect back-end information to the ASBCS back-end collection system. The ASBCS back-end collection system, based on the received command parameters, passes them to the API interface of AOM (application operation and maintenance management system) and APM (application performance management system) to obtain the corresponding back-end data information of the fault site.
[0052] Furthermore, in the process of the ASBCS front-end acquisition system collecting the client's fault site data information, it can be divided into two steps: front-end fault data collection and back-end fault data collection. In the process of collecting front-end data, the local screenshot tool of the computer (such as the Snipping Tool that comes with Windows or the screenshot tool of macOS) can be called to realize the screenshot of the client's fault site to capture the error information displayed by the client, page layout problems, etc. In addition, the ASBCS front-end acquisition system provides a browser plug-in, which users can install into their browsers. The plug-in helps users capture screenshots of web pages, record page interaction data, etc. for subsequent analysis and troubleshooting. When visiting for the first time, users may need to install the client components of the front-end acquisition system to ensure that the system can accurately collect the client's fault site data information. These components include necessary data acquisition modules, code injection tools, etc. to realize data collection and transmission.
[0053] Reference Figure 4, during the collection of backend fault data, after identifying the client fault, the ASBCS front-end collection system sends the instruction parameters for collecting backend information to the ASBCS back-end collection system. These instruction parameters include information such as the type of data to be collected, the data range, and the collection method. After receiving the instruction parameters, the ASBCS back-end collection system calls the API interfaces of AOM and APM according to the parameter content, passes in the instruction parameters and requests to obtain the back-end data information of the corresponding fault site. Data related to application operation and maintenance, such as server logs and database query results, can be obtained through the AOM API interface. Data related to application performance, such as code execution time and resource utilization, can be obtained through the APM API interface. After completing the above steps, the corresponding fault work order will be generated and submitted to ITS, and the collected fault data will be uploaded to the ITS system as a work order attachment of the fault work order in the subsequent process.
[0054] In this embodiment, through the above process, the ASBCS front-end acquisition system and the back-end acquisition system can realize the transmission of instruction parameters and the acquisition of back-end data, so as to comprehensively collect and process the client fault site data information.
[0055] Step S20: Packing the fault site data into a work order attachment of the fault work order, and uploading it to the centralized work order system;
[0056] In this embodiment, refer to Figure 4 The ASBCS management system is responsible for aggregating the front-end and back-end fault site data information collected by the collection system and packaging it into the attachment form required by the ITS system, and providing it with API and related management functions. After packaging, the ASBCS management system automatically saves the packaged files as work order attachments and reports them to the ITS system.
[0057] Furthermore, in the process of integrating and packaging the front-end and back-end fault site data information and automatically reporting it to the ITS system, the ASBCS management system receives the fault site data information from the front-end acquisition system and the back-end acquisition system. The system is responsible for aggregating, integrating and packaging these data, and ensures that the attachment format meets the requirements of the ITS system through operations such as data number conversion, data screening, and correlation analysis. Subsequently, the ASBCS management system provides the corresponding API interface for data interaction with the ITS system. First of all, this requires clarifying the data interaction requirements between the ASBCS management system and the ITS system, including the data type, data format, and transmission frequency to be transmitted. According to the results of the demand analysis, the URL (Uniform Resource Location) path, request method, request parameters, and response format of the API interface are designed, and the functions and effects of each interface are defined, including data upload, query, update, and other operations. Finally, the corresponding programming language and framework are used to implement the specific API interface according to the interface design. Optionally, security mechanisms such as identity authentication and permission control can also be added to the API interface to protect the security and integrity of the data. Here, API keys, tokens, etc. can be used for identity authentication and to limit the access rights of the interface.
[0058] In addition, the ASBCS management system also provides relevant management functions, including fault handling progress management, data statistics reports, user authority management, system log management and other functions, so that subsequent R&D and operation and maintenance personnel can view data processing, monitor system status, configure parameters, etc. through the management interface. Among them, the fault handling progress management can view the processing progress of each fault, including fault status, responsible person, processing time and other information, and can be modified and updated. The data statistics report can generate fault statistics reports based on time, equipment, fault type and other conditions, which is convenient for administrators to manage and analyze faults. User authority management supports administrators to set different permissions for different users to ensure that sensitive data can only be accessed by authorized personnel. The system log management is used to record the operation records of the system so that administrators can view the use of the system at any time to prevent security problems. Once the data is packaged, the ASBCS management system will automatically report the packaged files to the ITS system as work order attachments. This process realizes automated operation through pre-set rules and processes to reduce manual intervention.
[0059] In this embodiment, the collected fault site data is packaged, an API and corresponding management functions are added to it, and it is submitted to the ITS system as an attachment file of the previously submitted fault work order. This simplifies the way in which R&D and operation personnel obtain system fault data, making it easier for subsequent R&D and operation personnel to further analyze and process it.
[0060] Step S30: Based on the centralized work order system, reproduce the fault and determine the fault type according to the fault work order and the work order attachments.
[0061] In this embodiment, refer to Figure 4 After the application operation and maintenance personnel receive the work order with fault site data information reported by the ASBCS management system based on the ITS system, they can reproduce the fault and determine the fault type according to the fault work order and work order attachments. Here we divide the fault types into occasional faults (abbreviated as OD) and secondary faults (SD). OD refers to a non-reproducible fault, and SD refers to a reproducible fault.
[0062] Furthermore, when using reproduction technology to reproduce the fault based on the fault ticket and the fault site data, first obtain the fault description, occurrence time, related equipment information and other detailed contents contained in the fault ticket, and collect the field data related to the fault based on the information provided by the fault ticket, including log records, system status information, equipment data, etc. In a test environment similar to the production environment, restore the state when the fault occurred as much as possible, including relevant software versions, configuration information, network environment, etc. In the established test environment, try to simulate and reproduce the fault according to the situation described by the fault ticket and the field data. You can try to trigger the situation where the fault occurs by operating the equipment, adjusting the system parameters, etc. By recording the various operations and observed phenomena during the reproduction process, compare the fault manifestations described in the fault ticket, so as to carry out the next step of analyzing the fault type.
[0063] Next, we need to determine whether the fault is an occasional fault or a secondary fault. We can determine it by the performance characteristics of the fault. An occasional fault is mostly caused by some accidental factors. If the recurring fault is irregular and unpredictable, and it may not occur again under the same conditions, it can be determined as an occasional fault. A secondary fault is a secondary fault caused by other faults or problems that occurred before. It is manifested as a reproducible fault or a new fault or problem after solving a fault. As a feasible implementation method, the judgment of whether the fault is an occasional fault or a secondary fault can be determined by analyzing the fault frequency and the fault impact range log records. If the fault occurs less frequently and has no obvious regularity, it is an occasional fault. If the fault occurs or can be reproduced after solving other problems, it is a secondary fault. Analyze the impact range of the fault on the system. If the fault only occurs under a specific condition and has limited impact, it is an occasional fault. If the fault involves multiple system components or functions, it is a secondary fault. When checking the system log records, analyze the causes and consequences of the fault, and whether there are records of previous faults or abnormal conditions. If there are obvious precursors or warning information, it is a secondary failure. If it does not meet the above performance characteristics, it is determined to be an accidental failure.
[0064] Optionally, in a feasible implementation, during the process of reproducing the fault and determining the fault type, the R&D and operation and maintenance personnel can trigger the reproduction process by themselves. After each reproduction step is completed, such as the test environment is matched, the fault is reproduced in the test environment, and the fault type is determined according to the fault manifestation characteristics, etc., a corresponding confirmation page is generated on the ITS system interface. After confirming that everything is correct, the R&D and operation and maintenance personnel will proceed to the next step to ensure the accuracy of the fault reproduction. In another feasible implementation, a series of fault reproduction and determination steps can be directly completed with the authorization of the R&D and operation and maintenance personnel, and the final determination result can be presented on the system interface.
[0065] In this embodiment, through the above analysis, it is possible to better determine whether the fault is an accidental fault or a secondary fault, providing strong support for fault troubleshooting and repair, so that targeted solutions can be taken later and similar faults can be avoided from happening again.
[0066] Step S40: Based on the fault type, enter the corresponding sub-process for processing, and after the sub-process verification is completed, submit the fault work order to the feedback process.
[0067] In this embodiment, refer to Figure 4, by reproducing the fault, determining the fault type, and entering the corresponding sub-process for processing according to the fault type, that is, the corresponding R&D operation and maintenance personnel will process and verify it, and submit the fault ticket to the feedback process after the process verification is completed. The sub-processes that the ticket enters are different for different fault types and complex types of faults. If the fault type is determined to be OD, it will enter the OD processing sub-process. Subsequently, according to the actual processing of OD and the solutions that the operation and maintenance personnel may formulate, the client or server configuration will be corrected (for example: this OD only reproduces under a specific browser or version), entered into the knowledge base, and the implementation deployment manual will be upgraded. If the fault type is determined to be SD, it is necessary to further determine whether it is a complex SD through the application operation and maintenance personnel. If it is a simple SD, it will enter the simple operation and maintenance sub-process and be processed by professional operation and maintenance personnel. If it is a complex SD, the work order needs to be transferred to the operation and maintenance team leader for processing. The operation and maintenance team leader will work with the R&D team leader to convert the complex SD into a R&D BUG according to the situation. At the same time, this work order is also transferred to the DevOps system (integrated R&D operation management platform), thereby transferring the fault work order to the R&D fault processing sub-process.
[0068] Whether it is OD, complex SD or simple SD, it must enter the corresponding sub-process processing. In a feasible implementation method, the access control before entering each sub-process can also be set on the BPE (unified process engine) system according to actual needs. After the sub-process is processed and verified by the corresponding R&D operation and maintenance personnel, the process will be returned to the application operation and maintenance personnel in the ITS system. After the final verification by the application operation and maintenance personnel, if the fault is eliminated, the fault work order will enter the feedback process, that is, the application operation and maintenance personnel will feedback the work order status to the client in the ITS system and remind the person concerned to verify. If the person concerned passes the verification, the process ends. The ITS system automatically closes the work order, and DevOps (integrated research and operation management platform) automatically closes the R&D BUG.
[0069] In this embodiment, by determining the fault type and transferring the fault work order to the corresponding sub-process according to the fault type, it can assist the parties to quickly and accurately feedback the fault of the EgSAS system, and assist the research and operation analysts to quickly and efficiently locate and solve the fault bug of EgSAS, making the processing sub-process flow smoother and more efficient, while also reducing the buck-passing between departments or groups.
[0070] Further, see Figure 2 , the second embodiment of the system fault feedback method of the present invention, based on the above Figure 1 In the embodiment shown, before step S40, the following steps are also included:
[0071] Step S50: Determine corresponding processing requirements and processing personnel based on the fault type.
[0072] Step S60: according to the processing requirements and processing personnel, based on the unified process engine, set the access control for entering the sub-process, and the access control is used for personnel verification.
[0073] In this embodiment, since different fault types need to flow into different sub-processes and be handled by corresponding R&D and operation personnel, it is very important to ensure that the sub-processes are assigned to appropriate processing personnel. Figure 4 We determine the corresponding processing requirements and processing personnel in advance according to the fault type. Once the processing requirements and processing personnel are determined, we can set up access control to the sub-process in the unified process engine (BPE system) to verify the personnel in the sub-process.
[0074] Furthermore, to determine the corresponding processing requirements and processing personnel based on the fault type, it is necessary to first define the characteristics and processing requirements of different fault types, such as what specific operations or processes are required to solve this type of fault, specify the processing personnel or processing team, and determine who is responsible for handling each type of fault, including professional operation and maintenance personnel, operation and maintenance team leaders, R&D team leaders, etc. Subsequently, a mapping relationship table or configuration file is established to associate the fault type with the processing requirements and processing personnel, which can be managed by means of a database or configuration file. In the system, a rule engine or logic control module is implemented based on the defined fault type, processing requirements and processing personnel information. When a fault is identified as a specific type, the system will automatically determine the corresponding processing requirements and processing personnel based on the mapping relationship, and trigger the corresponding processing flow with the help of the trigger mechanism set in the system so that it can be assigned to the correct processing personnel or processing team.
[0075] Furthermore, define the access control conditions for entering the sub-process. The conditions can be determined based on factors such as the fault type, processing requirements, and the authority of the processing personnel. In the unified process engine, configure the corresponding access control rules according to the defined access control conditions. These rules can be configured based on conditional expressions, scripts, or business rules. When a fault process triggers the entry into the sub-process, the unified process engine automatically performs access control verification. The engine checks the characteristics and context information of the current fault, and determines whether the conditions for entering the sub-process are met based on the access control rules. If the fault meets the access control conditions for entering the sub-process, the process engine will allow entry into the sub-process and continue to perform subsequent operations. If the fault does not meet the access control conditions, the process engine will handle it according to the preset strategy, such as returning an error message, transferring it to other processing personnel, or executing other process paths. In order to ensure the compliance of the process, the transparency and traceability of the processing process, the unified process engine should also record the results of the access control verification and the processing process for subsequent auditing and tracking.
[0076] In this embodiment, corresponding authority restrictions are set according to different processing requirements and roles of processing personnel to ensure that only personnel with corresponding authority can perform specific operations, thereby ensuring the compliance and correctness of the process for future tracking or review.
[0077] Reference Figure 3 , the third embodiment of the system fault feedback method of the present invention, based on the above Figure 1 In the embodiment shown, after step S40, the following steps are also included:
[0078] Step S70: Based on the centralized work order system, close the fault work order and generate an evaluation questionnaire.
[0079] Step S80: Send the evaluation questionnaire to the system.
[0080] Step S90: updating or upgrading the system configuration based on the content written in the evaluation questionnaire.
[0081] In this embodiment, refer to Figure 4 After the fault ticket enters the feedback process, it means that the current fault has been operated and maintained. When the ITS system closes the ticket, it will generate and send a satisfaction evaluation of the ticket to the client system. After the evaluation, the evaluation will be entered into the ITS system for service satisfaction evaluation analysis. According to the content written in the evaluation questionnaire, the system needs to be updated later, the configuration / deployment implementation manual / operation and maintenance knowledge base needs to be upgraded, and the organizational assets need to be updated to make the organization run more efficiently.
[0082] Furthermore, in a feasible implementation, based on the centralized work order system, a fault work order is closed, an evaluation questionnaire is generated, the questionnaire is sent, and the system configuration is updated according to the feedback. At the same time as the fault work order is closed, an evaluation questionnaire can be automatically generated, including evaluation items, scoring methods, etc. The questionnaire can cover the user's evaluation of service quality, processing efficiency, etc. The centralized work order system can send the evaluation questionnaire to relevant users or customers through the built-in email notification or message push function. Ensure that the questionnaire can be delivered accurately and convenient for users to fill in. By timely collecting the evaluation questionnaire data filled in by users, and analyzing and summarizing them. According to the user feedback in the evaluation questionnaire, the system administrator can update or upgrade the system configuration. For example, improve the processing process, improve service quality, fix common problems, etc. These updates may include adjusting the work order processing process, adding automation functions, improving the user interface, etc., to improve the system performance and user experience.
[0083] In this embodiment, by continuously monitoring the feedback results of the evaluation questionnaire, the system configuration is adjusted in time and the improvement effect is followed up. The system configuration and service quality are continuously improved to meet user needs and improve the overall operation and maintenance efficiency.
[0084] Reference Figure 5 , Figure 5 The present invention is a schematic diagram of the structure of a system fault feedback device in a hardware operating environment according to an embodiment of the present invention.
[0085] like Figure 5 As shown, the system fault feedback device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.
[0086] Those skilled in the art will understand that Figure 5 The structure shown in does not constitute a limitation on the system fault feedback device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.
[0087] like Figure 5 As shown, the memory 1005 as a storage medium may include an operating system, a data storage module, a network communication module, a user interface module and a system fault feedback program.
[0088] exist Figure 5 In the system fault feedback device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the system fault feedback device of the present invention can be set in the system fault feedback device, and the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and performs the following steps:
[0089] When the fault reporting function is detected to be triggered, the fault site data of the system is collected and the fault work order is submitted to the centralized work order system;
[0090] Packing the fault site data as a work order attachment of the fault work order and uploading it to the centralized work order system;
[0091] Based on the centralized work order system, reproduce the fault and determine the fault type according to the fault work order and the work order attachments;
[0092] Based on the fault type, enter the corresponding sub-process for processing, and after the sub-process verification is completed, the fault work order is submitted to the feedback process.
[0093] Furthermore, the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and further performs the following steps:
[0094] A collection tool based on the front-end collection system collects front-end fault site data of the client of the system;
[0095] Sending instruction parameters to the back-end acquisition system based on the front-end acquisition system;
[0096] Based on the back-end acquisition system, the instruction parameters are transmitted to the application program interface of the management system to collect the back-end fault site data;
[0097] According to the fault page corresponding to the triggering of the fault reporting function, the fault work order is generated and submitted to the centralized work order system.
[0098] Furthermore, the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and further performs the following steps:
[0099] According to the fault information of the fault scene data, a corresponding application program interface and a fault management function are added to the fault scene data;
[0100] Packing the fault site data, the application program interface and the fault management function to generate the work order attachment;
[0101] Upload the work order attachment to the centralized work order system.
[0102] Furthermore, the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and further performs the following steps:
[0103] Parsing the work order attachment, and establishing a corresponding test environment according to the fault work order and the work order attachment;
[0104] Based on the test environment and the fault data in the work order attachment, simulate the fault site;
[0105] The fault type is determined according to the phenomena exhibited at the fault site.
[0106] Furthermore, the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and further performs the following steps:
[0107] If the fault type is an occasional fault, enter the occasional fault sub-process and perform fault analysis on the occasional fault;
[0108] Based on the analysis results of the fault analysis and the solution developed by the operation and maintenance personnel, correct the client or server configuration;
[0109] If the fault type is a secondary fault, determine whether the secondary fault is a complex secondary fault, and enter the sub-process of the corresponding processing personnel according to the determination result, so that the processing personnel can perform operation and maintenance on the secondary fault.
[0110] Furthermore, the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and further performs the following steps:
[0111] Based on the fault type, determine the corresponding processing requirements and processing personnel;
[0112] According to the processing requirements and processing personnel, based on the unified process engine, a gate access to the sub-process is set, and the gate access is used for personnel verification.
[0113] Furthermore, the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and further performs the following steps:
[0114] After the sub-process is verified by the processing personnel corresponding to the access control, the fault work order is returned to the application operation and maintenance personnel of the centralized work order system;
[0115] After detecting that the application operation and maintenance personnel have verified the sub-process and the system fault has been eliminated, the fault work order is submitted to the feedback process.
[0116] Furthermore, the system fault feedback device calls the system fault feedback program stored in the memory 1005 through the processor 1001, and further performs the following steps:
[0117] Based on the centralized work order system, closing the fault work order and generating an evaluation questionnaire;
[0118] Sending the evaluation questionnaire to the system;
[0119] Based on the content written in the evaluation questionnaire, the system configuration is updated or upgraded.
[0120] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or system including the element.
[0121] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.
[0122] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.
[0123] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.
Claims
1. A system fault feedback method, characterized in that: The system fault feedback method comprises the following steps: When the fault reporting function is detected to be triggered, the fault site data of the system is collected and the fault work order is submitted to the centralized work order system; Packing the fault site data as a work order attachment of the fault work order and uploading it to the centralized work order system; Based on the centralized work order system, reproduce the fault and determine the fault type according to the fault work order and the work order attachments; Based on the fault type, enter the corresponding sub-process for processing, and after the sub-process verification is completed, submit the fault work order to the feedback process; Among them, the fault types are divided into occasional faults (OD) and subsequent faults (SD). OD refers to a fault that cannot be reproduced, and SD refers to a fault that can be reproduced. Wherein, the step of entering the corresponding sub-process for processing based on the fault type includes: when the fault type is determined to be OD, entering the OD processing sub-process, correcting the client or server configuration, entering the knowledge base and upgrading the implementation deployment manual according to the actual processing situation of OD and the solution formulated by the operation and maintenance personnel; when the fault type is determined to be SD, further determining whether it is a complex SD; if it is a simple SD, entering the simple operation and maintenance sub-process; if it is a complex SD, transferring the work order to the operation and maintenance team leader for processing, converting the complex SD into a research and development BUG, and at the same time transferring the work order to the DevOps system for the processing personnel to operate and maintain the secondary fault; Wherein, before the step of entering the corresponding sub-process for processing based on the fault type, it also includes: determining the corresponding processing requirements and processing personnel based on the fault type; according to the processing requirements and processing personnel, setting access control for entering the sub-process based on the unified process engine, and the access control is used for personnel verification; wherein, in the unified process engine, according to the defined access control conditions, the corresponding access control rules are configured, and when a fault process triggers to enter the sub-process, the unified process engine checks the characteristics and context information of the current fault, and determines whether the conditions for entering the sub-process are met according to the access control rules; if the fault meets the access control conditions for entering the sub-process, it will be allowed to enter the sub-process; if the fault does not meet the access control conditions, it will be processed according to the preset strategy; The step of submitting the fault work order to the feedback process after the sub-process verification is completed includes: after the sub-process is verified by the processing personnel corresponding to the access control, returning the fault work order to the application operation and maintenance personnel of the centralized work order system; after detecting that the application operation and maintenance personnel has verified the sub-process and the system fault has been eliminated, submitting the fault work order to the feedback process; Among them, the process of collecting the fault site data of the system is divided into front-end fault data collection and back-end fault data collection; the steps of collecting the fault site data of the system and submitting the fault work order to the centralized work order system include: in the process of collecting the front-end data, calling the local screenshot tool of the computer to take a screenshot of the client fault site to capture the front-end fault site data, and the front-end fault site data includes the error information and page layout problems displayed by the client; based on the front-end collection system, sending instruction parameters to the back-end collection system, the instruction parameters include: the type of data to be collected, the data range and the collection method; based on the back-end collection system, calling the API interface of AOM and APM according to the instruction parameters, passing in the instruction parameters and requesting to obtain the back-end fault site data of the corresponding fault site, and the back-end fault site data includes server logs, database query results, code execution time and resource utilization; according to the fault page corresponding to the triggering of the fault reporting function, generating the fault work order and submitting it to the centralized work order system; Among them, the steps of reproducing the fault and determining the fault type based on the centralized work order system according to the fault work order and the work order attachments include: obtaining the fault description, occurrence time and related equipment information contained in the fault work order and the work order attachments, collecting relevant field data according to the information provided by the fault work order, the field data including log records, system status information and equipment data, restoring the state when the fault occurred in a test environment similar to the production environment, including relevant software versions, configuration information and network environment, to establish a corresponding test environment; in the constructed test environment, simulating and reproducing the fault according to the fault work order and field data; and determining the fault type according to the phenomena exhibited at the fault site.
2. The system fault feedback method according to claim 1, characterized in that: The step of packaging the fault site data as a work order attachment of the fault work order and uploading it to the centralized work order system includes: According to the fault information of the fault scene data, a corresponding application program interface and a fault management function are added to the fault scene data; Packing the fault site data, the application program interface and the fault management function to generate the work order attachment; Upload the work order attachment to the centralized work order system.
3. The system fault feedback method according to claim 1, characterized in that: After the step of entering the corresponding sub-process for processing based on the fault type and submitting the fault work order to the feedback process after the sub-process verification is completed, the method further includes: Based on the centralized work order system, closing the fault work order and generating an evaluation questionnaire; Sending the evaluation questionnaire to the system; Based on the content written in the evaluation questionnaire, the system configuration is updated or upgraded.
4. A system fault feedback device, characterized in that: The system fault feedback device comprises: a memory, a processor, and a system fault feedback program stored in the memory and executable on the processor, wherein the system fault feedback program is configured to implement the steps of the system fault feedback method according to any one of claims 1 to 3.
5. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a system fault feedback program, and when the system fault feedback program is executed by the processor, the steps of the system fault feedback method according to any one of claims 1 to 3 are implemented.
Citation Information
Patent Citations
Fault diagnosis method and system for primary loop of power grid
CN105445585A
Machine room fault management method and device, server and system
CN113435611A
Equipment fault processing method and device, storage medium and electronic device
CN114266368A
Business object management method and system, electronic equipment and storage medium
CN117829464A
Crane fault judging and processing method
CN118239391A
