Business exception handling method and device, computer equipment and storage medium

[0058] In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, and are not intended to limit the present application.

[0059] The business exception handling method provided by this application can be applied to such as figure 1shown in the application environment. Wherein, the terminal 102 communicates with the server 104 through the network. The exception processing module in the server 104 monitors each service interface, receives the abnormal service information set thrown by each service interface in real time, and sorts and organizes each abnormal service information in the abnormal service information set according to the preset abnormal service level table. As a result of sorting and sorting, the abnormal information of each abnormal service is determined, the abnormal business data is counted according to the abnormal information of each abnormal service, and the alarm prompt is pushed to the terminal 102 according to the abnormal business data, and the abnormal processing information corresponding to the alarm prompt fed back by the terminal 102 is received. Process information and process each abnormal service. Among them, the terminal 102 can be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices, and the server 104 can be realized by an independent server or a server cluster composed of multiple servers.

[0060] In one embodiment, such as figure 2 As shown, a method of business exception handling is provided, which is applied to figure 1 The server in , as an example, includes the following steps:

[0061] S202: Monitor each service interface, and receive a collection of abnormal service information thrown by each service interface in real time.

[0062] On the server side, each business service has a corresponding service interface, and users can interact with the business service through the service interface. Exceptions refer to the errors that occur during the operation of the business processed by the server. When the server handles business logic with abnormal services, the service interface will automatically throw out the abnormal service information. The exception handling module in the server monitors each service interface , when the preset annotation of the service interface is captured, the service interface of the abnormal service is determined according to the preset annotation, so as to locate the service interface of the abnormal service, and receive the abnormal service information thrown by the service interface of the abnormal service , and determine the abnormal service information set according to the abnormal service information thrown by the service interface where the abnormal service occurs. Among them, the preset annotations can be set according to the needs. When there is no abnormality in the processing business logic of the server, the service interface will not throw information, so the thrown information must be abnormal service information.

[0063] S204: According to the preset abnormal service level table, sort the abnormal service information in the abnormal service information set, and determine the abnormal information of each abnormal service according to the sorting result.

[0064] The exception processing module of the server determines the business service corresponding to each exception service according to each exception service information, queries the preset exception service level table according to each exception service information, and determines the level of each exception service, according to the level of each exception service and For the business service corresponding to each abnormal service, the information of each abnormal service is classified and sorted, and the abnormal information of each abnormal service is determined according to the sorting result. The abnormal information of the abnormal service includes the level of the abnormal service, the information of the service interface corresponding to the abnormal service, and the type of business service corresponding to the abnormal service. The abnormal service level table is used to determine the level of each abnormal service, and the abnormal service level table can be set according to the needs.

[0065] S206: Count abnormal business data according to the abnormal information of each abnormal service, and push an alarm prompt according to the abnormal business data.

[0066] The exception processing module of the server determines the number of occurrences of each abnormal service and the level of each abnormal service according to the abnormal information of each abnormal service, and according to the preset sorting algorithm, sorts each abnormal service according to the number of occurrences of each abnormal service and the level of each abnormal service The abnormal service is sorted, and the abnormal business data is determined according to the sorting results, and the alarm prompt is pushed to the user terminal according to the abnormal business data. Among them, the abnormal business data refers to the statistical data of abnormal services, including the abnormal service table that has been sorted according to the preset sorting algorithm, and the abnormal information of each abnormal service in the abnormal service table. The preset sorting algorithm can be customized according to the needs Set by yourself, the alarm prompt is used to prompt the staff of the user terminal to feed back the corresponding abnormal handling information according to the abnormal business data and the processing plan of each abnormal service carried in the alarm prompt.

[0067] S208: Receive exception handling information corresponding to the alarm prompt, and process each exception service according to the exception handling information.

[0068] The exception handling information is used to prompt the exception handling module of the server to handle each exception service. The alarm prompt carries the processing plan of each abnormal service. After receiving the alarm prompt, the staff of the user terminal will confirm whether the processing plan of each abnormal service carried in the alarm prompt is correct. If the processing plan is correct, the staff will return to press the processing The prompt information of the plan processing is sent to the exception handling module of the server, and the exception handling module handles each exception service according to the processing plan according to the prompt information. If the processing plan is incorrect, the staff will rewrite and return the processing plan to the exception handling module of the server, and the exception handling module will handle each exception service according to the returned processing plan. At the same time, the exception handling information includes the exception attributes of each exception service, and the exception attributes include systematic exceptions and sporadic exceptions, and the exception handling module can determine the order of processing each exception service according to the exception attributes. For example, high-level systemic exceptions of exception services can be prioritized.

[0069] The above-mentioned business exception handling method monitors each service interface, receives the abnormal service information set thrown by each service interface in real time, and sorts and sorts each abnormal service information in the abnormal service information set according to the preset abnormal service level table, and according to the classification Organize the results to determine the abnormal information of each abnormal service, count the abnormal business data according to the abnormal information of each abnormal service, push the alarm prompt according to the abnormal business data, receive the abnormal processing information corresponding to the alarm prompt, and perform abnormal processing for each abnormal service according to the abnormal processing information deal with. In this way, unified exception handling is provided for the service interface, so that the implementation of all interface services only focuses on the business logic required by the service, and does not need to pay attention to exception handling, and does not affect the normal business processing of the server.

[0070] The scheme of the present application is illustrated below through an embodiment.

[0071] The server-side exception handling module first monitors each service interface. When the preset annotation of the service interface is captured, it determines the service interface of the abnormal service according to the preset annotation, and receives the abnormal service information thrown by the service interface of the abnormal service. The abnormal service information set is determined according to the abnormal service information thrown by the service interface where the abnormal service occurs. Then, according to the abnormal service information, determine the business service corresponding to each abnormal service, query the preset abnormal service level table according to each abnormal service information, and determine the level of each abnormal service. For the corresponding business service, the abnormal service information is sorted, and the abnormal information of each abnormal service is determined according to the sorting result. Then, according to the abnormal information of each abnormal service, determine the number of occurrences of each abnormal service and the level of each abnormal service, and sort each abnormal service according to the number of occurrences of each abnormal service and the level of each abnormal service according to the preset sorting algorithm , according to the sorting results, determine the abnormal business data, and push the alarm prompt according to the abnormal business data. Finally, receive the abnormal processing information corresponding to the alarm prompt, determine the abnormal attributes and processing schemes of the abnormal service information corresponding to each abnormal service information according to the abnormal processing information, and process each abnormal service according to the abnormal attributes and processing solutions of each abnormal service.

[0072] In one of the examples, as image 3 As shown, S202 includes:

[0073] S302: Monitor each service interface, and when the preset annotation of the service interface is captured, determine the service interface with the abnormal service according to the preset annotation;

[0074] S304: Receive the abnormal service information thrown by the service interface where the abnormal service occurs;

[0075] S306: Determine the abnormal service information set according to the abnormal service information thrown by the service interface where the abnormal service occurs.

[0076] The exception handling module of the server monitors each service interface. When the preset annotation of the service interface is captured, the service interface with the abnormal service is determined according to the preset annotation, and the abnormal service information thrown by the service interface with the abnormal service is received. The abnormal service information thrown by the service interface of the abnormal service determines the abnormal service information set. Among them, the preset annotation can be set as required, and the annotation can be used to identify the service interface corresponding to the annotation, and the annotation includes parameter information of the service interface. When the server processes business logic without exception, the service interface will not throw information, so the thrown information must be abnormal service information.

[0077] In the above embodiment, each service interface is monitored, the service interface with abnormal service is determined according to the preset annotation of the service interface, the abnormal service information thrown by the service interface with abnormal service is received, and the abnormal service information set is determined according to the abnormal service information, Accurate acquisition of abnormal service information is realized.

[0078] In one of the examples, as Figure 4 As shown, S204 includes:

[0079] S402: Determine the business service corresponding to each abnormal service according to the information of each abnormal service;

[0080] S404: According to the information of each abnormal service, query the preset abnormal service level table, and determine the level of each abnormal service;

[0081] S406: According to the level of each abnormal service and the business service corresponding to each abnormal service, sort and organize the information of each abnormal service;

[0082] S408: Determine the abnormal information of each abnormal service according to the sorting result.

[0083] The exception handling module of the server can determine the business service corresponding to each exception service according to each exception service information, query the preset exception service level table according to each exception service information, and determine the level of each exception service. The level and the business service corresponding to each abnormal service classify and organize the information of each abnormal service, and determine the abnormal information of each abnormal service according to the classification and sorting results. Wherein, after the business service corresponding to each abnormal service is determined, the service interface corresponding to the abnormal service information can be determined according to the business service, that is, the source information of the abnormal service can be determined. The preset abnormal service level table can be set according to the needs. For example, the abnormal service can be divided into three levels: first-class, second-class and third-class according to the degree of influence of the abnormal service. Among them, the first-class abnormal service has great impact on business Service processing logic has the greatest impact and needs to be resolved first. Second-class abnormal services are resolved before third-class abnormal services.

[0084] Further, according to the level of each abnormal service and the business service corresponding to each abnormal service, the classification of each abnormal service information includes: first, according to the business service corresponding to each abnormal service, the various abnormal services belonging to the same business service are summarized and sorted , and then sort the abnormal services belonging to the same business service according to the level of each abnormal service. The exception information of each exception service includes the level of the exception service, the business service type corresponding to the exception service, and the service interface information corresponding to the exception service.

[0085] In the above embodiment, according to the abnormal service information, determine the business service corresponding to each abnormal service, and query the preset abnormal service level table to determine the level of each abnormal service, and then according to the level of each abnormal service and the corresponding The business service of each abnormal service is classified and arranged, and the abnormal information of each abnormal service is determined, so as to realize the acquisition of abnormal information of each abnormal service.

[0086] In one of the examples, as Figure 5 As shown, S206 includes:

[0087] S502: Determine the number of occurrences of each abnormal service and the level of each abnormal service according to the abnormal information of each abnormal service;

[0088] S504: According to the number of occurrences of each abnormal service and the level of each abnormal service, sort each abnormal service according to a preset sorting algorithm;

[0089] S506: Determine the abnormal business data according to the sorting result;

[0090] S508: Push an alarm prompt according to the abnormal business data.

[0091] The exception processing module of the server determines the number of occurrences of each abnormal service and the level of each abnormal service according to the abnormal information of each abnormal service, and according to the preset sorting algorithm, sorts each abnormal service according to the number of occurrences of each abnormal service and the level of each abnormal service The abnormal service is sorted, and the abnormal business data is determined according to the sorting results, and the alarm prompt is pushed according to the abnormal business data. Among them, the preset sorting algorithm can be set according to the needs. For example, the abnormal services can be sorted according to the level of each abnormal service, and then the abnormal services belonging to the same level can be sorted according to the number of occurrences of each abnormal service , to generate an exception service table. Abnormal business data refers to the statistical data of abnormal services, including the abnormal service table that has been sorted according to the preset sorting algorithm, and the abnormal information of each abnormal service in the abnormal service table. The alarm prompt is used to remind the staff of the terminal, Feedback the corresponding exception handling information according to the abnormal business data. Further, the alarm prompt may prompt relevant staff to give priority to processing abnormal services with high levels and abnormal services with high occurrence frequency.

