CN107273263B - Abnormal operation analysis method, application terminal and monitoring server - Google Patents

Abnormal operation analysis method, application terminal and monitoring server Download PDF

Info

Publication number
CN107273263B
CN107273263B CN201710382761.1A CN201710382761A CN107273263B CN 107273263 B CN107273263 B CN 107273263B CN 201710382761 A CN201710382761 A CN 201710382761A CN 107273263 B CN107273263 B CN 107273263B
Authority
CN
China
Prior art keywords
application
stack data
running
monitoring server
grabbing
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
Application number
CN201710382761.1A
Other languages
Chinese (zh)
Other versions
CN107273263A (en
Inventor
倪秉炬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nubia Technology Co Ltd
Original Assignee
Nubia Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Nubia Technology Co Ltd filed Critical Nubia Technology Co Ltd
Priority to CN201710382761.1A priority Critical patent/CN107273263B/en
Publication of CN107273263A publication Critical patent/CN107273263A/en
Application granted granted Critical
Publication of CN107273263B publication Critical patent/CN107273263B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3051Monitoring 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
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466Performance evaluation by tracing or monitoring
    • G06F11/3476Data logging

Abstract

The embodiment of the invention discloses an abnormal operation analysis method, which comprises the following steps: starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal; when the timed grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application; and uploading the current operating stack data to the monitoring server so that the monitoring server can analyze the abnormal operation according to the current operating stack data. The invention also discloses an application terminal and a monitoring server. The abnormal operation analysis method provided by the embodiment of the invention can automatically report the abnormal operation so as to accurately position the operation problem, thereby improving the abnormal operation solving efficiency.

Description

Abnormal operation analysis method, application terminal and monitoring server
Technical Field
The present invention relates to network operation technologies in the field of communications, and in particular, to an abnormal operation analysis method, an application terminal, and a monitoring server.
Background
With the continuous development of science and technology, electronic technology has also gained rapid development, and the variety of electronic products is also more and more, and people also enjoy various conveniences brought by the development of science and technology. People can enjoy comfortable life brought along with the development of science and technology through various types of electronic equipment.
A large number of applications can be installed on an existing terminal to provide various functions, but the applications on the terminal may have the problems of blocking, flashing, and the like, and for solving the problems, a user is often required to send the terminal back to a manufacturer for maintenance, the manufacturer repeatedly tests a mobile phone through a tester, a developer repeatedly checks an operation log, searches possible reasons of the problems, and then analyzes codes to solve the problems. However, the terminals that solve the problem are very passive and inefficient.
Disclosure of Invention
In order to solve the above technical problems, embodiments of the present invention are expected to provide an abnormal operation analysis method, an application terminal, and a monitoring server, which can autonomously report abnormal operations so as to accurately locate operation problems, thereby improving the efficiency of solving the abnormal operations.
The technical scheme of the invention is realized as follows:
the embodiment of the invention provides an analysis method for abnormal operation, which is applied to an application terminal and comprises the following steps:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal;
when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application;
and uploading the current running stack data to a monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data.
In the above scheme, the starting the timed grabbing task according to the preset starting condition includes:
receiving a remote starting instruction of the monitoring server;
and starting the timed grabbing task according to the remote starting instruction.
In the above scheme, the starting the timed grabbing task according to the preset starting condition includes:
and when the abnormal operation data of the operation of the first application is detected, starting the timed grabbing task.
The embodiment of the invention also provides an analysis method for abnormal operation, which is applied to the monitoring server and comprises the following steps:
receiving current running stack data of a first application, wherein the current running stack data is used for representing the running condition of the first application;
when the current running stack data is the non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result.
In the foregoing solution, the analyzing the operating condition of the first application according to the current operating stack data and the historical stack data includes:
and comparing the current running stack data with the historical stack data, and analyzing the running state of the first application according to a comparison result and a preset abnormal rule.
In the foregoing solution, after analyzing the operating condition of the first application according to the current operating stack data and the historical stack data to obtain an analysis result, the method further includes:
sending the analysis result to a monitoring terminal;
and storing the analysis result into an exception database.
An embodiment of the present invention provides an application terminal, including: the system comprises a first transmitter, a first memory, a first processor and a first communication bus, wherein the first transmitter, the first memory and the first processor are connected through the first communication bus;
the first memory is used for storing the executable instruction or the running exception related program of the first processor and the current running stack data acquired by the first processor;
the first processor is used for calling the running exception related program stored in the first memory and executing the following steps:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal;
when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application;
the first transmitter is used for uploading the current running stack data to a monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data.
In the above application terminal, the application terminal further includes: a first receiver, the first transmitter, the first memory, and the first processor are connected by the first communication bus;
the first receiver is used for receiving a remote start instruction of the monitoring server,
the first processor is specifically configured to start the timed grabbing task according to the remote start instruction;
alternatively, the first and second electrodes may be,
the first processor is specifically configured to start the timing capture task when abnormal operation data occurs in operation of the first application.
An embodiment of the present invention provides a monitoring server, including: the second receiver, the second memory, the second processor and the second communication bus are connected through the second communication bus;
the receiver is used for receiving current running stack data of a first application, and the current running stack data is used for representing the running condition of the first application;
the second memory is used for storing the executable instruction of the second processor or the running exception related program and the current running stack data received by the second receiver;
the second processor is used for calling the running exception related program stored in the second memory and executing the following steps:
when the current running stack data is the non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result.
In the above monitoring server, the monitoring server further includes: a second receiver, the second transmitter, the second memory, and the second processor are connected by the second communication bus;
the second transmitter is configured to analyze the operating condition of the first application according to the current operating stack data and the historical stack data, and after an analysis result is obtained, transmit the analysis result to a monitoring terminal;
the second memory is also used for storing the analysis result into an exception database.
The embodiment of the invention provides a first computer readable storage medium applied to an application terminal, wherein the computer readable storage medium stores one or more programs, and the one or more programs can be executed by one or more first processors to realize the following steps:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal; when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application; and indicating a sender to upload the current running stack data to a monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data.
An embodiment of the present invention provides a second computer-readable storage medium, which is applied in a monitoring server, and the computer-readable storage medium stores one or more programs, and the one or more programs are executable by one or more second processors to implement the following steps:
acquiring current running stack data of a first application received by the receiver, wherein the current running stack data is used for representing the running condition of the first application; when the current running stack data is the non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result.
The embodiment of the invention provides an analysis method for abnormal operation, an application terminal and a monitoring server, wherein the application terminal starts a timing grabbing task according to a preset starting condition, the timing grabbing task is used for regularly grabbing operation stack data of a first application, and the first application is an application operated in the application terminal; when the timed grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application; and uploading the current operating stack data to the monitoring server so that the monitoring server can analyze the abnormal operation according to the current operating stack data. By adopting the implementation technology of the scheme, the application terminal is provided with the timed grabbing task, so that after the timed grabbing task is started when the preset starting condition is met, the application terminal can regularly grab the current running stack data of the first application, and upload the current running stack data to the monitoring server to analyze the abnormal operation, namely, the terminal can timely and regularly report the running related data to the monitoring server to analyze the abnormal data, so that the report of the abnormal operation is automatically carried out, the monitoring server can accurately position the running problem, and the solution efficiency of the abnormal operation is improved.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of an alternative mobile terminal according to an embodiment of the present invention;
fig. 2 is a diagram of a communication network system architecture according to an embodiment of the present invention;
fig. 3 is a flowchart of an analysis method for an operation anomaly according to an embodiment of the present invention;
fig. 4 is a first flowchart of a method for analyzing an operation abnormality according to a further embodiment of the present invention;
fig. 5 is an architecture diagram of an analysis system for abnormal operation according to an embodiment of the present invention;
fig. 6 is an application system architecture diagram of an application terminal and an application server according to an embodiment of the present invention;
fig. 7 is a second flowchart of a method for analyzing an operation abnormality according to another embodiment of the present invention;
FIG. 8-1 is a first interaction diagram of a method for analyzing an operation anomaly according to an embodiment of the present invention;
fig. 8-2 is an interaction diagram ii of an analysis method for an operation abnormality according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of an application terminal according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a monitoring server according to an embodiment of the present invention.
Detailed Description
The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The terminal may be implemented in various forms. For example, the application terminal and the monitoring terminal described in the present invention may include mobile terminals such as a mobile phone, a tablet computer, a notebook computer, a palm top computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and fixed terminals such as a Digital TV, a desktop computer, and the like.
The following description will be given by way of example of a mobile terminal, and it will be understood by those skilled in the art that the construction according to the embodiment of the present invention can be applied to a fixed type terminal, in addition to elements particularly used for mobile purposes.
Referring to fig. 1, which is a schematic diagram of a hardware structure of an optional mobile terminal for implementing various embodiments of the present invention, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, Wi-Fi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).
Wi-Fi belongs to a short-distance wireless transmission technology, and a mobile terminal can help a user to receive and send emails, browse webpages, access streaming media and the like through a Wi-Fi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the Wi-Fi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the Wi-Fi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.
Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.
The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.
Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.
In order to facilitate understanding of the embodiments of the present invention, a communication network system on which the mobile terminal of the present invention is based is described below.
Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present invention, where the communication Network system is an LTE system of a universal mobile telecommunications technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and an IP service 204 of an operator, which are in communication connection in sequence.
Specifically, the UE201 may be the terminal 100 described above, and is not described herein again.
The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Among them, the eNodeB2021 may be connected with other eNodeB2022 through backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.
The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, and the like. The MME2031 is a control node that handles signaling between the UE201 and the EPC203, and provides bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).
The IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem), or other IP services, among others.
Although the LTE system is described as an example, it should be understood by those skilled in the art that the present invention is not limited to the LTE system, but may also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.
Based on the above mobile terminal hardware structure and communication network system, the present invention provides various embodiments of the method.
Example one
The embodiment of the invention provides an analysis method for abnormal operation, as shown in fig. 3, which is applied to an application terminal, and the method can include:
s101, starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in an application terminal.
The embodiment of the invention is mainly applied to monitoring or analyzing the abnormal condition of the first application installed on the application terminal when the first application runs. Such as the phenomenon of seizure, etc.
Optionally, the application terminal in the embodiment of the present invention may be an electronic device of a mobile phone, a tablet, or a desktop, where the application may be installed, and the embodiment of the present invention is not limited. The first application may be any type of application, such as a social application, a payment application, an entertainment application, and the like, and the embodiments of the present invention are not limited thereto.
It should be noted that the analysis method for abnormal operation provided in the embodiment of the present invention mainly analyzes the operation of an application program, and preferably, an android application program in an android system.
In the embodiment of the invention, a monitoring program is installed in a system of an application terminal, the monitoring program can monitor the running data of the application program in the application terminal, the monitoring program also has the realization of a timing grabbing task, and meanwhile, the monitoring program defaults to not start the timing grabbing task for running stack data.
The preset starting conditions for starting the timed grabbing task in the embodiment of the invention can be two, one can be remote starting indicated by the monitoring server, and the other can be starting when the monitoring program of the application terminal monitors that the running data of the application program is abnormal. The method comprises the following specific steps:
(1) and the application terminal receives the remote start instruction of the monitoring server, and starts the timing grabbing task according to the remote start instruction.
It should be noted that the monitoring server may remotely start the timing grabbing task, and the monitoring server may send a remote start instruction to the application terminal through the push service, for example, an IMEI of a mobile phone (application terminal) is used as an identifier of a push channel, and the remote start instruction is sent, so that the application terminal may remotely start the timing grabbing task on the mobile phone.
In the embodiment of the present invention, the premise that whether the monitoring server can remotely control the timing grabbing task in the application terminal is as follows: the remote control between the application terminal and the monitoring server is an enabling relationship, i.e. the application terminal is involved in a service that is remotely controlled by the monitoring server.
Then, for the case that the application terminal does not support remote control, the following manner (2) may be adopted to implement the starting of the timing grabbing task.
(2) And when the application terminal detects that abnormal operation data occurs in the operation of the first application, starting a timing grabbing task.
It should be noted that the monitoring program in the application terminal may detect the running data of the application program, and if the CPU occupied by which application process is too much (for example, more than half of the CPU is occupied) or the memory occupied (for example, more than half of the memory is occupied) is too much, the monitoring program monitors that running abnormal data occurs, or monitors that the application program is crashed or stuck for a long time, and the application terminal may actively start a timing capture task.
It can be understood that, since the application terminal can capture the stack data through the above-mentioned stack data capture mechanism (i.e. preset start condition), it is ensured that the application terminal can capture the stack data immediately when the application terminal goes wrong; and a method for remotely starting a switch for grabbing operating stack data can be provided for an application terminal which is voluntarily added to a terminal experience test, so that the timeliness of finding the operating problems of the application terminal is ensured.
S102, when the timed grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application.
After the application terminal starts the timing grabbing task according to the preset starting condition, the application terminal can grab the running stack data because the application terminal already starts the timing grabbing task. After the timing grabbing task is started, the timing grabbing task is timed, so that when the application terminal executes the timing grabbing task, the grabbing action is executed only when a preset time period is reached, namely when the timing grabbing task is started, and when the preset time period is reached, the current running stack data of the first application is grabbed. That is, the application terminal captures the currently running stack data of the first application every preset time period from the time when the timed capture task is started.
It should be noted that, in the embodiment of the present invention, the stack data may be in the form of a stack log.
Optionally, the preset time period may be 10 seconds, the specific setting of the preset time period may be set in the monitoring program, and the specific setting of the time value may be obtained by requirements of actual situations or experiments, which is not limited in the embodiment of the present invention.
In the embodiment of the present invention, the first application representation is an application running in the application terminal, and therefore, the first application representation is a generic name of the application.
In an embodiment of the present invention, running stack data may include: the method comprises the steps of identifying a process identifier, a thread identifier, the current state of each thread, the class and the method of each thread which is currently running, a lock identifier of each thread waiting and the like corresponding to a first application. In the process of the first application, there may be multiple tasks that are performed simultaneously, each task is a thread, and thus, the running stack data of each application may include multiple threads. The lock identification of each thread waiting is used for representing the condition of occupied resources of each thread.
In this embodiment of the present invention, the current state of each thread may include: running state, waiting state, suspension state, dead lock station and the like.
It should be noted that the application program may be composed of different classes, and the classes are composed of different methods, so that each thread has a corresponding class and method.
For example, if the preset time period is 10 seconds, the application terminal captures the currently running stack data corresponding to the first application every 10 seconds, so that the application terminal can capture 60 times of currently running stack data in 10 minutes.
S103, uploading the current running stack data to the monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data.
After the application terminal captures the current running stack data of the first application, the application terminal can upload the captured current running stack data to the monitoring server, and the monitoring server can analyze whether the running of the application program of the first application is normal or not based on the current running stack data.
It can be understood that, since the application terminal sets the timed grabbing task, after the preset starting condition is met and the timed grabbing task is started, the application terminal can grab the current running stack data of the first application at a fixed time and upload the current running stack data to the monitoring server to analyze abnormal operation, that is, the terminal can report the running related data to the monitoring server timely and at a fixed time to analyze abnormal data, so that the reporting of abnormal operation is realized autonomously, the monitoring server can accurately position the running problem, and the solution efficiency of abnormal operation is improved.
Example two
The embodiment of the present invention further provides an analysis method for abnormal operation, as shown in fig. 4, which is applied to a monitoring server, and the method may include:
s201, receiving current running stack data of a first application, wherein the current running stack data is used for representing the running condition of the first application.
The analysis method for the operation exception provided in the embodiment of the present invention is proposed based on the architecture of the analysis system for the operation exception, as shown in fig. 5, the analysis system for the operation exception may include: the application terminal comprises an application terminal 1, an application server 3, a monitoring server 2 and a monitoring terminal 5, wherein a first application is installed on the application terminal, the application server is a background server corresponding to the first application, and the application server and the background server perform data interaction to complete the function of the first application. The monitoring server can receive the running stack data about the first application sent by the application terminal and the application server so as to analyze the running abnormity according to the running stack data, and send an analysis result to the monitoring terminal so that a worker can know the reason and the position of the running abnormity through the monitoring terminal so as to solve the problem of the running abnormity in the subsequent process.
Fig. 6 is a diagram illustrating an architecture of an application system of an application terminal and an application server, where fig. 6 includes: one or more application servers 3, application terminals 1-1 to 1-5, and a network 4, wherein the network 4 includes network entities such as routers, gateways, etc., which are not shown in the figure. The application terminals 1-1 to 1-5 perform information interaction with the application server 3 through a wired network or a wireless network, so that data such as relevant position information collected from the application terminals 1-1 to 1-5 are transmitted to the application server 3. The types of the application terminals are shown in fig. 6, and include a mobile phone (application terminal 1-3), a tablet computer or PDA (application terminal 1-5), a desktop computer (application terminal 1-2), a PC (application terminal 1-4), a smart TV (application terminal 1-1), and the like. The application terminal is installed with various applications (i.e., a first application) required by a user, such as applications with an entertainment function (e.g., a video application, an audio playing application, a game application, and reading software), and applications with a service function (e.g., a map navigation application, a group purchase application, and a shooting application). The application server 3 is the server for the first application.
In the embodiment of the present invention, the application server may also upload the stack data to the monitoring server, and the timed crawling task for running the stack data on the application server is always running. That is, in the embodiment of the present invention, the monitoring server may receive and store the currently running stack data of the first application from the application terminal or the application server, where the currently running stack data is used to characterize the running status of the first application.
Optionally, the application server may capture the currently running stack data within a preset time period, where the preset time period may be 10 seconds or other values, and the embodiment of the present invention is not limited, where the preset time period may be different from or the same as the preset time period in the first embodiment, and the embodiment of the present invention is not limited.
In an embodiment of the present invention, running stack data may include: the method comprises the steps of identifying a process identifier, a thread identifier, the current state of each thread, the class and the method of each thread which is currently running, a lock identifier of each thread waiting and the like corresponding to a first application. In the process of the first application, there may be multiple tasks that are performed simultaneously, each task is a thread, and thus, the running stack data of each application may include multiple threads. The lock identification of each thread waiting is used for representing the condition of occupied resources of each thread.
In this embodiment of the present invention, the current state of each thread may include: running state, waiting state, suspension state, dead lock station and the like.
It should be noted that the application program may be composed of different classes, and the classes are composed of different methods, so that each thread has a corresponding class and method.
S202, when the current running stack data is the non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result.
After the monitoring server receives the currently running stack data of the first application, the currently running stack data received by the monitoring server may be the running stack data of the first application received by the monitoring server first or the running stack data of the first application received by the monitoring server not first. In the embodiment of the present invention, the method for the monitoring server to perform the operation anomaly analysis needs the cooperation analysis of the historical stack data, so that if the monitoring server receives the operation stack data first, the monitoring server does not perform the analysis of the operation status of the first application, and when the current operation stack data received by the monitoring server is the non-first operation data corresponding to the first application, the monitoring server extracts the historical stack data corresponding to the first application that has been received before, and then the monitoring server can analyze the operation status of the first application according to the current operation stack data and the historical stack data to obtain the analysis result.
Specifically, the monitoring server compares the current running stack data with the historical stack data, and analyzes the running state of the first application according to the comparison result and a preset abnormal rule to obtain an analysis result.
For example, in the embodiment of the present invention, the monitoring server may compare current running stack data received this time with historical running stack data received several times before, the monitoring server compares the running stack data when the process identifier and the thread identifier corresponding to the first application are consistent when comparing, first performs a comparison of a current state of a thread, if the current state of the thread compared by the monitoring server is compared with the historical state of the thread, the thread is always in an abnormal state, at this time, the monitoring server may compare the running class and the method in the thread, if the current running class and the method of the thread compared by the monitoring server are consistent with the running class and the method of the history of the thread, the monitoring server may determine that the thread has a problem of dead loop, the monitoring server derives the result of which particular class and method in the thread that is currently running is problematic.
For example, the period for grabbing the running stack data is set to be 10 seconds, 60 times of running stack data are grabbed in 10 minutes, and after the running stack data are uploaded to the monitoring server, the monitoring server finds that a thread with a thread identifier of 123 is always in a running state in the running stack data, so that the thread is likely to be in a dead loop state, at this time, the system compares the class methods running in the thread, and if the class methods are consistent, the system can determine that the dead loop problem occurs.
It should be noted that the abnormal operation problem that can be analyzed by the monitoring server may include: the abnormal operation type and method, the time length of the jamming, the problem of the dead cycle, the problem of the conflict lock and the like.
Here, the analysis method of the dead cycle has been described above. Several other analytical methods are described below. The following were used:
(1) the monitoring server can directly detect the class and the method of each thread currently running and the class and the method of each thread historically running according to the preset error setting, and obtain the abnormal problems, such as the abnormal problem 404, which are in accordance with the preset error setting.
(2) The monitoring server can simultaneously acquire the running time of each thread by comparing the current state of each thread with the historical state of each thread, and if the monitoring server detects that the running time of a certain thread acquired at a certain time is longer than the normal running time, the monitoring server indicates that the certain part of the first application is blocked, so that the blocking time can be acquired.
(3) The monitoring server can know that all threads of the first application have the problem of using the same lock at present, namely the problem of occupying the same resource, namely the problem of existence of a conflicting lock, according to the lock identifier of each thread waiting and the historical lock identifier of each thread waiting. The lock identification of the thread wait is used to characterize the resource waiting to be occupied.
In the embodiment of the present invention, the monitoring server may finally obtain an analysis result, where the analysis result may include: process identification, thread identification, type of problem, and location of problem.
Further, as shown in fig. 7, in the analysis method for abnormal operation according to an embodiment of the present invention, after S202, the method may further include: S203-S204. The following were used:
and S203, sending the analysis result to the monitoring terminal.
After the monitoring server obtains the analysis result, the monitoring server and the monitoring terminal can perform information interaction through the network, and the principle is consistent with the interaction between the application server and the application terminal, so that the monitoring server can send the analysis result to the monitoring terminal, and a worker or a tester can solve corresponding problems according to the analysis result.
Optionally, the manner in which the monitoring server sends the analysis result to the monitoring terminal may include: the method and the system can be realized by short messages, song push or social application and the like, and the embodiment of the invention is not limited.
It should be noted that a preset communication list of a worker or a tester may be stored in the monitoring server, and after the monitoring server analyzes the result, the analysis result may be sent according to the preset communication list.
Further, in the embodiment of the present invention, after each analysis is completed, the monitoring terminal obtains an analysis result, where the analysis result may include: normal information and abnormal information, and the abnormal information refers to the analysis result of the abnormal. Therefore, the monitoring server sends information that the analysis result of the monitoring terminal may be normal or abnormal.
Here, when the analysis result is abnormal information, the monitoring server sends the analysis result to the monitoring terminal, and displays the analysis result on the monitoring terminal, so that the worker or the tester can visually see where the problem occurs.
Illustratively, the monitoring server notifies the problem description and the problem occurrence class method to the monitoring terminal, so that the related personnel (i.e. the monitoring terminal owner) preset by the project group can quickly analyze and solve the problem.
And S204, storing the analysis result into an abnormal database.
After the monitoring server obtains the analysis result, the monitoring server can also store the analysis result into an exception database so as to facilitate tracking and tracing the problem in the project.
It can be understood that, since the application terminal sets the timed grabbing task, after the preset starting condition is met and the timed grabbing task is started, the application terminal can grab the current running stack data of the first application at a fixed time and upload the current running stack data to the monitoring server to analyze abnormal operation, that is, the terminal can report the running related data to the monitoring server timely and at a fixed time to analyze abnormal data, so that the reporting of abnormal operation is realized autonomously, the monitoring server can accurately position the running problem, and the solution efficiency of abnormal operation is improved.
EXAMPLE III
Based on the implementation of the first embodiment and the second embodiment, the embodiment of the present invention provides an abnormal operation analysis method, as shown in fig. 8-1 and fig. 8-2, the method may include:
s301, the application terminal receives a remote start instruction of the monitoring server, and starts a timing grabbing task according to the remote start instruction, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal.
S302, when the application terminal detects that abnormal operation data occurs in the operation of the first application, starting a timing grabbing task, wherein the timing grabbing task is used for regularly grabbing operation stack data of the first application, and the first application is an application operated in the application terminal.
And S303, when the timing grabbing task is started and a preset time period is reached, the application terminal grabs the current running stack data of the first application.
S304, the application terminal uploads the current running stack data to the monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data.
S305, when the current running stack data is the non-first running data corresponding to the first application, the monitoring server obtains the historical stack data corresponding to the first application, and analyzes the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result.
S306, the monitoring server sends the analysis result to the monitoring terminal.
S307, the monitoring server stores the analysis result into an abnormal database.
And S308, displaying the analysis result by the monitoring terminal.
Example four
Based on the same inventive concept of the first embodiment and the third embodiment, as shown in fig. 9, an embodiment of the present invention provides an application terminal 1, including: a first transmitter 10, a first memory 11, a first processor 12 and a first communication bus 13, wherein the first transmitter 10, the first memory 11 and the first processor 12 are connected through the first communication bus 13;
the first memory 11 is configured to store an executable instruction or an operation exception related program of the first processor 12, and current operation stack data acquired by the first processor 11;
the first processor 12 is configured to call the running exception related program stored in the first memory 11, and execute the following steps:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal;
when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application;
the first transmitter 10 is configured to upload the currently running stack data to a monitoring server, so that the monitoring server performs analysis on abnormal operation according to the currently running stack data.
Optionally, the application terminal 1 further includes: a first receiver 14, wherein the first receiver 14, the first transmitter 10, the first memory 11 and the first processor 12 are connected through the first communication bus 13;
the first receiver 14 is configured to receive a remote start instruction of the monitoring server;
the first processor 12 is specifically configured to start the timed grabbing task according to the remote start instruction.
Optionally, the first processor 12 is specifically configured to start the timing grabbing task when abnormal operation data occurs in operation of the first application.
Based on the same inventive concept of the second embodiment and the third embodiment, as shown in fig. 10, an embodiment of the present invention provides a monitoring server 2, including: a second receiver 20, a second memory 21, a second processor 22 and a second communication bus 23, wherein the second receiver 20, the second memory 21 and the second processor 22 are connected through the second communication bus 23;
the receiver 20 is configured to receive current running stack data of a first application, where the current running stack data is used to characterize a running condition of the first application;
the second memory 21 is used for storing the current running stack data received by the second receiver 20 and the executable instructions or running exception related programs of the second processor 22;
the second processor 22 is configured to call the running exception related program stored in the second memory 21, and execute the following steps:
when the current running stack data is the non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result.
Optionally, the second processor 22 is specifically configured to compare the current running stack data with the historical stack data, and analyze the running status of the first application according to a comparison result and a preset exception rule.
Optionally, the monitoring server 2 further includes: a second transmitter 24, wherein the second receiver 20, the second transmitter 24, the second memory 21 and the second processor 22 are connected through the second communication bus 23;
the second transmitter 24 is configured to analyze the operation status of the first application according to the current operation stack data and the historical stack data, and after an analysis result is obtained, transmit the analysis result to the monitoring terminal;
the second memory 21 is further configured to store the analysis result in an exception database.
In practical applications, the Memory may be a volatile Memory (volatile Memory), such as a Random-Access Memory (RAM); or a non-volatile Memory (non-volatile Memory), such as a Read-Only Memory (ROM), a flash Memory (flash Memory), a Hard Disk (HDD), or a Solid-State Drive (SSD); or a combination of the above types of memories and provides instructions and data to the processor.
The Processor may be at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, and a microprocessor. It will be appreciated that the electronic devices used to implement the processor functions described above may be other devices, and embodiments of the present invention are not limited in particular.
EXAMPLE five
Each functional module in this embodiment may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware or a form of a software functional module.
Based on the understanding that the technical solution of the present embodiment essentially or a part contributing to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a computer-readable storage medium, which includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the method of the present embodiment. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The embodiment of the invention provides a first computer readable storage medium applied to an application terminal, wherein the computer readable storage medium stores one or more programs, and the one or more programs can be executed by one or more first processors to realize the following steps:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal; when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application; and indicating a sender to upload the current running stack data to a monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data.
An embodiment of the present invention provides a second computer-readable storage medium, which is applied in a monitoring server, and the computer-readable storage medium stores one or more programs, and the one or more programs are executable by one or more second processors to implement the following steps:
acquiring current running stack data of a first application received by the receiver, wherein the current running stack data is used for representing the running condition of the first application; when the current running stack data is the non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result.
It should be noted that, in the embodiment of the present invention, the one or more programs may be executed by the one or more first processors to perform the method according to the first embodiment and the third embodiment; in an embodiment of the invention, the one or more programs may be executable by the one or more second processors to perform the method as described in embodiment two and embodiment three.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims (9)

1. An abnormal operation analysis method is applied to an application terminal, and comprises the following steps:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal; the stack data includes: the method comprises the steps that a process identifier, a thread identifier, the current state of each thread, the class and the method of each thread which is currently running and a lock identifier of each thread waiting are corresponding to a first application;
when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application;
uploading the current running stack data to a monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data;
when the application terminal supports remote control, the starting of the timed grabbing task according to the preset starting condition comprises the following steps:
receiving a remote starting instruction of the monitoring server;
starting the timed grabbing task according to the remote starting instruction;
when the application terminal does not support remote control, starting a timing grabbing task according to a preset starting condition, wherein the starting step comprises the following steps: and when the abnormal operation data of the operation of the first application is detected, starting the timed grabbing task.
2. An abnormal operation analysis method is applied to a monitoring server, and comprises the following steps:
receiving current running stack data of a first application, wherein the current running stack data is used for representing the running condition of the first application;
when the current running stack data is non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result;
wherein the analysis result comprises: process identification, thread identification, type of problem, and location information of the problem.
3. The method of claim 2, wherein analyzing the operating condition of the first application based on the current operating stack data and the historical stack data comprises:
and comparing the current running stack data with the historical stack data, and analyzing the running state of the first application according to a comparison result and a preset abnormal rule.
4. The method of claim 2, wherein after analyzing the operating condition of the first application according to the current operating stack data and the historical stack data to obtain an analysis result, the method further comprises:
sending the analysis result to a monitoring terminal;
and storing the analysis result into an exception database.
5. An application terminal, comprising: the system comprises a first transmitter, a first memory, a first processor and a first communication bus, wherein the first transmitter, the first memory and the first processor are connected through the first communication bus;
the first memory is used for storing the executable instruction or the running exception related program of the first processor and the current running stack data acquired by the first processor;
the first processor is used for calling the running exception related program stored in the first memory and executing the following steps:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal; the stack data includes: the method comprises the steps that a process identifier, a thread identifier, the current state of each thread, the class and the method of each thread which is currently running and a lock identifier of each thread waiting are corresponding to a first application;
when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application;
the first transmitter is used for uploading the current running stack data to a monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data;
wherein, the application terminal further comprises: a first receiver, the first transmitter, the first memory, and the first processor are connected by the first communication bus;
when the application terminal supports remote control:
the first receiver is used for receiving a remote start instruction of the monitoring server,
the first processor is specifically configured to start the timed grabbing task according to the remote start instruction;
when the application terminal does not support remote control:
the first processor is further configured to start the timed capture task when detecting that abnormal operation data occurs in the operation of the first application.
6. A monitoring server, comprising: the second receiver, the second memory, the second processor and the second communication bus are connected through the second communication bus;
the receiver is used for receiving current running stack data of a first application, and the current running stack data is used for representing the running condition of the first application;
the second memory is used for storing the executable instruction of the second processor or the running exception related program and the current running stack data received by the second receiver;
the second processor is used for calling the running exception related program stored in the second memory and executing the following steps:
when the current running stack data is non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result;
wherein the analysis result comprises: process identification, thread identification, type of problem, and location information of the problem.
7. The server of claim 6, wherein the monitoring server further comprises: a second receiver, the second transmitter, the second memory, and the second processor are connected by the second communication bus;
the second transmitter is configured to analyze the operating condition of the first application according to the current operating stack data and the historical stack data, and after an analysis result is obtained, transmit the analysis result to a monitoring terminal;
the second memory is also used for storing the analysis result into an exception database.
8. A first computer-readable storage medium for use in an application terminal, the computer-readable storage medium storing one or more programs, the one or more programs being executable by one or more first processors to perform the steps of:
starting a timing grabbing task according to a preset starting condition, wherein the timing grabbing task is used for regularly grabbing running stack data of a first application, and the first application is an application running in the application terminal; the stack data includes: the method comprises the steps that a process identifier, a thread identifier, the current state of each thread, the class and the method of each thread which is currently running and a lock identifier of each thread waiting are corresponding to a first application; when the timing grabbing task is started and a preset time period is reached, grabbing current running stack data of the first application; indicating a sender to upload the current running stack data to a monitoring server so that the monitoring server can analyze abnormal running according to the current running stack data; when the application terminal supports remote control, the starting of the timed grabbing task according to the preset starting condition comprises the following steps: receiving a remote starting instruction of the monitoring server; starting the timed grabbing task according to the remote starting instruction; when the application terminal does not support remote control, starting a timing grabbing task according to a preset starting condition, wherein the starting step comprises the following steps: and when the abnormal operation data of the operation of the first application is detected, starting the timed grabbing task.
9. A second computer-readable storage medium for use in a monitoring server, the computer-readable storage medium storing one or more programs, the one or more programs being executable by one or more second processors to perform the steps of:
receiving current running stack data of a first application, wherein the current running stack data is used for representing the running condition of the first application; when the current running stack data is non-first running data corresponding to the first application, obtaining historical stack data corresponding to the first application, and analyzing the running state of the first application according to the current running stack data and the historical stack data to obtain an analysis result; wherein the analysis result comprises: process identification, thread identification, type of problem, and location information of the problem.
CN201710382761.1A 2017-05-26 2017-05-26 Abnormal operation analysis method, application terminal and monitoring server Active CN107273263B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710382761.1A CN107273263B (en) 2017-05-26 2017-05-26 Abnormal operation analysis method, application terminal and monitoring server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710382761.1A CN107273263B (en) 2017-05-26 2017-05-26 Abnormal operation analysis method, application terminal and monitoring server

Publications (2)

Publication Number Publication Date
CN107273263A CN107273263A (en) 2017-10-20
CN107273263B true CN107273263B (en) 2020-11-17

Family

ID=60065605

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710382761.1A Active CN107273263B (en) 2017-05-26 2017-05-26 Abnormal operation analysis method, application terminal and monitoring server

Country Status (1)

Country Link
CN (1) CN107273263B (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10467774B2 (en) * 2017-11-06 2019-11-05 Qualcomm Incorporated Memory address flipping to determine data content integrity in GPU sub-system
CN108279975B (en) * 2017-12-11 2022-01-14 努比亚技术有限公司 Memory control method, mobile terminal, data interaction method and server
CN108337127B (en) * 2017-12-21 2020-11-03 中国平安人寿保险股份有限公司 Application performance monitoring method, system, terminal and computer readable storage medium
CN108647106B (en) * 2018-05-11 2023-06-30 深圳市腾讯网络信息技术有限公司 Application exception handling method, storage medium and computer device
CN108762960B (en) * 2018-05-14 2021-07-06 国网福建省电力有限公司 Mobile application monitoring system
CN109491860A (en) * 2018-10-17 2019-03-19 深圳壹账通智能科技有限公司 Method for detecting abnormality, terminal device and the medium of application program
CN109783311A (en) * 2018-12-14 2019-05-21 平安普惠企业管理有限公司 Monitor processing method, device, equipment and the readable storage medium storing program for executing of breakpoint behavior
CN111367774A (en) * 2018-12-26 2020-07-03 阿里巴巴集团控股有限公司 Detection method and device
CN110647417B (en) * 2019-09-03 2020-09-22 珠海格力电器股份有限公司 Energy internet abnormal data processing method, device and system
CN111159051B (en) * 2019-12-31 2023-07-04 北京天融信网络安全技术有限公司 Deadlock detection method, deadlock detection device, electronic equipment and readable storage medium
CN111538599A (en) * 2020-04-23 2020-08-14 杭州涂鸦信息技术有限公司 LINUX-based multithreading deadlock problem positioning method and system

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05346874A (en) * 1992-06-15 1993-12-27 Hitachi Ltd Automatic retest result verifying system
CN101257678A (en) * 2008-03-21 2008-09-03 宇龙计算机通信科技(深圳)有限公司 Method, terminal and system for realizing mobile terminal software safe detection
CN103532797A (en) * 2013-11-06 2014-01-22 网之易信息技术(北京)有限公司 Abnormity monitoring method and device for user registration
CN103957133A (en) * 2014-04-22 2014-07-30 北京联时空网络通信设备有限公司 Log monitoring method and device
CN104394009A (en) * 2014-10-29 2015-03-04 中国建设银行股份有限公司 Fault information processing method and device
CN106201756A (en) * 2016-07-12 2016-12-07 努比亚技术有限公司 Log acquisition device, mobile terminal and method
CN106560796A (en) * 2015-12-31 2017-04-12 哈尔滨安天科技股份有限公司 Early-warning method and system for internal memory stack abnormity of intranet terminal application program

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05346874A (en) * 1992-06-15 1993-12-27 Hitachi Ltd Automatic retest result verifying system
CN101257678A (en) * 2008-03-21 2008-09-03 宇龙计算机通信科技(深圳)有限公司 Method, terminal and system for realizing mobile terminal software safe detection
CN103532797A (en) * 2013-11-06 2014-01-22 网之易信息技术(北京)有限公司 Abnormity monitoring method and device for user registration
CN103957133A (en) * 2014-04-22 2014-07-30 北京联时空网络通信设备有限公司 Log monitoring method and device
CN104394009A (en) * 2014-10-29 2015-03-04 中国建设银行股份有限公司 Fault information processing method and device
CN106560796A (en) * 2015-12-31 2017-04-12 哈尔滨安天科技股份有限公司 Early-warning method and system for internal memory stack abnormity of intranet terminal application program
CN106201756A (en) * 2016-07-12 2016-12-07 努比亚技术有限公司 Log acquisition device, mobile terminal and method

Also Published As

Publication number Publication date
CN107273263A (en) 2017-10-20

Similar Documents

Publication Publication Date Title
CN107273263B (en) Abnormal operation analysis method, application terminal and monitoring server
CN108040159B (en) Restart positioning method based on hardware drive, mobile terminal and readable storage medium
CN107133797B (en) Payment abnormity automatic detection method, terminal and computer readable storage medium
US10587741B2 (en) Communication event processing method and apparatus
CN107465841B (en) Fault information reporting method and terminal
CN107506646B (en) Malicious application detection method and device and computer readable storage medium
CN109086164A (en) A kind of application crashes processing method, terminal and computer readable storage medium
CN112148579A (en) User interface testing method and device
CN108196968B (en) Mobile terminal restart positioning method, mobile terminal and computer readable storage medium
CN108121613B (en) Memory page-based restart positioning method, mobile terminal and readable storage medium
CN108012031B (en) Mobile terminal restart positioning method, mobile terminal and computer readable storage medium
CN108052437B (en) Restart positioning method, mobile terminal and computer readable storage medium
CN108255631B (en) Mobile terminal restart positioning method, mobile terminal and computer readable storage medium
CN108089937B (en) Direct memory allocation-based restart positioning method, mobile terminal and storage medium
US9826568B2 (en) Method, system and computer-readable storage medium for reducing data transmission delay
CN112347067A (en) Log information management and control method and device and computer readable storage medium
CN108076200B (en) Mobile terminal restart positioning method, mobile terminal and computer readable storage medium
CN108228423B (en) Mobile terminal restart positioning method, mobile terminal and computer readable storage medium
CN108268335B (en) Restart positioning method based on system service, mobile terminal and storage medium
CN110647418A (en) Exception handling method, server and mobile terminal
CN113099513B (en) Base station selection method, electronic terminal and computer readable storage medium
CN104516803A (en) Electronic device information monitoring method and system and electronic device
CN109856544B (en) Terminal electricity usage time analysis method, terminal and computer-readable storage medium
CN113079528A (en) Network exception handling method and device and computer readable storage medium
CN108334433B (en) Restart positioning method based on power consumption management, mobile terminal and readable storage medium

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