Method, apparatus and system for handling failures of application programs

Abstract

The invention discloses a method, a device and a system for dealing with failures of application programs, and relates to the field of computers. A specific implementation of the method includes: separately acquiring abnormal data generated when the application program is running, any of the abnormal data includes at least one kind of abnormal characteristic information; aggregating the abnormal data according to the abnormal characteristic information, Acquiring the amount of abnormal data corresponding to any abnormal characteristic information; displaying any abnormal characteristic information and the abnormal data amount corresponding to the abnormal characteristic information, so as to deal with the failure of the application program. This embodiment can quickly find faults and accurately locate fault points.

Description

technical field [0001] The present invention relates to the field of computers, and in particular, to a method, an apparatus and a system for handling application program failures. Background technique [0002] In the field of computer technology, it is necessary to deal with the faults generated during the running of the application program in time, 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 by hard coding, and output 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 que...

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