[0092] In the above embodiment, according to the abnormal information of each abnormal service, the number of occurrences of each abnormal service and the level of each abnormal service are determined, and according to the number of occurrences of each abnormal service and the level of each abnormal service, according to a preset sorting algorithm, each abnormal service is sorted. The abnormal service is sorted, the abnormal business data is determined according to the sorting result, and the alarm prompt is pushed according to the abnormal business data, so that the relevant staff can feedback the abnormal processing information according to the alarm prompt, so as to realize the accurate processing of the abnormal service.

[0093] In one of the examples, as Image 6 As shown, S208 includes:

[0094] S602: According to the abnormal handling information, determine the abnormal attributes and processing scheme of the abnormal service corresponding to each abnormal service information;

[0095] S604: Process each abnormal service according to the abnormal attribute and the processing scheme of each abnormal service.

[0096] The exception handling information is used to prompt the exception handling module of the server to handle each exception service. The alarm prompt carries the processing plan of each abnormal service. After receiving the alarm prompt, the staff of the user terminal will confirm whether the processing plan of each abnormal service carried in the alarm prompt is correct. If the processing plan is correct, the staff will return to press the processing The prompt information of the plan processing is sent to the exception handling module of the server, and the exception handling module handles each exception service according to the processing plan according to the prompt information. If the processing plan is incorrect, the staff will rewrite and return the processing plan to the exception handling module of the server, and the exception handling module will handle each exception service according to the returned processing plan.

[0097] At the same time, the exception handling information includes the exception attributes of each exception service, and the exception attributes include systematic exceptions and sporadic exceptions, and the exception handling module can determine the order of processing each exception service according to the exception attributes. For example, high-level systemic exceptions of exception services can be prioritized. Among them, systematic anomalies refer to abnormal services whose occurrence times are greater than or equal to a preset threshold, sporadic anomalies refer to abnormal services whose occurrence times are less than a preset threshold, and the preset threshold can be set according to needs.

[0098] In the above-mentioned embodiment, according to the exception handling information, the abnormal attributes and processing schemes of the abnormal services corresponding to each abnormal service information are determined, and each abnormal service is processed according to the abnormal attributes and processing schemes of each abnormal service, realizing accurate processing of abnormal services .

[0099] In one of the examples, as Figure 7 As shown, after S204, including:

[0100] S702: Record the abnormal information of each abnormal service that occurs according to the preset log;

[0101] S704: Determine the service interface information corresponding to each abnormal service according to the abnormal information;

[0102] S706: Record the information of the service interface corresponding to each abnormal service according to the preset log;

[0103] S708: According to the abnormal information of each abnormal service and the information of the service interface corresponding to each abnormal service, make statistics and record the number of occurrences of each abnormal service, the number of abnormal occurrences of each service interface, and the occurrence of corresponding business services according to the preset log The number of exceptions.

[0104] The exception handling module of the server records the abnormal information of each abnormal service according to the preset log record, determines the information of the service interface corresponding to each abnormal service according to the abnormal information, and records the information of the service interface corresponding to each abnormal service according to the preset log record. Information, according to the abnormal information of each abnormal service and the information of the service interface corresponding to each abnormal service, count and record the number of occurrences of each abnormal service, the number of abnormal occurrences of each service interface, and the occurrence of corresponding business services according to the preset log The number of exceptions. Among them, the preset log is used to record information related to abnormal services, which is convenient for data analysis of abnormal service processing.

[0105] In the above embodiment, according to the preset log records the abnormal information of each abnormal service and the information of the service interface corresponding to each abnormal service, count and record the number of occurrences of each abnormal service, the number of abnormal occurrences of each service interface, and the corresponding The number of abnormalities in business services enables the recording of various data in the process of abnormal service processing, which is convenient for data analysis of abnormal service processing.

[0106] It should be understood that although Figure 2-7 The various steps in the flowchart are displayed in sequence according to the arrows, but these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. and, Figure 2-7 At least some of the steps may include a plurality of sub-steps or stages, these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the order of execution of these sub-steps or stages is not necessarily It is performed sequentially, but may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

[0107] In one embodiment, such as Figure 8 As shown, a device for handling business exceptions is provided, including: a monitoring module 802, a sorting module 804, a push module 806, and a processing module 808, wherein:

[0108] A monitoring module 802, configured to monitor each service interface, and receive in real time the set of abnormal service information thrown by each service interface;

[0109] The sorting module 804 is configured to sort and sort the abnormal service information in the abnormal service information set according to the preset abnormal service level table, and determine the abnormal information of each abnormal service according to the sorting result;

[0110] The push module 806 is used to count abnormal business data according to the abnormal information of each abnormal service, and push an alarm prompt according to the abnormal business data;

[0111] The processing module 808 is configured to receive abnormality processing information corresponding to the alarm prompt, and process each abnormal service according to the abnormality processing information.

[0112] The above-mentioned business exception processing device monitors each service interface, receives the abnormal service information set thrown by each service interface in real time, sorts and sorts each abnormal service information in the abnormal service information set according to the preset abnormal service level table, and sorts out the abnormal service information according to the classification Organize the results to determine the abnormal information of each abnormal service, count the abnormal business data according to the abnormal information of each abnormal service, push the alarm prompt according to the abnormal business data, receive the abnormal processing information corresponding to the alarm prompt, and perform abnormal processing for each abnormal service according to the abnormal processing information deal with. In this way, unified exception handling is provided for the service interface, so that the implementation of all interface services only focuses on the business logic required by the service, and does not need to pay attention to exception handling, and does not affect the normal business processing of the server.

[0113] In one of the embodiments, the monitoring module is also used to monitor each service interface. When the preset annotation of the service interface is captured, the service interface of the abnormal service is determined according to the preset annotation, and the service interface of the abnormal service is received. According to the abnormal service information thrown by the service interface where the abnormal service occurs, the abnormal service information set is determined.

[0114] In one of the embodiments, the sorting module is also used to determine the business service corresponding to each abnormal service according to the information of each abnormal service, query the preset abnormal service level table according to each abnormal service information, and determine the level of each abnormal service , according to the level of each abnormal service and the business service corresponding to each abnormal service, classify and organize the information of each abnormal service, and determine the abnormal information of each abnormal service according to the classification and sorting results.

[0115] In one of the embodiments, the push module is also used to determine the number of occurrences of each abnormal service and the level of each abnormal service according to the abnormal information of each abnormal service, and determine the number of occurrences of each abnormal service and the level of each abnormal service according to the predetermined The established sorting algorithm sorts the abnormal services, determines the abnormal business data according to the sorting results, and pushes the alarm prompt according to the abnormal business data.

[0116] In one of the embodiments, the processing module is further configured to determine the abnormal attributes and processing schemes of the abnormal services corresponding to each abnormal service information according to the abnormal processing information, and process each abnormal service according to the abnormal attributes and processing schemes of each abnormal service.

[0117] In one of the embodiments, the device for business exception processing further includes a recording module, the recording module is used to record the abnormal information of each abnormal service that occurs according to the preset log, and determine the information of the service interface corresponding to each abnormal service according to the abnormal information , according to the preset log records the information of the service interface corresponding to each abnormal service, according to the abnormal information of each abnormal service and the information of the service interface corresponding to each abnormal service, make statistics and record the occurrence of each abnormal service according to the preset log , the number of abnormal occurrences of each service interface, and the number of abnormal occurrences of corresponding business services.

[0118] For the specific limitations of the device for handling exceptions in business, please refer to the limitations of the method for handling exceptions in business above, which will not be repeated here. Each module in the above-mentioned device for business exception handling may be implemented in whole or in part by software, hardware or a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, and can also be stored in the memory of the computer device in the form of software, so that the processor can invoke and execute the corresponding operations of the above-mentioned modules.

[0119] In one embodiment, a computer device is provided, the computer device may be a server, and its internal structure diagram may be as follows Figure 9 shown. The computer device includes a processor, memory, network interface and database connected by a system bus. Wherein, the processor of the computer device is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs and databases. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device is used to store the data of the abnormal service level table. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a business exception handling method is implemented.

[0120] Those skilled in the art can understand that, Figure 9The structure shown in is only a block diagram of a part of the structure related to the solution of this application, and does not constitute a limitation to the computer equipment on which the solution of this application is applied. The specific computer equipment may include more than shown in the figure or Fewer parts, or combining certain parts, or having a different arrangement of parts.

[0121] In one embodiment, a computer device is provided, including a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0122] Monitor each service interface and receive the collection of abnormal service information thrown by each service interface in real time;

[0123] According to the preset abnormal service level table, the abnormal service information in the abnormal service information set is sorted, and the abnormal information of each abnormal service is determined according to the sorting result;

[0124] According to the abnormal information of each abnormal service, the abnormal business data is counted, and the alarm prompt is pushed according to the abnormal business data;

[0125] Receive the exception handling information corresponding to the alarm prompt, and process each exception service according to the exception handling information.

[0126] The above-mentioned computer equipment for business exception processing monitors each service interface, receives the abnormal service information set thrown by each service interface in real time, and sorts and sorts each abnormal service information in the abnormal service information set according to the preset abnormal service level table. The results of sorting and sorting determine the abnormal information of each abnormal service, count the abnormal business data according to the abnormal information of each abnormal service, push the alarm prompt according to the abnormal business data, receive the abnormal processing information corresponding to the alarm prompt, and according to the abnormal processing information to process. In this way, unified exception handling is provided for the service interface, so that the implementation of all interface services only focuses on the business logic required by the service, and does not need to pay attention to exception handling, and does not affect the normal business processing of the server.

[0127] In one embodiment, the following steps are also implemented when the processor executes the computer program:

[0128] Monitor each service interface, and when the preset annotation of the service interface is captured, determine the service interface of the abnormal service according to the preset annotation;

[0129] Receive the abnormal service information thrown by the service interface of the abnormal service;

[0130] The abnormal service information set is determined according to the abnormal service information thrown by the service interface where the abnormal service occurs.

[0131] In one embodiment, the following steps are also implemented when the processor executes the computer program:

[0132] According to the information of each abnormal service, determine the business service corresponding to each abnormal service;

[0133] According to the information of each abnormal service, query the preset abnormal service level table to determine the level of each abnormal service;

[0134] According to the level of each abnormal service and the business service corresponding to each abnormal service, classify and organize the information of each abnormal service;

[0135] The abnormal information of each abnormal service is determined according to the sorting result.

[0136] In one embodiment, the following steps are also implemented when the processor executes the computer program:

[0137] According to the abnormal information of each abnormal service, determine the number of occurrences of each abnormal service and the level of each abnormal service;

[0138] According to the number of occurrences of each abnormal service and the level of each abnormal service, sort each abnormal service according to the preset sorting algorithm;

[0139] Determine the abnormal business data according to the sorting results;

[0140] Push alarm prompts based on abnormal business data.

[0141] In one embodiment, the following steps are also implemented when the processor executes the computer program:

[0142] According to the abnormal handling information, determine the abnormal attribute and processing plan of the abnormal service corresponding to each abnormal service information;

[0143] Each abnormal service is processed according to the abnormal attribute and the processing scheme of each abnormal service.

[0144] In one embodiment, the following steps are also implemented when the processor executes the computer program:

[0145] Record the abnormal information of each abnormal service according to the preset log;

[0146] Determine the service interface information corresponding to each abnormal service according to the abnormal information;

[0147] Record the information of the service interface corresponding to each abnormal service according to the preset log;

