CN107301115B - Application program exception monitoring and recovery method and device - Google Patents
Application program exception monitoring and recovery method and device Download PDFInfo
- Publication number
- CN107301115B CN107301115B CN201710494314.5A CN201710494314A CN107301115B CN 107301115 B CN107301115 B CN 107301115B CN 201710494314 A CN201710494314 A CN 201710494314A CN 107301115 B CN107301115 B CN 107301115B
- Authority
- CN
- China
- Prior art keywords
- program
- rule
- preset
- application program
- exception
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
Abstract
The invention provides an application program abnormity monitoring and recovering method and device, which are used for solving the problem of the defects of the traditional watchdog program. The method comprises the following steps: extracting information in the application program log file according to a preset extraction rule, and recording the information into a data table; analyzing information in the data table, and analyzing whether log data are matched with a preset abnormal rule or not; and if the log data is matched with the preset abnormal rule, generating a fault recovery instruction according to the analysis result and a preset recovery strategy. The method of the invention realizes the monitoring of the application program by identifying the keywords in the log output by the application program without embedding codes in the application program, and compared with the modes based on message interaction mode, process reporting and the like, the monitoring program does not need to implant monitoring class codes irrelevant to the service, thereby reducing the coupling and instability of the program.
Description
Technical Field
The invention relates to a computer technology, in particular to a method and equipment for monitoring and recovering application program abnormity.
Background
The application program is operated and deployed in a production environment, and a watchdog program is generally set for improving the reliability of the program and ensuring that the program can be recovered in time when the program is abnormal. The core thought of the traditional watchdog program is to periodically monitor the running state of the monitored program process, so as to ensure that the running state of the monitored process is normal, and once the running state is abnormal, the monitored program is restarted. The monitoring modes mainly comprise the following modes:
(1) based on a message interaction mode, communication between a monitoring process and a monitored process is realized, and the monitored process periodically sends messages to the monitoring process;
(2) a process alive reporting instruction mode, wherein the monitored process and the monitoring process agree on a two-party communication alive reporting instruction and interact through a periodic alive reporting instruction;
(3) and monitoring the PID of the monitored program process. By monitoring the PID of the monitored program process in the operating system, if the PID exists, the program is normal.
The conventional watchdog program has the following disadvantages:
(1) on one hand, no matter the monitoring function is realized based on a message interaction mode or a process reporting mode, monitoring program codes irrelevant to service are required to be implanted into a monitoring program, and the coupling and instability of the codes are increased; meanwhile, if a plurality of application programs are monitored, monitoring codes need to be added in each program, and the expandability is poor;
(2) on the other hand, the types of errors of the application program are complicated, some error types are expected at the beginning of programming, and the unexpected exceptions are difficult to monitor by the existing watchdog program. For example, for some application programs, once errors such as data message errors and instruction errors of an application program interface side beyond the design of the two sides occur, the display state of the application program process is normal, but the application program process cannot normally process other subsequent message data.
Disclosure of Invention
In view of the above, the present invention proposes an application exception monitoring and recovery method and apparatus that overcomes or at least partially solves the above mentioned problems.
To this end, in a first aspect, the present invention provides an application exception monitoring and recovery method, including:
extracting information in the application program log file according to a preset extraction rule, and recording the information into a data table;
analyzing information in the data table, and analyzing whether log data are matched with a preset abnormal rule or not;
and if the log data is matched with the preset abnormal rule, generating a fault recovery instruction according to the analysis result and a preset recovery strategy.
Optionally, the fault information generated by the monitored application program is recorded according to the analysis result, and fault reminding is performed to the user through one or more modes of webpage popup, short message or mail.
Optionally, the preset abnormal rule includes an illegal keyword rule and a legal keyword rule. A first abnormal rule formed by a single communication illegal keyword and/or a plurality of communication illegal keywords and used for identifying an abnormal state;
the preset exception rule comprises at least one first exception rule;
the preset abnormal rule also comprises a second abnormal rule which is composed of a single communication legal keyword and/or any plurality of communication legal keywords and is used for identifying a normal state. The preset exception rule comprises at least one second exception rule. Optionally, the generating the fault recovery instruction includes:
generating a thread-level recovery instruction for recovering the thread with the exception;
and generating program level recovery, namely generating a program restart instruction for the exception which can be recovered only by restarting the program.
In a second aspect, the invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method as set forth in any one of the above.
In a third aspect, the invention provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of any of the methods described above when executing the program.
According to the technical scheme, codes do not need to be embedded in the application program, the application program is monitored by identifying the keywords in the log output by the application program, and compared with a message interaction mode, a process reporting mode and the like, monitoring class codes which are irrelevant to service do not need to be implanted in the monitoring program, so that the coupling and instability of the program are reduced. In addition, the method of the invention can realize the monitoring of a plurality of programs simultaneously, and the application of the monitoring service of the application program is simple and has strong expansibility. Compared with a watchdog system adopting a process PID monitoring mode, the watchdog system can monitor the program class of which the display state of the application program process is normal but the service processing is abnormal.
The foregoing is a brief summary that provides an understanding of some aspects of the invention. This section is neither exhaustive nor exhaustive of the invention and its various embodiments. It is neither intended to identify key or critical features of the invention nor to delineate the scope of the invention but rather to present selected principles of the invention in a simplified form as a brief introduction to the more detailed description presented below. It is to be understood that other embodiments of the present invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow diagram performed in one embodiment of the present invention.
Detailed Description
The invention will be described in connection with an exemplary system.
As shown in fig. 1, the present invention provides an application program exception monitoring and recovering method, including:
s101, extracting information in an application program log file according to a preset extraction rule, and recording the information into a data table;
s102, analyzing information in the data table, and analyzing whether log data are matched with a preset abnormal rule or not;
s103, if the log data are matched with the preset abnormal rule, generating a fault recovery instruction according to the analysis result and a preset recovery strategy.
For example, for java application programs, some exceptions can be captured and processed in a try { }/catch () manner during running, some exceptions can be captured but cannot be processed in the try { }/catch () manner, and a log is output after the exceptions are captured in the try { }/catch () manner. It is the computing logic of these applications and the log of their outputs that the method of the present invention was devised herein. The abnormal operation of the program can be finally caused by the abnormality, and the program can be finally operated in a mode deviating from the expected mode of a designer, so that the normal operation of the program can be timely recovered by monitoring the abnormal operation and restarting the program in time.
In some embodiments of the invention, extracting the keywords in the log may be performed by: and recording the running log by using a tool such as log4j, collecting the communication keywords, the communication illegal keywords and the log timestamp data by a collection module (the collection module collects the keywords according to an extraction rule, and the extraction rule is designed according to the functions, the operation logic and the characteristics of the log of the application program) and recording the collected data into a data table.
It is understood that before the method of the present application is executed, the extraction rule, the exception rule and the recovery policy need to be preset, which may be when the configuration parameter is configured.
If the log data is matched with the preset abnormal rule, the application program with the error can be obtained through analysis, the fault recovery instruction is used for recovering the application program with the error, and the recovery can be a recovery step executed according to the error data after restarting or collecting the error data.
The recovery instruction is preset, and the corresponding recovery instruction is selected and called according to the analysis result. For example, when the method of the invention is used for monitoring the wireless network module, the information in the log output by the wireless network module is extracted according to the preset rule and is recorded in the data table; the extracted information may be a record formed by a combination of a keyword and a timestamp; and analyzing the information in the data table, and analyzing whether the log data is matched with a preset abnormal rule or not.
For example, in an embodiment of the present invention, if a sentence log includes CONNECTED, the sentence log should further include a CONNECTED wireless network name (i.e., an ssid name), that is, if a CONNECTED keyword is found in the log, the content and the timestamp of the log are stored in a data table, and whether the log includes a wireless network name is analyzed, if the content of the log is as follows: the method includes the steps of (1) registering a wireless network name, (b) registering a wireless network name, (c) registering a wireless network name, (d) registering a wireless network name, ("CONNECTED wireless network name"), and (d) identifying an anomaly. At this time, if the preset recovery strategy is according to the wireless network restart, an instruction for restarting the wireless network is generated.
It is understood that the above embodiments only exemplify the case of recognizing an abnormality from one log. In the actual monitoring process, an anomaly may be identified from multiple logs, for example, by repeatedly appearing the keyword X3 times, and by appearing the keyword Y in the log program after 1 minute, the anomaly z is identified. For example, when an application program works normally, instruction access is usually required to be performed regularly, response data is obtained, and the request/response keywords are recorded in a log file; by combining the service requirements of the application program, part of request/response pair data appears regularly and only appears after the request is sent out, regular expressions of request/response keywords appearing in the log can be abstracted, and the keywords and the keyword regular expressions are started and loaded by the configuration parameter loading module. The log analysis module matches the collected log data with the keyword regular expression, and performs character string analysis through a regular expression analysis algorithm, so that whether the program data communication state is normal can be accurately monitored.
The method of the invention realizes the monitoring of the application program by identifying the keywords in the log output by the application program without embedding codes in the application program, and compared with the modes based on message interaction mode, process reporting and the like, the monitoring program does not need to implant monitoring class codes irrelevant to the service, thereby reducing the coupling and instability of the program.
In addition, the method of the invention can realize the monitoring of a plurality of programs simultaneously, and the application of the monitoring service of the application program is simple and has strong expansibility. Compared with a watchdog system adopting a process PID monitoring mode, the watchdog system can monitor the program class of which the display state of the application program process is normal but the service processing is abnormal.
In some embodiments of the present invention, the fault information generated by the monitored application program is recorded according to the analysis result, and the fault is prompted to the user through one or more of a webpage popup, a short message, or an email. So that the user can check and analyze the log in time.
Optionally, the preset abnormal rule includes an illegal keyword rule and a legal keyword rule. A first abnormal rule formed by a single communication illegal keyword and/or a plurality of communication illegal keywords and used for identifying an abnormal state; the first exception rule is also referred to as an illegal state rule. That is, if the first exception rule is satisfied, the monitored application program is considered to be in an exception state.
The preset abnormal rule also comprises a second abnormal rule which is composed of a single communication legal keyword and/or a plurality of communication legal keywords and is used for identifying a normal state. The second exception rule is also called a legal status rule, i.e. if the second exception rule is met, the monitored application program is considered to be in a normal status.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
The single keyword is a continuous character string, and the single word represents a quantifier. A single keyword may also be referred to as a keyword. The keyword may be a keyword in information output by program execution in the log, for example, the keyword may be a directory name, a script name, a class name of the program code, and the like. The abnormal rule is composed of the keywords and the relations between the keywords, and it can be understood that the abnormal rule also includes a fault-tolerant rule. That is, in some embodiments, the abnormal rule may be represented by a state machine, the keywords in the log may be extracted according to a preset extraction rule, and the state of the state machine may be determined according to the extracted keywords.
The combination of the single keywords in the text includes a combination formed by a plurality of keywords in sequence, namely, if the keywords appear in the log in sequence, the abnormal rule is considered to be met. And identifying whether the monitored application program is in an abnormal state or a normal state according to whether the combination of the single keywords belongs to the first abnormal rule or the second abnormal rule. It is understood that the combination of the plurality of keywords also includes a combination having a time series characteristic formed by the plurality of keywords. For example, in one embodiment of the present invention, an exception rule formed by a combination of multiple keywords is included, i.e., the rule: keyword X appears 3 times repeatedly, and keyword Y appears in the log program after 1 minute.
In other embodiments of the present invention, the keywords are extracted from the log, and according to a rule formed by a preset single keyword or a combination of keywords, it can be further identified whether the monitored application program is in a normal state. The rules formed by the single key or the combination of keys are also called fault-tolerant rules.
Optionally, the generating the fault recovery instruction includes:
generating a thread-level recovery instruction for recovering the thread with the exception;
and generating program level recovery, namely generating a program restart instruction for the exception which can be recovered only by restarting the program.
The invention provides a computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method as set forth in any of the above.
The invention provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method as described in any one of the above when executing the program.
As used herein, "monitoring" includes any type of function associated with observing, recording or detecting with an instrument that does not have any effect on the operation or status of the element or group of elements being monitored.
As used herein, "at least one," "one or more," and/or "are open-ended expressions that can be combined and separated when used. For example, "at least one of A, B and C," "at least one of A, B or C," "one or more of A, B and C," and "one or more of A, B or C" mean a alone, B alone, C, A and B together, a and C together, B and C together, or A, B and C together.
The term "a" or "an" entity refers to one or more of that entity. Thus the terms "a", "an", "one or more" and "at least one" are used interchangeably herein. It should also be noted that the terms "comprising," "including," and "having" are also used interchangeably.
The term "automated" and variations thereof as used herein refers to any process or operation that is completed without substantial human input when the process or operation is performed. However, a process or operation may be automated even if substantial or insubstantial human input received prior to performing the process or operation is used in performing the process or operation. An artificial input is considered essential if the input affects how the process or operation will proceed. Human input that does not affect the processing or operation is not considered essential.
The term "computer-readable medium" as used herein refers to any tangible storage device and/or transmission medium that participates in providing instructions to a processor for execution. The computer readable medium may be a serial set of instructions encoded in a network transport (e.g., SOAP) over an IP network. Such a medium may take many forms, including but not limited to, non-volatile media, and transmission media. Non-volatile media includes, for example, NVRAM or magnetic or optical disks. Volatile media include dynamic memory, such as main memory (e.g., RAM). Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, magneto-optical medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, a solid state medium such as a memory card, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read. Digital file attachments to e-mail or other self-contained information archives or sets of archives are considered distribution media equivalent to tangible storage media. When the computer readable medium is configured as a database, it should be understood that the database may be any type of database, such as a relational database, a hierarchical database, an object-oriented database, and the like. Accordingly, the present invention is considered to include a tangible storage or distribution medium and equivalents of the prior art known as well as future developed media in which to store a software implementation of the present invention.
The terms "determine," "calculate," and "compute," and variations thereof, as used herein, are used interchangeably and include any type of methodology, process, mathematical operation or technique. More specifically, such terms may include interpreted rules or rule languages such as BPEL, where logic is not hard coded but represented in a rule file that can be read, interpreted, compiled, and executed.
The term "module" or "tool" as used herein refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element. Additionally, while the invention has been described with reference to exemplary embodiments, it should be understood that aspects of the invention may be separately claimed.
It is to be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrases "comprising … …" or "comprising … …" does not exclude the presence of additional elements in a process, method, article, or terminal that comprises the element. Further, herein, "greater than," "less than," "more than," and the like are understood to exclude the present numbers; the terms "above", "below", "within" and the like are to be understood as including the number.
Although the embodiments have been described, once the basic inventive concept is obtained, other variations and modifications of these embodiments can be made by those skilled in the art, so that the above embodiments are only examples of the present invention, and not intended to limit the scope of the present invention, and all equivalent structures or equivalent processes using the contents of the present specification and drawings, or any other related technical fields, which are directly or indirectly applied thereto, are included in the scope of the present invention.
Claims (5)
1. The application program exception monitoring and recovery method is characterized by comprising the following steps:
extracting information in the application program log file according to a preset extraction rule, and recording the information into a data table;
analyzing information in the data table, and analyzing whether log data are matched with a preset abnormal rule or not;
if the log data are matched with a preset abnormal rule, generating a fault recovery instruction according to the analysis result and a preset recovery strategy; wherein the exception rules include fault tolerance rules;
the preset abnormal rule comprises a first abnormal rule which is composed of a single communication illegal keyword and/or a plurality of communication illegal keywords and is used for identifying an abnormal state; the preset exception rule comprises at least one first exception rule;
the preset abnormal rule also comprises a second abnormal rule which is composed of a single communication legal keyword and/or a plurality of communication legal keywords and is used for identifying a normal state;
the preset exception rule comprises at least one second exception rule.
2. The method of claim 1, wherein the fault information generated by the monitored application program is recorded according to the analysis result, and the fault is prompted to the user through one or more of webpage popup, short message or mail.
3. The method of claim 1, wherein generating the fault recovery instruction comprises:
generating a thread-level recovery instruction for recovering the thread with the exception;
and generating program level recovery, namely generating a program restart instruction for the exception which can be recovered only by restarting the program.
4. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 3.
5. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method according to any of claims 1 to 3 are implemented when the program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710494314.5A CN107301115B (en) | 2017-06-26 | 2017-06-26 | Application program exception monitoring and recovery method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710494314.5A CN107301115B (en) | 2017-06-26 | 2017-06-26 | Application program exception monitoring and recovery method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107301115A CN107301115A (en) | 2017-10-27 |
| CN107301115B true CN107301115B (en) | 2020-12-18 |
Family
ID=60135575
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710494314.5A Active CN107301115B (en) | 2017-06-26 | 2017-06-26 | Application program exception monitoring and recovery method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107301115B (en) |
Families Citing this family (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107886242A (en) * | 2017-11-10 | 2018-04-06 | 平安科技（深圳）有限公司 | Data monitoring method, device, computer equipment and storage medium |
| CN108282517A (en) * | 2017-12-21 | 2018-07-13 | 福建天泉教育科技有限公司 | A kind of method and terminal of web services upgrading |
| CN108052452A (en) * | 2017-12-29 | 2018-05-18 | 北京酷我科技有限公司 | The visual optimization method that a kind of daily record is checked and accepted |
| CN108255623B (en) * | 2018-01-22 | 2022-03-15 | 深圳市卓讯信息技术有限公司 | Data exchange monitoring method and device for realizing internal and external double account checking mechanism of thread |
| CN108363762A (en) * | 2018-02-05 | 2018-08-03 | 广州阿里巴巴文学信息技术有限公司 | A kind of collection processing method of user trajectory, device and terminal device |
| CN108345518A (en) * | 2018-03-12 | 2018-07-31 | 张立江 | A kind of data recovery system after software crash and its restoration methods |
| CN108762966A (en) * | 2018-06-05 | 2018-11-06 | 中国平安人寿保险股份有限公司 | System exception hold-up interception method, device, computer equipment and storage medium |
| CN110825611A (en) * | 2018-08-14 | 2020-02-21 | 深圳兆日科技股份有限公司 | Abnormal program analysis method and device and computer readable storage medium |
| CN109460343A (en) * | 2018-09-10 | 2019-03-12 | 平安科技（深圳）有限公司 | System exception monitoring method, device, equipment and storage medium based on log |
| CN109344060A (en) * | 2018-09-20 | 2019-02-15 | 迈普通信技术股份有限公司 | A kind of analysis method and device of automatic test |
| CN110032487A (en) * | 2018-11-09 | 2019-07-19 | 阿里巴巴集团控股有限公司 | Keep Alive supervision method, apparatus and electronic equipment |
| CN111290927A (en) * | 2018-12-06 | 2020-06-16 | 北京京东尚科信息技术有限公司 | Data monitoring method and device |
| CN111309584B (en) * | 2018-12-11 | 2024-02-23 | 迈普通信技术股份有限公司 | Data processing method, device, electronic equipment and storage medium |
| CN109726272A (en) * | 2018-12-20 | 2019-05-07 | 杭州数梦工场科技有限公司 | Audit regulation recommended method and device |
| CN110059491A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Data import monitoring method, device, equipment and readable storage medium storing program for executing |
| CN110267215B (en) * | 2019-05-21 | 2022-07-08 | 深圳壹账通智能科技有限公司 | Data detection method, equipment and storage medium |
| CN110362545A (en) * | 2019-05-27 | 2019-10-22 | 平安科技（深圳）有限公司 | Log monitoring method, device, terminal and computer readable storage medium |
| CN110690992B (en) * | 2019-09-16 | 2022-03-29 | 中盈优创资讯科技有限公司 | Network cutover abnormity identification method and device |
| CN110764977B (en) * | 2019-09-27 | 2023-11-10 | 赛诺贝斯（北京）营销技术股份有限公司 | Alarm method and device for realizing system safety |
| WO2021212409A1 (en) * | 2020-04-23 | 2021-10-28 | Citrix Systems, Inc. | Identification of log events for computing systems |
| CN112464066B (en) * | 2020-11-25 | 2024-03-15 | 中国信息安全测评中心 | Monitoring method and system for data crawling process |
| CN113778780A (en) * | 2020-11-27 | 2021-12-10 | 北京京东尚科信息技术有限公司 | Application stability determination method and device, electronic equipment and storage medium |
| CN112685045A (en) * | 2020-12-28 | 2021-04-20 | 北京达佳互联信息技术有限公司 | Page source file processing method and device, electronic equipment and storage medium |
| CN112925675B (en) * | 2021-02-26 | 2023-08-01 | 北京百度网讯科技有限公司 | Recovery method and device for applet |
| CN113268377A (en) * | 2021-04-25 | 2021-08-17 | 山东英信计算机技术有限公司 | Abnormal state data backup method, system and storage medium |
| CN114629786A (en) * | 2022-03-22 | 2022-06-14 | 康键信息技术（深圳）有限公司 | Log real-time analysis method, device, storage medium and system |
| CN114816942B (en) * | 2022-06-29 | 2022-09-02 | 智者四海（北京）技术有限公司 | Mobile terminal application stability monitoring method and device, electronic equipment and storage medium |
| CN117493127B (en) * | 2023-12-29 | 2024-04-05 | 太平金融科技服务（上海）有限公司 | Application program detection method, device, equipment and medium |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7137041B2 (en) * | 2003-06-20 | 2006-11-14 | International Business Machines Corporation | Methods, systems and computer program products for resolving problems in an application program utilizing a situational representation of component status |
| CN101060436A (en) * | 2007-06-05 | 2007-10-24 | 杭州华三通信技术有限公司 | A fault analyzing method and device for communication equipment |
| WO2012148841A1 (en) * | 2011-04-29 | 2012-11-01 | Google Inc. | Method and apparatus for detecting memory access faults |
| CN102981943B (en) * | 2012-10-29 | 2016-05-11 | 新浪技术（中国）有限公司 | The method and system of monitoring application daily record |
| CN103793288B (en) * | 2014-02-14 | 2017-07-18 | 北京邮电大学 | A kind of software watchdog system and method |
| CN104503892B (en) * | 2014-12-19 | 2018-07-24 | 宇龙计算机通信科技(深圳)有限公司 | Processing method, processing unit and the terminal of terminal abnormal |
| CN105004957A (en) * | 2015-07-31 | 2015-10-28 | 福州瑞芯微电子股份有限公司 | SD card test method and test device |
| CN105224443A (en) * | 2015-10-09 | 2016-01-06 | 广州视睿电子科技有限公司 | A kind of method and apparatus of Android terminal show log information |
| CN105743712B (en) * | 2016-04-12 | 2018-11-09 | 中国铁道科学研究院电子计算技术研究所 | PIS external interface monitoring system and methods |
-
2017
- 2017-06-26 CN CN201710494314.5A patent/CN107301115B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107301115A (en) | 2017-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107301115B (en) | Application program exception monitoring and recovery method and device | |
| He et al. | Identifying impactful service system problems via log analysis | |
| US9542255B2 (en) | Troubleshooting based on log similarity | |
| Aharon et al. | One graph is worth a thousand logs: Uncovering hidden structures in massive system event logs | |
| US20150121136A1 (en) | System and method for automatically managing fault events of data center | |
| JP6048038B2 (en) | Information processing apparatus, program, and information processing method | |
| US20110083123A1 (en) | Automatically localizing root error through log analysis | |
| US10248517B2 (en) | Computer-implemented method, information processing device, and recording medium | |
| Kobayashi et al. | Towards an NLP-based log template generation algorithm for system log analysis | |
| US7398511B2 (en) | System and method for providing a health model for software | |
| Ding et al. | Mining historical issue repositories to heal large-scale online service systems | |
| Caglayan et al. | Usage of multiple prediction models based on defect categories | |
| Jureczko et al. | A review of process metrics in defect prediction studies | |
| Gurumdimma et al. | Towards detecting patterns in failure logs of large-scale distributed systems | |
| US20150100584A1 (en) | Method, computer program and apparatus for analyzing symbols in a computer system | |
| Liu et al. | Incident-aware duplicate ticket aggregation for cloud systems | |
| CN113127320B (en) | Application program abnormity detection method, device, equipment and system | |
| CN114020432A (en) | Task exception handling method and device and task exception handling system | |
| US10042686B2 (en) | Determination method, selection method, and determination device | |
| CN116756021A (en) | Fault positioning method and device based on event analysis, electronic equipment and medium | |
| CN116721763A (en) | Analysis method and device for disease diagnosis result | |
| CN111338609B (en) | Information acquisition method, device, storage medium and terminal | |
| US11514163B2 (en) | Terminal device, method for control of report of operation information performed by terminal device, and recording medium storing therein program for control of report of operation information performed by terminal device | |
| Ouyang et al. | Explainable ai enabled inspection of business process prediction models | |
| CN114756401B (en) | Abnormal node detection method, device, equipment and medium based on log |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |