Abnormal instance processing method and device, computer device, and readable storage medium
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA PING AN PROPERTY INSURANCE CO LTD
- Filing Date
- 2022-08-05
- Publication Date
- 2026-06-26
AI Technical Summary
Existing anomaly monitoring software is inefficient in locating and repairing business anomalies, requiring a large amount of manual analysis, which leads to high processing costs.
By obtaining information about abnormal instances, including instance name, number of slow requests, and number of errors, processing controls are displayed, and corresponding functions are triggered based on the application interface to automatically handle abnormal instances.
It improves the efficiency of anomaly handling, reduces processing costs, and decreases the need for manual analysis.
Smart Images
Figure CN115269253B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of cloud monitoring technology, and in particular to an abnormal instance handling method, apparatus, computer equipment, and readable storage medium. Background Technology
[0002] As businesses grow, companies now have many subsystems, and each subsystem is further divided into different application components based on its functions. The implementation of a business function, corresponding to the backend service, may involve a great deal of complex inter-system and multi-component calls.
[0003] During mutual calls, if a business anomaly occurs, pinpointing which specific component caused the problem is a complex and time-consuming task. Current anomaly monitoring software can only monitor the situation; determining the cause of the fault and how to fix it in the shortest possible time requires manual analysis and resolution, necessitating significant manpower, resulting in low efficiency and high costs. Summary of the Invention
[0004] The main objective of this application is to provide an exception instance handling method, apparatus, computer device, and readable storage medium, which aims to improve the processing efficiency of exception handling and reduce the processing cost of exception instances.
[0005] Firstly, this application provides a method for handling abnormal instances, the method comprising:
[0006] If an abnormal instance is detected, information about the abnormal instance is obtained, including the instance name, the number of slow requests, and the number of errors.
[0007] Based on the number of slow requests and the number of errors, N controls for handling the abnormal instances are displayed on the display page, wherein the N controls include at least one of the following: offline control, restart control, close control, login control, and backup control;
[0008] Upon receiving input for the N controls, the application to which the abnormal instance belongs is determined based on the instance name;
[0009] Based on the application interface of the application to which it belongs, the function corresponding to the control is triggered to handle the abnormal instance.
[0010] Secondly, this application also provides an exception instance handling apparatus, the apparatus comprising:
[0011] The acquisition module is used to acquire information about the abnormal instance when an abnormal instance is detected, wherein the information about the abnormal instance includes the instance name, the number of slow requests, and the number of errors.
[0012] The display module is used to display N controls for handling the abnormal instance on the display page based on the number of slow requests and the number of errors, wherein the N controls include at least one of the following: offline control, restart control, close control, login control, and backup control;
[0013] The determination module is used to determine the application to which the abnormal instance belongs based on the instance name when input is received for the N controls;
[0014] The processing module is used to trigger the function corresponding to the control based on the application interface of the application to which it belongs, and to process the abnormal instance.
[0015] Thirdly, this application also provides a computer device, the computer device including a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, it implements the steps of the exception instance handling method described above.
[0016] Fourthly, this application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the exception instance handling method described above.
[0017] This application discloses an abnormal instance handling method, apparatus, computer device, and readable storage medium. The abnormal instance handling method, upon detecting an abnormal instance, acquires information about the abnormal instance, including the instance name, the number of slow requests, and the number of errors. Based on the number of slow requests and errors, it displays N controls on a display page for handling the abnormal instance. These N controls include at least one of a logout control, a restart control, a close control, a login control, and a backup control. The user can perform corresponding processing operations based on these controls. Upon receiving input for any of the N controls, the method first determines the application to which the abnormal instance belongs based on the instance name. Then, based on the application programming interface (API) of the application to which the instance belongs, it triggers the function corresponding to the control to process the abnormal instance. This eliminates the need for the user to analyze the abnormal instance and determine how to handle it, thereby improving the efficiency and reducing the cost of handling abnormal instances.
[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description
[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0020] Figure 1 This is a flowchart illustrating an embodiment of the abnormal instance handling method of this application;
[0021] Figure 2 This is a flowchart illustrating another embodiment of the abnormal instance handling method of this application;
[0022] Figure 3 A schematic block diagram of an exception instance handling apparatus provided in an embodiment of this application;
[0023] Figure 4 This is a schematic block diagram of the structure of a computer device according to an embodiment of this application.
[0024] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0025] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0026] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.
[0027] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.
[0028] It should also be understood that the term "and / or" as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.
[0029] Embodiments of this application provide an exception instance handling method, apparatus, computer device, and readable storage medium. The exception instance handling method is primarily applied to an exception instance handling device, which can be a terminal device with data processing capabilities, such as a server.
[0030] The server can be a standalone server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and data analysis platforms.
[0031] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.
[0032] Currently, there are numerous complex cross-system, multi-component calls between various systems.
[0033] During mutual calls, if a business anomaly occurs, pinpointing which specific component caused the problem is a complex and time-consuming task. Current anomaly monitoring software can only monitor the situation; determining the cause of the fault and how to fix it in the shortest possible time requires manual analysis and resolution, necessitating significant manpower, resulting in low efficiency and high costs.
[0034] Therefore, this application provides an exception instance processing method, apparatus, computer device, and readable storage medium. The exception instance processing method aims to improve the processing efficiency of exception processing and reduce the processing cost of exception instances.
[0035] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating an exception instance handling method provided in an embodiment of this application.
[0036] like Figure 1 As shown, the exception instance handling method includes steps S101 to S104.
[0037] Step S101: If an abnormal instance is detected, obtain information about the abnormal instance, wherein the information about the abnormal instance includes the instance name, the number of slow requests, and the number of errors.
[0038] Among them, the system and application can be tested in real time or at regular intervals based on pre-set indicators to determine whether there are any abnormalities in the system or application.
[0039] Specifically, the system can include a network operating system and a distributed operating system. The distributed operating system can be a distributed lock operating system, a distributed storage operating system, a high-reliability metadata management operating system, etc., and can be configured according to actual needs.
[0040] Anomalies include availability, performance, capacity, sampling period, and thresholds. Availability can include instances where an application attempts to access an empty object, provides an exception for database access errors or other error messages, a sorting index (such as sorting an array, string, or vector) goes out of range, or an application attempts to convert a string to a numeric type, but the string cannot be converted to the appropriate format. Performance can include instances affected by anomalies such as I / O exceptions, instance migration or retirement, disk failures, and service failures. Capacity can include the application's capacity to the system's capacity. Sampling period includes the period at which various information is collected. Thresholds can include memory thresholds, sampling thresholds, etc., and are not limited here.
[0041] Upon detecting an abnormal instance, its specific information is obtained, including the instance name, the number of slow requests, and the number of errors. The instance name allows for the identification of the specific location of the abnormal instance, such as which application the exception pertains to. The number of slow requests and errors reveals the specific nature of the exception, providing users with detailed information about the anomaly.
[0042] Before obtaining the exception instance, the following can be included:
[0043] Based on the application to be monitored, set N monitoring metrics, wherein the N monitoring metrics include at least one of availability, performance, capacity, sampling period, and threshold.
[0044] Before identifying anomalous instances, different monitoring metrics can be set for each application to detect various anomalous instances. This facilitates real-time or periodic monitoring of applications based on specific instructions, thereby identifying anomalous instances across different applications. Specifically, monitoring metrics can include at least one of availability, performance, capacity, sampling period, and threshold.
[0045] In this embodiment, by setting monitoring metrics for each application, accurate detection of abnormal instances can be achieved.
[0046] Step S102: Based on the number of slow requests and the number of errors, display N controls on the display page to handle the abnormal instances, wherein the N controls include at least one of the following: offline control, restart control, close control, login control, and backup control.
[0047] In this embodiment, N controls for handling the abnormal instance can be displayed on the display page based on the number of slow requests and the number of errors. The controls may include at least one of the following: offline control, restart control, close control, login control, and backup control. The specific number of controls can be determined based on the number of slow requests and the number of errors.
[0048] Further, after step 101, the following may be included:
[0049] Modify the attribute information of the exception instance and its information to a link, and display the generated link.
[0050] Specifically, the attribute information of the abnormal instance and the information of the abnormal instance can be modified into a link, and the generated link can be sent out and displayed.
[0051] Step 102 may specifically include:
[0052] Step 1021: Based on the historical exception instance handling cases corresponding to the number of slow requests and the number of errors, predict the handling method of the exception instance;
[0053] Step 1022: Display N controls for processing the abnormal instance based on the processing method.
[0054] In some embodiments, the handling method of the abnormal instance can be predicted based on historical abnormal instance handling cases corresponding to the number of slow requests and the number of errors. For example, historical abnormal instance handling cases that match the number of slow requests and the number of errors of the abnormal instance can be obtained, or historical abnormal instance handling cases whose difference from the number of slow requests and the number of errors in the historical abnormal instance are within a preset range can be obtained. Based on the obtained historical abnormal instance handling cases, the corresponding historical handling methods can be obtained, and the handling method of the abnormal instance can be predicted based on the historical handling methods. Then, N controls for handling the abnormal instance are displayed based on the handling methods. For example, if the predicted handling method includes offline, an offline control is displayed on the display page; if the predicted handling method includes closing, a close control is displayed on the display page. The specific number and method of displaying controls are not limited here.
[0055] Furthermore, the display order of the controls can be determined based on the number of slow requests and the number of errors. Step 1022 may specifically include:
[0056] Based on the number of slow requests and the number of errors, the priority of various processing methods is determined;
[0057] Based on the priority, the display positions of the N controls in the progress bar are determined;
[0058] The N controls are displayed based on the specified display positions.
[0059] In some embodiments, the priority of various processing methods is determined based on the number of slow requests and the number of errors; for example, if there are many errors requiring restart, the restart control has a higher priority. Based on the priority, the display positions of the N controls in the progress bar are determined, where the priority is directly proportional to the display position; for example, the higher the priority, the earlier the control is displayed. Alternatively, user operating habits can be pre-calculated to obtain the user's habitual operating area. In this case, the higher the priority, the smaller the distance between the control's display position and the user's habitual operating area. Finally, the N controls are displayed based on the specified display positions. This facilitates user input on high-priority controls and also helps users understand the specific information of abnormal instances.
[0060] Step S103: Upon receiving input for the N controls, determine the application to which the abnormal instance belongs based on the instance name.
[0061] After displaying N controls, the user can determine the specific processing method by inputting into the controls. Furthermore, before processing the exception instance according to the specific processing method, it is necessary to further determine the application to which the exception instance belongs. This allows for processing of the exception instance based on the specific application, making the processing more targeted and improving the accuracy of handling exception instances. Specifically, the application to which the exception instance belongs can be determined by the instance name of the exception instance.
[0062] In some embodiments, step S103 specifically includes:
[0063] Upon receiving input for the N controls, the instance name is compared with the preset instance name of each application;
[0064] The application to which the abnormal instance belongs is determined based on the comparison results.
[0065] In some embodiments, when input is received for the N controls, the instance name is compared with the preset instance name of each application; in each application, each instance name can be pre-associated with the associated application, thereby realizing the comparison of the instance name with the preset instance name of each application, and determining the application to which the abnormal instance belongs based on the comparison result.
[0066] Step S104: Based on the application programming interface of the application to which it belongs, trigger the function corresponding to the control to handle the abnormal instance.
[0067] After determining the application to which the abnormal instance belongs, the function corresponding to the control selected by the user can be triggered through the application programming interface of the application to handle the abnormal instance.
[0068] After handling the abnormal instances, the process may further include:
[0069] Create a processed exception instance and an associated instance of the corresponding processing method;
[0070] Store the associated instance.
[0071] In some embodiments, after processing an exception instance, a processed exception instance can be created, and the created exception instance can be associated with the corresponding processing method and the associated instance can be stored, thereby enriching the database of reference exception instances and corresponding processing methods.
[0072] To better understand the above embodiments, the following are some application scenarios:
[0073] In the current case of instance exception handling, based on the specific information of the exception instance, the controls that need to be displayed are determined. Then, it is determined which application the exception instance is running on. Next, based on the corresponding application and the user-selected controls, the corresponding interface can be called. The exception instance is then processed based on the called interface. By analyzing the distribution of erroneous and slow requests within the exception instance, it can be determined which specific instance caused the exception. Then, based on the specific information of the exception instance, historical exception handling experience or exception handling contingency plans are obtained. On the current page, operations such as taking the instance offline, restarting, shutting down, and backing up can be performed to quickly handle instance exceptions, shorten the exception recovery time, improve the efficiency of exception instance handling, and minimize the impact on business.
[0074] The abnormal instance handling method provided in the above embodiments, upon detecting an abnormal instance, obtains information about the abnormal instance, including the instance name, the number of slow requests, and the number of errors. Based on the number of slow requests and the number of errors, N controls for handling the abnormal instance are displayed on a display page. These N controls include at least one of a logout control, a restart control, a close control, a login control, and a backup control. The user can perform corresponding processing operations based on the controls. Upon receiving input for the N controls, the application to which the abnormal instance belongs is first determined based on the instance name. Then, based on the application programming interface of the application to which the instance belongs, the function corresponding to the control is triggered to handle the abnormal instance. This eliminates the need for the user to analyze the abnormal instance and determine how to handle it, thereby improving the processing efficiency of abnormal instances and reducing the processing cost.
[0075] Please refer to Figure 3 , Figure 3 This is a schematic block diagram of an exception instance handling device provided in an embodiment of this application.
[0076] like Figure 3 As shown, the device 300 includes: an acquisition module 301, a display module 302, a determination module 303, and a processing module 304.
[0077] The acquisition module 301 is used to acquire information about the abnormal instance when an abnormal instance is detected, wherein the information about the abnormal instance includes the instance name, the number of slow requests, and the number of errors.
[0078] Display module 302 is used to display N controls for handling the abnormal instance on the display page based on the number of slow requests and the number of errors, wherein the N controls include at least one of offline control, restart control, close control, login control and backup control;
[0079] The determination module 303 is used to determine the application to which the abnormal instance belongs based on the instance name when receiving input for the N controls;
[0080] The processing module 304 is used to trigger the function corresponding to the control based on the application interface of the application to which it belongs, and to process the abnormal instance.
[0081] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the above-described device and its modules and units can be referred to the corresponding processes in the aforementioned abnormal instance handling method embodiments, and will not be repeated here.
[0082] The apparatus provided in the above embodiments can be implemented as a computer program, which can be used in, for example... Figure 4 It runs on the computer device shown.
[0083] Please see Figure 4 , Figure 4 This is a schematic block diagram illustrating the structure of a computer device provided in an embodiment of this application. The computer device can be a personal computer (PC), a server, or other device with data processing capabilities.
[0084] like Figure 4 As shown, the computer device includes a processor, memory, and network interface connected via a system bus, wherein the memory may include non-volatile storage media and internal memory.
[0085] Non-volatile storage media can store operating systems and computer programs. These computer programs include program instructions that, when executed, cause the processor to perform any exception handling method.
[0086] The processor provides computing and control capabilities, supporting the operation of the entire computer device.
[0087] Internal memory provides an environment for the execution of computer programs stored in non-volatile storage media, which, when executed by a processor, enable the processor to perform any exception handling method.
[0088] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0089] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.
[0090] In one embodiment, the processor is configured to run a computer program stored in memory to perform the following steps:
[0091] If an abnormal instance is detected, information about the abnormal instance is obtained, including the instance name, the number of slow requests, and the number of errors.
[0092] Based on the number of slow requests and the number of errors, N controls for handling the abnormal instances are displayed on the display page, wherein the N controls include at least one of the following: offline control, restart control, close control, login control, and backup control;
[0093] Upon receiving input for the N controls, the application to which the abnormal instance belongs is determined based on the instance name;
[0094] Based on the application interface of the application to which it belongs, the function corresponding to the control is triggered to handle the abnormal instance.
[0095] In some embodiments, when the processor implements the display of N controls on the display page to handle the abnormal instance based on the number of slow requests and the number of errors, wherein the N controls include at least one of the following: offline control, restart control, close control, login control, and backup control, it is used to implement:
[0096] Based on the historical exception handling cases corresponding to the number of slow requests and the number of errors, predict the handling method of the exception instances.
[0097] Based on the aforementioned processing method, N controls are displayed to handle the abnormal instance.
[0098] In some embodiments, the processor implements the N controls for displaying and processing the exception instance based on the processing method, for the following purposes:
[0099] Based on the number of slow requests and the number of errors, the priority of various processing methods is determined;
[0100] Based on the priority, the display positions of the N controls in the progress bar are determined;
[0101] The N controls are displayed based on the specified display positions.
[0102] In some embodiments, the processor implements the step of determining the application to which the abnormal instance belongs based on the instance name upon receiving input for the N controls, for the following purposes:
[0103] Upon receiving input for the N controls, the instance name is compared with the preset instance name of each application;
[0104] The application to which the abnormal instance belongs is determined based on the comparison results.
[0105] In some embodiments, the processor, upon detecting an abnormal instance, obtains information about the abnormal instance, wherein the information about the abnormal instance includes the instance name, the number of slow requests, and the number of errors, and then uses this information to implement:
[0106] Modify the attribute information of the exception instance and its information to a link, and display the generated link.
[0107] In some embodiments, the processor implements the step of obtaining information about the abnormal instance upon detecting an abnormal instance, wherein the information about the abnormal instance includes the instance name, the number of slow requests, and the number of errors, before implementing:
[0108] Based on the application to be monitored, N monitoring indicators are set, wherein the N monitoring indicators include at least one of availability, performance, capacity, sampling period, and threshold.
[0109] In some embodiments, the processor implements the application programming interface based on the application, triggers the function corresponding to the control, and after processing the exception instance, is used to implement:
[0110] Create a processed exception instance and an associated instance of the corresponding processing method;
[0111] Store the associated instance.
[0112] This application also provides a computer-readable storage medium storing a computer program, the computer program including program instructions, and the method implemented when the program instructions are executed can refer to various embodiments of the exception instance handling method of this application.
[0113] The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, SmartMedia Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the computer device.
[0114] Furthermore, the computer-readable storage medium may primarily include a program storage area and a data storage area, wherein the program storage area may store the operating system, at least one application required for a function, etc.; and the data storage area may store data created based on the use of blockchain nodes, etc.
[0115] The blockchain referred to in this invention is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include an underlying blockchain platform, a platform product service layer, and an application service layer.
[0116] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.
[0117] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments. The above descriptions are merely specific implementations of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for handling exception instances, characterized in that, The method includes the following steps: If an abnormal instance is detected, information about the abnormal instance is obtained, including the instance name, the number of slow requests, and the number of errors. Based on the number of slow requests and the number of errors, N controls for handling the abnormal instances are displayed on the display page, wherein the N controls include at least one of the following: offline control, restart control, close control, login control, and backup control; Upon receiving input for the N controls, the application to which the abnormal instance belongs is determined based on the instance name; Based on the application interface of the application to which it belongs, the function corresponding to the control is triggered to handle the abnormal instance; The N controls that display the handling of the abnormal instances on the display page based on the number of slow requests and the number of errors include: Based on the historical exception handling cases corresponding to the number of slow requests and the number of errors, predict the handling method of the exception instances. Based on the processing method described above, N controls are displayed to process the abnormal instance; The N controls for displaying and processing the abnormal instance based on the processing method include: Based on the number of slow requests and the number of errors, the priority of various processing methods is determined; Based on the priority, the display positions of the N controls in the progress bar are determined; The N controls are displayed based on the specified display positions; The step of determining the application to which the abnormal instance belongs based on the instance name upon receiving input for the N controls includes: Upon receiving input for the N controls, the instance name is compared with the preset instance name of each application; The application to which the abnormal instance belongs is determined based on the comparison results.
2. The abnormal instance handling method according to claim 1, characterized in that, Upon detecting an abnormal instance, the step of obtaining information about the abnormal instance, wherein the information about the abnormal instance includes the instance name, the number of slow requests, and the number of errors, and further includes: Modify the attribute information of the exception instance and its information to a link, and display the generated link.
3. The abnormal instance handling method according to claim 1, characterized in that, Upon detecting an abnormal instance, the step of obtaining information about the abnormal instance, including the instance name, number of slow requests, and number of errors, further includes: Based on the application to be monitored, set N monitoring metrics, wherein the N monitoring metrics include at least one of availability, performance, capacity, sampling period, and threshold.
4. The abnormal instance handling method according to claim 1, characterized in that, After triggering the function corresponding to the control based on the application interface of the application to which it belongs, and handling the abnormal instance, the method further includes: Create a processed exception instance and an associated instance of the corresponding processing method; Store the associated instance.
5. An exception instance handling device, characterized in that, The exception instance handling device includes: The acquisition module is used to acquire information about the abnormal instance when an abnormal instance is detected, wherein the information about the abnormal instance includes the instance name, the number of slow requests, and the number of errors. The display module is used to display N controls for handling the abnormal instance on a display page based on the number of slow requests and the number of errors. The N controls include at least one of a logout control, a restart control, a close control, a login control, and a backup control. Displaying the N controls for handling the abnormal instance on the display page based on the number of slow requests and the number of errors includes: predicting the handling method of the abnormal instance based on historical abnormal instance handling cases corresponding to the number of slow requests and the number of errors; and displaying the N controls for handling the abnormal instance based on the handling method. Displaying the N controls for handling the abnormal instance based on the handling method includes: determining the priority of various handling methods based on the number of slow requests and the number of errors; determining the display position of the N controls in the display progress bar based on the priority; and displaying the N controls based on the display position. Determining the application to which the abnormal instance belongs based on the instance name when input is received for the N controls includes: comparing the instance name with preset instance names for each application when input is received for the N controls; and determining the application to which the abnormal instance belongs based on the comparison result. The determination module is used to determine the application to which the abnormal instance belongs based on the instance name when input is received for the N controls; The processing module is used to trigger the function corresponding to the control based on the application interface of the application to which it belongs, and to process the abnormal instance.
6. A computer device, characterized in that, The computer device includes a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, it implements the steps of the exception instance handling method as described in any one of claims 1 to 4.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the exception instance handling method as described in any one of claims 1 to 4.