Method, apparatus and system for handling failure of an application

Abstract

The invention discloses a method, a device and a system for handling the failure of an application program, which relates to the computer field. One embodiment of the method includes separately acquiring exception data generated when an application is running, any of the exception data including at least one exception characteristic information; Aggregating the abnormal data according to the abnormal characteristic information to obtain the amount of abnormal data corresponding to any abnormal characteristic information; Displaying any exception characteristic information, and the amount of exception data corresponding to the exception characteristic information, to handle a failure of the application. The embodiment can quickly discover a fault and accurately locate a fault point.

Description

technical field [0001] The present invention relates to the field of computers, in particular to a method, device and system for handling failures of application programs. Background technique [0002] In the field of computer technology, it is necessary to deal with the faults generated during the running of the application in a timely manner, so as to ensure the normal operation of the business and improve the user experience. Therefore, it is necessary to find and locate the fault point at the first time through technical means. [0003] The process of fault discovery and processing in the prior art is generally as follows: [0004] S101. Generate a collection program through hard coding, and output the abnormal information when the application program is running to a log file. [0005] S102. The log collection service reports the content of the log file to the log system for storage. [0006] S103. When a system failure is found through the monitoring system, manually ...

AI Technical Summary

Problems solved by technology

[0008] 1. The log output depends on the hard coding of the program. When a fault occurs, the fault point that does not output abnormal data cannot be located and must be processed online, which is inefficient

[0009] 2. The abnormal data output code is coupled with the business code, making maintenance difficult

[0010] 3. The content of the output log cannot be controlled, and there are a lot of content irrelevant to the fault, which makes the log data huge, resulting in inability to query or slow query

[0011] 4. The efficiency of manual query is low. At the same time, the log is unstructured data, which cannot be aggregated and analyzed. It is difficult to accurately locate the fault point and obtain the cause of the fault.

Images