[0148] According to the abnormal information of each abnormal service and the information of the service interface corresponding to each abnormal service, make statistics and record the number of occurrences of each abnormal service, the number of abnormal occurrences of each service interface, and the number of abnormal occurrences of corresponding business services according to the preset log frequency.

[0149] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0150] Monitor each service interface and receive the collection of abnormal service information thrown by each service interface in real time;

[0151] According to the preset abnormal service level table, the abnormal service information in the abnormal service information set is sorted, and the abnormal information of each abnormal service is determined according to the sorting result;

[0152] According to the abnormal information of each abnormal service, the abnormal business data is counted, and the alarm prompt is pushed according to the abnormal business data;

[0153] Receive the exception handling information corresponding to the alarm prompt, and process each exception service according to the exception handling information.

[0154] The storage medium for the above-mentioned business exception processing monitors each service interface, receives the abnormal service information set thrown by each service interface in real time, and sorts and sorts each abnormal service information in the abnormal service information set according to the preset abnormal service level table. The results of sorting and sorting determine the abnormal information of each abnormal service, count the abnormal business data according to the abnormal information of each abnormal service, push the alarm prompt according to the abnormal business data, receive the abnormal processing information corresponding to the alarm prompt, and according to the abnormal processing information to process. In this way, unified exception handling is provided for the service interface, so that the implementation of all interface services only focuses on the business logic required by the service, and does not need to pay attention to exception handling, and does not affect the normal business processing of the server.

[0155] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented:

[0156] Monitor each service interface, and when the preset annotation of the service interface is captured, determine the service interface of the abnormal service according to the preset annotation;

[0157] Receive the abnormal service information thrown by the service interface of the abnormal service;

[0158] The abnormal service information set is determined according to the abnormal service information thrown by the service interface where the abnormal service occurs.

[0159] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented:

[0160] According to the information of each abnormal service, determine the business service corresponding to each abnormal service;

[0161] According to the information of each abnormal service, query the preset abnormal service level table to determine the level of each abnormal service;

[0162] According to the level of each abnormal service and the business service corresponding to each abnormal service, classify and organize the information of each abnormal service;

[0163] The abnormal information of each abnormal service is determined according to the sorting result.

[0164] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented:

[0165] According to the abnormal information of each abnormal service, determine the number of occurrences of each abnormal service and the level of each abnormal service;

[0166] According to the number of occurrences of each abnormal service and the level of each abnormal service, sort each abnormal service according to the preset sorting algorithm;

[0167] Determine the abnormal business data according to the sorting results;

[0168] Push alarm prompts based on abnormal business data.

[0169] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented:

[0170] According to the abnormal handling information, determine the abnormal attribute and processing plan of the abnormal service corresponding to each abnormal service information;

[0171] Each abnormal service is processed according to the abnormal attribute and the processing plan of each abnormal service.

[0172] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented:

[0173] Record the abnormal information of each abnormal service according to the preset log;

[0174] Determine the service interface information corresponding to each abnormal service according to the abnormal information;

[0175] Record the information of the service interface corresponding to each abnormal service according to the preset log;

[0176] According to the abnormal information of each abnormal service and the information of the service interface corresponding to each abnormal service, make statistics and record the number of occurrences of each abnormal service, the number of abnormal occurrences of each service interface, and the number of abnormal occurrences of corresponding business services according to the preset log frequency.

[0177] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented through computer programs to instruct related hardware, and the computer programs can be stored in a non-volatile computer-readable memory In the medium, when the computer program is executed, it may include the processes of the embodiments of the above-mentioned methods. Wherein, any references to memory, storage, database or other media used in the various embodiments provided in the present application may include non-volatile and/or volatile memory. Nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Chain Synchlink DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0178] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be It is considered to be within the range described in this specification.

[0179]The above-mentioned embodiments only represent several implementation modes of the present application, and the description thereof is relatively specific and detailed, but it should not be construed as limiting the scope of the patent for the invention. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the scope of protection of the patent application should be based on the appended claims.