CN114564369A - Application program abnormity monitoring method and device, electronic equipment and storage medium - Google Patents
Application program abnormity monitoring method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114564369A CN114564369A CN202210454557.7A CN202210454557A CN114564369A CN 114564369 A CN114564369 A CN 114564369A CN 202210454557 A CN202210454557 A CN 202210454557A CN 114564369 A CN114564369 A CN 114564369A
- Authority
- CN
- China
- Prior art keywords
- program
- application program
- client
- starting
- running
- 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.)
- Granted
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/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides an application program abnormity monitoring method, an application program abnormity monitoring device, electronic equipment and a storage medium, wherein the method comprises the following steps: when detecting that the application program is started and receiving an indication that a starting module program is loaded, acquiring running data of the starting module program, wherein the loaded sequence of the starting module program is prior to a reporting management module program, and the starting module program and the reporting management module program are subprograms of the application program; performing first detection on whether the starting module program runs abnormally according to the running data; if the detection result of the first detection is that the starting module program is abnormal in operation, an abnormal operation alarm instruction is sent to the server side by reporting the management module program; and if the detection result of the first detection indicates that the starting module program runs normally, sending a normal running instruction to the server by reporting the management module program. The user can improve the application program on the client according to the abnormal operation alarm received by the server, and the operation stability of the application program is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an application program abnormity monitoring method and device, electronic equipment and a storage medium.
Background
The application program at least comprises a starting module program, a reporting management module program and other subprograms, and after the application program is started, the application program can load all the subprograms or a plurality of subprograms of the application program;
at present, when an application program on a client is started, a starting module program loaded before reporting a management module program generates an operation exception, and the operation exception alarm cannot be reported to a server through a reporting management module. The user can not improve the application program on the client according to the abnormal operation alarm received by the server, so that the operation stability of the application program is poor.
Disclosure of Invention
The embodiment of the invention provides an anomaly monitoring method and device for an application program, electronic equipment and a storage medium, aiming at solving the problem that the conventional starting module program loaded before reporting a management module program generates abnormal operation, and the abnormal operation alarm cannot be reported to a server side through a reporting management module; the user can not improve the application program on the client according to the abnormal operation alarm received by the server, so that the operation stability of the application program is poor.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides an anomaly monitoring method for an application program, which is applied to a client, and includes:
when detecting that an application program is started and receiving an indication that a starting module program is loaded, acquiring running data of the starting module program, wherein the loaded sequence of the starting module program is prior to a reporting management module program, and the starting module program and the reporting management module program are subprograms of the application program;
performing first detection on whether the starting module program runs abnormally according to the running data;
if the detection result of the first detection is that the starting module program is abnormal in operation, an abnormal operation alarm instruction is sent to a server side through the reporting management module program;
and if the detection result of the first detection indicates that the starting module program operates normally, sending a normal operation instruction to the server side through the reporting management module program.
In a second aspect, an embodiment of the present invention provides an anomaly monitoring method for an application program, which is applied to a server and includes:
acquiring an abnormal operation alarm instruction sent by a client in a preset statistical time period, and counting the abnormal alarm instruction to obtain abnormal alarm statistical times; the application program running on the client loads a starting module program when being started, and the abnormity warning instruction is used for indicating that the loading starting module program runs abnormally;
determining whether to permit the application program to load the starting module program in the starting process after the preset counting time period or not according to the abnormal alarm counting times;
and if the application program is permitted to load the starting module program in the starting process after the preset statistical time period, sending a permission loading instruction to the client.
Alternatively,
determining whether to permit the application program to load the starting module program in the starting process after the preset statistical time period according to the abnormal alarm statistical times, wherein the method comprises the following steps:
if the abnormal alarm counting times do not exceed a preset alarm counting time threshold, allowing the application program to load the starting module program in the starting process after the preset counting time period;
and if the abnormal alarm counting times exceed the preset warning time threshold, not allowing the application program to load the starting module program in the starting process after the preset counting time period.
In a third aspect, an embodiment of the present invention provides an anomaly monitoring method for an application program, which is applied to a server and includes:
acquiring a normal operation instruction sent by a first client in a preset counting time period, and counting the normal operation instruction sent by the first client to obtain a first normal operation counting number; the method comprises the steps that an application program running on a first client loads a starting module program when the application program is started, and a normal running instruction sent by the first client is used for indicating that the loading starting module program runs normally;
acquiring a normal operation instruction sent by a second client within a preset statistical time period, and counting the normal operation instruction sent by the second client to obtain a second normal operation statistical frequency; the application program running on the second client does not load a starting module program when being started, and the normal running instruction sent by the second client is used for indicating that the application program running on the second client runs normally;
determining whether to permit the application program running on the first client to load the starting module program in the starting process after the preset counting time period according to the first normal running counting times and the second normal running counting times;
and if the application program running on the first client is permitted to load the starting module program in the starting process after the preset statistical time period, sending a permission loading instruction to the first client.
Alternatively,
determining whether to permit the application program running on the first client to load the starting module program in the starting process after the preset statistical time period according to the first normal running statistical number and the second normal running statistical number, wherein the determining comprises the following steps:
if the difference between the first normal running statistical frequency and the second normal running statistical frequency is smaller than or equal to a preset difference threshold, allowing the application program running on the first client to load the starting module program in the starting process after the preset statistical time period;
if the difference between the first normal running statistical frequency and the second normal running statistical frequency is larger than the preset difference threshold, the application program running on the first client is not allowed to load the starting module program in the starting process after the preset statistical time period.
In a fourth aspect, an embodiment of the present invention provides an anomaly monitoring apparatus for an application program, including:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring running data of a starting module program when detecting that the application program is started and receiving an instruction that the starting module program is loaded, the loaded sequence of the starting module program is prior to a reporting management module program, and the starting module program and the reporting management module program are subprograms of the application program;
the first execution module is used for carrying out first detection on whether the starting module program runs abnormally according to the running data;
the first execution module is further configured to send an operation exception warning instruction to a server through the reporting management module program if the detection result of the first detection indicates that the starting module program is abnormal in operation;
the first execution module is further configured to send a normal operation instruction to the server through the reporting management module program if the detection result of the first detection indicates that the starting module program operates normally.
In a fifth aspect, an embodiment of the present invention provides an apparatus for monitoring an exception of an application program, including:
the second acquisition module is used for acquiring an abnormal operation alarm instruction sent by the client in a preset statistical time period, and counting the abnormal alarm instruction to obtain abnormal alarm statistical times; the application program running on the client loads a starting module program when being started, and the abnormity warning instruction is used for indicating that the loading starting module program runs abnormally;
the second execution module is used for determining whether to permit the application program to load the starting module program in the starting process after the preset counting time period or not according to the abnormal alarm counting times;
the second execution module is further configured to send a permission loading instruction to the client if the application program is permitted to load the starting module program during starting after the preset statistical time period.
In a sixth aspect, an embodiment of the present invention provides an anomaly monitoring apparatus for an application program, including:
the third acquisition module is used for acquiring a normal operation instruction sent by the first client within a preset statistical time period, and counting the normal operation instruction sent by the first client to obtain a first normal operation statistical frequency; the method comprises the steps that an application program running on a first client loads a starting module program when the application program is started, and a normal running instruction sent by the first client is used for indicating that the loading starting module program runs normally;
the third obtaining module is further configured to obtain a normal operation instruction sent by the second client within a preset statistical time period, and count the normal operation instruction sent by the second client to obtain a second normal operation statistical frequency; the application program running on the second client does not load a starting module program when being started, and the normal running instruction sent by the second client is used for indicating that the application program running on the second client runs normally;
a third execution module, configured to determine whether to permit the application program running on the first client to load the start module program during starting after the preset statistical time period according to the first normal running statistical frequency and the second normal running statistical frequency;
the third execution module is further configured to send a permission loading instruction to the first client if the application program permitted to run on the first client is loaded during starting after the preset statistical time period.
In a seventh aspect, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements the steps in the abnormality monitoring method for the application program according to any one of the first to third aspects.
In an eighth aspect, the embodiment of the present invention provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps in the abnormality monitoring method for an application program according to any one of the first to third aspects.
In the embodiment of the invention, by acquiring the running data of the starting module program loaded before reporting the management module program, first detection is carried out on whether the starting module program runs abnormally or not according to the running data; if the detection result of the first detection indicates that the starting module program is abnormal in operation, the reporting management module program sends an abnormal operation alarm instruction to the server, so that a user can improve the application program on the client according to the abnormal operation alarm received by the server, and the operation stability of the application program is improved.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flowchart illustrating an anomaly monitoring method for an application according to an embodiment of the present invention;
FIG. 2 is a second flowchart illustrating an anomaly monitoring method for an application according to an embodiment of the present invention;
FIG. 3 is a third flowchart illustrating an anomaly monitoring method for an application according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of an application in the anomaly monitoring method for an application according to the embodiment of the present invention;
FIG. 5 is a diagram illustrating an example of an anomaly monitoring method applied to an application program according to an embodiment of the present invention;
FIG. 6 is a comparison list corresponding to the statistical frequency X of FIG. 5;
FIG. 7 is a schematic diagram of an internal structure of an anomaly monitoring device according to an embodiment of the present invention;
FIG. 8 is a second schematic diagram of an internal structure of an anomaly monitoring device according to an embodiment of the present invention;
FIG. 9 is a third exemplary diagram of an internal structure of an anomaly monitoring device according to an embodiment of the present invention;
fig. 10 is a schematic diagram of an internal structure of an electronic device according to an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present invention provides an anomaly monitoring method for an application program, which is applied to a client, and as shown in fig. 1, fig. 1 is one of flow diagrams of the anomaly monitoring method for the application program according to the embodiment of the present invention, and includes:
step 11: when detecting that the application program is started and receiving an indication that a starting module program is loaded, acquiring running data of the starting module program, wherein the loaded sequence of the starting module program is prior to a reporting management module program, and the starting module program and the reporting management module program are subprograms of the application program;
step 12: performing first detection on whether the starting module program runs abnormally according to the running data;
step 13: if the detection result of the first detection is that the starting module program is abnormal in operation, an abnormal operation alarm instruction is sent to the server side by reporting the management module program;
step 14: and if the detection result of the first detection indicates that the starting module program runs normally, sending a normal running instruction to the server side by reporting the management module program.
In the embodiment of the invention, by acquiring the running data of the starting module program loaded before reporting the management module program, first detection is carried out on whether the starting module program runs abnormally or not according to the running data; if the detection result of the first detection indicates that the starting module program is abnormal in operation, the reporting management module program sends an abnormal operation alarm instruction to the server, so that a user can improve the application program on the client according to the abnormal operation alarm received by the server, and the operation stability of the application program is improved.
An embodiment of the present invention provides an anomaly monitoring method for an application, which is applied to a server, and referring to fig. 2, fig. 2 is a second flowchart of the anomaly monitoring method for an application according to the embodiment of the present invention, and includes:
step 21: acquiring an abnormal operation alarm instruction sent by a client in a preset statistical time period, and counting the abnormal alarm instruction to obtain abnormal alarm statistical times; the method comprises the steps that an application program running on a client loads a starting module program when being started, and an exception warning instruction is used for indicating that the loading starting module program runs abnormally;
step 22: according to the abnormal alarm counting times, determining whether the application program is allowed to load a starting module program in the starting process after a preset counting time period;
step 23: and if the license application program loads the starting module program in the starting process after the preset statistical time period, sending a license loading instruction to the client.
In some embodiments of the present invention, optionally, the number of the clients may be one, and one client may be started multiple times within a preset statistical time period, that is: the abnormal alarm obtained in step 21 may be an abnormal alarm generated by multiple times of starting of a client within a preset statistical time period.
In some embodiments of the present invention, optionally, the number of the clients may be at least two, and the at least two clients are started only once within a preset statistical time period, that is: the abnormal alarm obtained in step 21 may be an abnormal alarm sent by a client that generates an abnormality in at least two clients within a preset statistical time period.
In some embodiments of the present invention, optionally, the number of the clients may be at least two, and each client may have respective starting times within a preset statistical time period (where the number of the clients that are not started within the preset statistical time period is included, that is, the starting times are 0 times), that is: the abnormal alarm obtained in step 21 may be an abnormal alarm sent by a client that generates an abnormality in at least two clients within a preset statistical time period.
In some embodiments of the present invention, optionally, determining whether to permit the application program to load the start module program during starting after a preset statistical time period according to the abnormal alarm statistics number includes:
if the abnormal alarm counting times do not exceed the preset alarm counting time threshold, the application program is allowed to load a starting module program in the starting process after the preset counting time period;
and if the abnormal alarm counting times exceed the preset alarm counting time threshold, not allowing the application program to load the starting module program in the starting process after the preset counting time period.
For example, the preset warning number threshold may be 0, that is, as long as an abnormal warning instruction is acquired in the preset statistical period, the application program is not permitted to load the start module program in the start after the preset statistical period.
An embodiment of the present invention provides an anomaly monitoring method for an application program, which is applied to a server, and referring to fig. 3, fig. 3 is a third schematic flow diagram of the anomaly monitoring method for an application program according to an embodiment of the present invention, and includes:
step 31: acquiring a normal operation instruction sent by a first client within a preset counting time period, and counting the normal operation instruction sent by the first client to obtain a first normal operation counting number; the method comprises the steps that an application program running on a first client loads a starting module program when the application program is started, and a normal running instruction sent by the first client is used for indicating that the loading starting module program runs normally;
step 32: acquiring a normal operation instruction sent by a second client within a preset counting time period, and counting the normal operation instruction sent by the second client to obtain a second normal operation counting number; the application program running on the second client does not load the starting module program when being started, and the normal running instruction sent by the second client is used for indicating that the application program running on the second client runs normally;
step 33: determining whether to permit the application program running on the first client to load a starting module program in starting after a preset counting time period according to the first normal running counting times and the second normal running counting times;
step 34: and if the application program running on the first client is allowed to load the starting module program in the starting process after the preset statistical time period, sending a permission loading instruction to the first client.
In some embodiments of the present invention, optionally, determining whether to allow the application program running on the first client to load the start module program during the start after the preset statistical time period according to the first normal running statistical number and the second normal running statistical number, includes:
if the difference between the first normal running statistical frequency and the second normal running statistical frequency is smaller than or equal to a preset difference threshold value, allowing the application program running on the first client to load the starting module program in the starting process after a preset statistical time period;
and if the difference value between the first normal running statistical frequency and the second normal running statistical frequency is larger than a preset difference value threshold value, the application program running on the first client is not permitted to load the starting module program in the starting process after the preset statistical time period.
Exemplarily, referring to fig. 4, fig. 4 is a schematic structural diagram of an application program in the anomaly monitoring method for an application program according to the embodiment of the present invention, where an application program (APP) start module and a configuration management module are split into two types, i.e., a class a and a class B, where:
(1) the A-type starting module is a starting module which needs to be loaded before the networking report management module (the A-type starting module is equivalent to a starting module program in the embodiment of the invention);
(2) the B-type starting module is a module loaded after the networking configuration management module is loaded;
(3) the A-type configuration management module is used for configuration management of the A-type starting module, only performs local data reading operation during starting, and does not depend on a network;
(4) the B-type configuration management module is used for reading the latest server side updating configuration aiming at the configuration management of the B-type starting module and updating the local A-type or B-type configuration file.
For example, referring to fig. 5, fig. 5 is a schematic diagram illustrating an example of an abnormality monitoring method applied to an application program according to an embodiment of the present invention, and referring to fig. 6, fig. 6 is a comparison list corresponding to the statistical frequency X of fig. 5. The application program (APP) abnormal data statistics time is divided into a non-statistics period and a statistics period.
(1) In a non-statistical period, the APP does not locally count the period time and X configuration, the local counting identifier is 0, the non-loading related module is started by default, if the non-loading related module does not load, the corresponding abnormality cannot be generated, but the identifier 0 needs to be reported for the server to count T _ M _0, and the value is used for analyzing whether the abnormality is generated in the statistical period subsequently; reporting and pulling the latest configuration; the server can configure the relevant data in the statistical period and provide the client for the next pulling. (the non-statistical-period APP is equivalent to an application program running on the second client in the embodiment of the present invention, and the application program running on the second client does not load a start module program when starting;
(2) in the statistical period, the time of the statistical period,
1) when X =1 or APP is started for the nX time, a module to be monitored is loaded, and the loading may generate an exception, including three states: reporting the identifier 0 without generating an exception, and simultaneously pulling the latest configuration; generating an abnormal reporting identifier 1, and simultaneously pulling the latest configuration; a crash cannot be reported and the latest configuration cannot be pulled. Wherein, X >1 is monitoring in the execution cycle, and X =1 is loading when the server side which is tested and confirmed to have no problem issues and can be permanently opened and started.
2) When X =0 or APP is started for a non-Nth X time, a module needing to be monitored is not loaded, and related logic is loaded in a non-statistical period.
(3) In the counting period, the server performs analysis processing according to the total number T _ N _0 of the reported 0 records and the total number T _ N _1 of the reported 1 records in the counting period, and when T _ N _0=0 (in this example, the preset warning frequency threshold is 0 times, that is, as long as an abnormal warning instruction is obtained in the preset counting period, the application program is not permitted to load the startup module program during startup after the preset counting period) or T _ N _0 is approximately equal to T _ M _0 (which is equivalent to the difference between the first normal operation counting frequency and the second normal operation counting frequency in the embodiment of the present invention is less than or equal to the preset difference threshold), the relevant startup module is loaded without generating abnormality and crash, the server may prepare to issue X =1 (the application program is permitted to load the startup module during startup after the preset counting period), sending a permission load instruction to the client) and waiting for the client to pull the latest configuration next time to open the persistent load logic.
When T _ N _1 is far greater than 0 (in this example, the preset warning number threshold is 0, that is, as long as an abnormal warning instruction is obtained in the preset statistical period, the application is not permitted to load the startup module program during startup after the preset statistical period), or T _ N _0 is far smaller than T _ M _0 (which is equivalent to that a difference between the first normal running statistical number and the second normal running statistical number in the embodiment of the present invention is greater than the preset difference threshold), the load-related startup module generates an abnormality or a crash, and the server may prepare to issue X =0 (the impermissible application is permitted to load the startup module program during startup after the preset statistical period) and wait for the client to pull the latest configuration to close the related load logic next time.
An embodiment of the present invention provides an anomaly monitoring device for an application program, and referring to fig. 7, fig. 7 is a schematic diagram of an internal structure of an anomaly monitoring device for an application program according to an embodiment of the present invention, where the anomaly monitoring device 70 includes:
a first obtaining module 71, configured to obtain running data of a starting module program when detecting that an application program is started and receiving an instruction that the starting module program is loaded, where a loaded sequence of the starting module program is prior to a reporting management module program, and the starting module program and the reporting management module program are both subroutines of the application program;
the first execution module 72 is configured to perform a first detection on whether the start module program runs abnormally according to the running data;
the first execution module 72 is further configured to send an operation exception warning instruction to the server by reporting the management module program if the detection result of the first detection is that the starting module program is abnormal in operation;
the first executing module 72 is further configured to send a normal operation instruction to the server by reporting the management module program if the detection result of the first detection indicates that the starting module program operates normally.
An embodiment of the present invention provides an anomaly monitoring device for an application program, referring to fig. 8, where fig. 8 is a second schematic diagram of an internal structure of the anomaly monitoring device for the application program according to the embodiment of the present invention, and the anomaly monitoring device 80 includes:
the second obtaining module 81 is configured to obtain an abnormal operation alarm instruction sent by the client within a preset statistical time period, and count the abnormal alarm instruction to obtain the abnormal alarm statistical frequency; the method comprises the steps that an application program running on a client loads a starting module program when being started, and an exception warning instruction is used for indicating that the loading starting module program runs abnormally;
a second execution module 82, configured to determine whether to permit the application program to load the start module program during starting after a preset statistical time period according to the abnormal alarm statistics times;
the second executing module 82 is further configured to, if the license application program loads the starting module program in starting after the preset statistical time period, send a license loading instruction to the client.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the second execution module 82 is further configured to, if the abnormal alarm statistics number does not exceed the preset warning number threshold, permit the application program to load the start module program in the starting process after the preset statistics time period;
the second executing module 82 is further configured to disallow the application program to load the starting module program in the starting process after the preset statistical time period if the abnormal alarm statistical number exceeds the preset alarm number threshold.
An embodiment of the present invention provides an anomaly monitoring device for an application program, as shown in fig. 9, where fig. 9 is a third schematic diagram of an internal structure of the anomaly monitoring device for an application program according to an embodiment of the present invention, and the anomaly monitoring device 90 includes:
the third obtaining module 91 is configured to obtain a normal operation instruction sent by the first client within a preset statistical time period, and count the normal operation instruction sent by the first client to obtain a first normal operation statistical frequency; the method comprises the steps that an application program running on a first client loads a starting module program when the application program is started, and a normal running instruction sent by the first client is used for indicating that the loading starting module program runs normally;
the third obtaining module 91 is further configured to obtain a normal operation instruction sent by the second client within a preset statistical time period, and count the normal operation instruction sent by the second client to obtain a second normal operation statistical frequency; the application program running on the second client does not load the starting module program when being started, and the normal running instruction sent by the second client is used for indicating that the application program running on the second client runs normally;
a third executing module 92, configured to determine whether to allow the application program running on the first client to load the starting module program during starting after a preset statistical time period according to the first normal running statistical frequency and the second normal running statistical frequency;
the third executing module 92 is further configured to, if the application program running on the first client is permitted to load the starting module program in the starting process after the preset statistical time period, send a permission loading instruction to the first client.
The anomaly monitoring device for the application program provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 1 to fig. 6, and achieve the same technical effect, and is not described here again to avoid repetition.
Referring to fig. 10, fig. 10 is a schematic diagram of an internal structure of an electronic device 100 according to an embodiment of the present invention, and the electronic device 100 includes a processor 101, a memory 102, and a program or an instruction stored in the memory 102 and executable on the processor 101, where the program or the instruction implements, when executed by the processor, steps in an abnormality monitoring method of any application program according to the present invention.
The embodiment of the present invention provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the embodiment of the method for monitoring an abnormality of an application program, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. An anomaly monitoring method of an application program is applied to a client, and is characterized by comprising the following steps:
when detecting that an application program is started and receiving an instruction that a starting module program is loaded, acquiring running data of the starting module program, wherein the loaded sequence of the starting module program is prior to a reporting management module program, and the starting module program and the reporting management module program are subprograms of the application program;
performing first detection on whether the starting module program runs abnormally according to the running data;
if the detection result of the first detection is that the starting module program is abnormal in operation, an abnormal operation alarm instruction is sent to a server side through the reporting management module program;
and if the detection result of the first detection indicates that the starting module program operates normally, sending a normal operation instruction to the server side through the reporting management module program.
2. An anomaly monitoring method of an application program is applied to a server side, and is characterized by comprising the following steps:
acquiring an abnormal operation alarm instruction sent by a client in a preset statistical time period, and counting the abnormal alarm instruction to obtain abnormal alarm statistical times; the application program running on the client loads a starting module program when being started, and the abnormity warning instruction is used for indicating that the loading starting module program runs abnormally;
determining whether to permit the application program to load the starting module program in the starting process after the preset counting time period or not according to the abnormal alarm counting times;
and if the application program is permitted to load the starting module program in the starting process after the preset statistical time period, sending a permission loading instruction to the client.
3. The abnormality monitoring method for an application program according to claim 2, characterized in that:
determining whether to permit the application program to load the starting module program in the starting process after the preset statistical time period according to the abnormal alarm statistical times, wherein the method comprises the following steps:
if the abnormal alarm counting times do not exceed a preset alarm counting time threshold, allowing the application program to load the starting module program in the starting process after the preset counting time period;
and if the abnormal alarm counting times exceed the preset warning time threshold, not allowing the application program to load the starting module program in the starting process after the preset counting time period.
4. An anomaly monitoring method of an application program is applied to a server side, and is characterized by comprising the following steps:
acquiring a normal operation instruction sent by a first client within a preset counting time period, and counting the normal operation instruction sent by the first client to obtain a first normal operation counting number; the method comprises the steps that an application program running on a first client loads a starting module program when the application program is started, and a normal running instruction sent by the first client is used for indicating that the loading starting module program runs normally;
acquiring a normal operation instruction sent by a second client within a preset statistical time period, and counting the normal operation instruction sent by the second client to obtain a second normal operation statistical frequency; the application program running on the second client does not load a starting module program when being started, and the normal running instruction sent by the second client is used for indicating that the application program running on the second client runs normally;
determining whether to permit the application program running on the first client to load the starting module program in the starting process after the preset counting time period according to the first normal running counting times and the second normal running counting times;
and if the application program running on the first client is permitted to load the starting module program in the starting process after the preset statistical time period, sending a permission loading instruction to the first client.
5. The abnormality monitoring method for an application program according to claim 4, characterized in that:
determining whether to permit the application program running on the first client to load the starting module program in the starting process after the preset statistical time period according to the first normal running statistical number and the second normal running statistical number, wherein the determining comprises the following steps:
if the difference between the first normal running statistical frequency and the second normal running statistical frequency is smaller than or equal to a preset difference threshold, allowing the application program running on the first client to load the starting module program in the starting process after the preset statistical time period;
if the difference between the first normal running statistical frequency and the second normal running statistical frequency is larger than the preset difference threshold, the application program running on the first client is not allowed to load the starting module program in the starting process after the preset statistical time period.
6. An anomaly monitoring device for an application program, comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring running data of a starting module program when detecting that the application program is started and receiving an instruction that the starting module program is loaded, the loaded sequence of the starting module program is prior to a reporting management module program, and the starting module program and the reporting management module program are subprograms of the application program;
the first execution module is used for carrying out first detection on whether the starting module program runs abnormally according to the running data;
the first execution module is further configured to send an operation exception warning instruction to a server through the reporting management module program if the detection result of the first detection indicates that the starting module program is abnormal in operation;
the first execution module is further configured to send a normal operation instruction to the server through the reporting management module program if the detection result of the first detection indicates that the starting module program operates normally.
7. An anomaly monitoring device for an application program, comprising:
the second acquisition module is used for acquiring an abnormal operation alarm instruction sent by the client in a preset statistical time period, and counting the abnormal alarm instruction to obtain abnormal alarm statistical times; the application program running on the client loads a starting module program when being started, and the abnormity warning instruction is used for indicating that the loading starting module program runs abnormally;
the second execution module is used for determining whether to permit the application program to load the starting module program in the starting process after the preset counting time period or not according to the abnormal alarm counting times;
the second execution module is further configured to send a permission loading instruction to the client if the application program is permitted to load the starting module program during starting after the preset statistical time period.
8. An anomaly monitoring device for an application program, comprising:
the third acquisition module is used for acquiring a normal operation instruction sent by the first client within a preset statistical time period, and counting the normal operation instruction sent by the first client to obtain a first normal operation statistical frequency; the method comprises the steps that an application program running on a first client loads a starting module program when the application program is started, and a normal running instruction sent by the first client is used for indicating that the loading starting module program runs normally;
the third obtaining module is further configured to obtain a normal operation instruction sent by the second client within a preset statistical time period, and count the normal operation instruction sent by the second client to obtain a second normal operation statistical frequency; the application program running on the second client does not load a starting module program when being started, and the normal running instruction sent by the second client is used for indicating that the application program running on the second client runs normally;
a third execution module, configured to determine whether to permit the application program running on the first client to load the start module program during starting after the preset statistical time period according to the first normal running statistical frequency and the second normal running statistical frequency;
the third execution module is further configured to send a permission loading instruction to the first client if the application program permitted to run on the first client is loaded during starting after the preset statistical time period.
9. An electronic device, characterized in that: comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which program or instructions, when executed by the processor, implement the steps in the method of anomaly monitoring of an application program according to any one of claims 1 to 5.
10. A readable storage medium, characterized by: the readable storage medium stores thereon a program or instructions which, when executed by a processor, implement the steps in the anomaly monitoring method of an application program according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210454557.7A CN114564369B (en) | 2022-04-28 | 2022-04-28 | Application program abnormity monitoring method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210454557.7A CN114564369B (en) | 2022-04-28 | 2022-04-28 | Application program abnormity monitoring method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114564369A true CN114564369A (en) | 2022-05-31 |
| CN114564369B CN114564369B (en) | 2022-08-02 |
Family
ID=81720783
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210454557.7A Active CN114564369B (en) | 2022-04-28 | 2022-04-28 | Application program abnormity monitoring method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114564369B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5237688A (en) * | 1987-11-18 | 1993-08-17 | International Business Machines Corporation | Software packaging structure having hierarchical replaceable units |
| CA2222349A1 (en) * | 1997-11-27 | 1999-05-27 | Ibm Canada Limited-Ibm Canada Limitee | Method and apparatus for using stored procedures with a database management system |
| CN101384054A (en) * | 2007-09-04 | 2009-03-11 | 中兴通讯股份有限公司 | Method for network exception condition monitoring through performance data |
| CN107729167A (en) * | 2016-08-10 | 2018-02-23 | 腾讯科技（深圳）有限公司 | Using abnormality eliminating method and device |
| CN108667855A (en) * | 2018-07-19 | 2018-10-16 | 百度在线网络技术（北京）有限公司 | Network traffic anomaly monitor method, apparatus, electronic equipment and storage medium |
| CN109542724A (en) * | 2018-11-14 | 2019-03-29 | 北京达佳互联信息技术有限公司 | Application exception processing method, device, electronic equipment and storage medium |
| CN110851204A (en) * | 2019-11-08 | 2020-02-28 | 北京字节跳动网络技术有限公司 | Application starting method and device and application packaging method and device |
| CN111984452A (en) * | 2020-08-26 | 2020-11-24 | 网易（杭州）网络有限公司 | Program failure detection method, program failure detection device, electronic device, and storage medium |
-
2022
- 2022-04-28 CN CN202210454557.7A patent/CN114564369B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5237688A (en) * | 1987-11-18 | 1993-08-17 | International Business Machines Corporation | Software packaging structure having hierarchical replaceable units |
| CA2222349A1 (en) * | 1997-11-27 | 1999-05-27 | Ibm Canada Limited-Ibm Canada Limitee | Method and apparatus for using stored procedures with a database management system |
| CN101384054A (en) * | 2007-09-04 | 2009-03-11 | 中兴通讯股份有限公司 | Method for network exception condition monitoring through performance data |
| CN107729167A (en) * | 2016-08-10 | 2018-02-23 | 腾讯科技（深圳）有限公司 | Using abnormality eliminating method and device |
| CN108667855A (en) * | 2018-07-19 | 2018-10-16 | 百度在线网络技术（北京）有限公司 | Network traffic anomaly monitor method, apparatus, electronic equipment and storage medium |
| CN109542724A (en) * | 2018-11-14 | 2019-03-29 | 北京达佳互联信息技术有限公司 | Application exception processing method, device, electronic equipment and storage medium |
| CN110851204A (en) * | 2019-11-08 | 2020-02-28 | 北京字节跳动网络技术有限公司 | Application starting method and device and application packaging method and device |
| CN111984452A (en) * | 2020-08-26 | 2020-11-24 | 网易（杭州）网络有限公司 | Program failure detection method, program failure detection device, electronic device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114564369B (en) | 2022-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110888783B (en) | Method and device for monitoring micro-service system and electronic equipment | |
| CN108508874B (en) | Method and device for monitoring equipment fault | |
| CN110545276A (en) | threat event warning method and device, warning equipment and machine-readable storage medium | |
| CN114356499A (en) | Kubernetes cluster alarm root cause analysis method and device | |
| EP2354945A1 (en) | Noisy monitor detection and intermittent fault isolation | |
| CN112783725A (en) | Index acquisition method and device | |
| CN110674149B (en) | Service data processing method and device, computer equipment and storage medium | |
| CN111859399A (en) | Vulnerability detection method and device based on oval | |
| JP2004145536A (en) | Management system | |
| CN106294364B (en) | Method and device for realizing web crawler to capture webpage | |
| CN114564369B (en) | Application program abnormity monitoring method and device, electronic equipment and storage medium | |
| CN115794479B (en) | Log data processing method and device, electronic equipment and storage medium | |
| CN110704313A (en) | Memory leakage detection method and device for JAVA virtual machine | |
| CN114610560B (en) | System abnormality monitoring method, device and storage medium | |
| CN114083987B (en) | Correction method and device for battery monitoring parameters and computer equipment | |
| CN114036032A (en) | Real-time program monitoring method and device | |
| CN110365520B (en) | Method, device and equipment for polling nodes in distributed system | |
| CN111857689A (en) | Framework, function configuration method of framework, terminal and storage medium | |
| CN113138872A (en) | Abnormal processing device and method for database system | |
| CN111813872A (en) | Fault troubleshooting model generation method, device and equipment | |
| JP2003345629A (en) | System monitor device, system monitoring method used for the same, and program therefor | |
| CN115514630B (en) | Self-adaptive fault analysis method, device, equipment and storage medium | |
| CN110598415B (en) | Security vulnerability emergency response triggering judgment method and device | |
| CN114095391B (en) | Data detection method, baseline model construction method and electronic equipment | |
| CN114363150B (en) | Network card connectivity monitoring method and device of server cluster |
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 |