CN113312263B - Anomaly monitoring method and device - Google Patents

Anomaly monitoring method and device Download PDF

Info

Publication number
CN113312263B
CN113312263B CN202110629730.8A CN202110629730A CN113312263B CN 113312263 B CN113312263 B CN 113312263B CN 202110629730 A CN202110629730 A CN 202110629730A CN 113312263 B CN113312263 B CN 113312263B
Authority
CN
China
Prior art keywords
page
information
control
list
application program
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
CN202110629730.8A
Other languages
Chinese (zh)
Other versions
CN113312263A (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.)
Vivo Mobile Communication Hangzhou Co Ltd
Original Assignee
Vivo Mobile Communication Hangzhou 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 Vivo Mobile Communication Hangzhou Co Ltd filed Critical Vivo Mobile Communication Hangzhou Co Ltd
Priority to CN202110629730.8A priority Critical patent/CN113312263B/en
Publication of CN113312263A publication Critical patent/CN113312263A/en
Application granted granted Critical
Publication of CN113312263B publication Critical patent/CN113312263B/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/36Preventing errors by testing or debugging software
    • G06F11/3604Software analysis for verifying properties of programs
    • G06F11/3612Software analysis for verifying properties of programs by runtime analysis

Abstract

The application discloses an anomaly monitoring method and device, and belongs to the technical field of fault detection. The abnormality monitoring method comprises the steps of receiving first input of a user to a first control in an application program; in response to the first input, determining whether response information is monitored within a preset time period; the response information comprises at least one item of page opening information, window pop-up information, message pop-up information or layout change information; and uploading abnormal information generated when the first control is operated to a server under the condition that the response information is not monitored.

Description

Anomaly monitoring method and device
Technical Field
The application belongs to the technical field of fault detection, and particularly relates to an anomaly monitoring method and device.
Background
With the continuous popularization of intelligent electronic devices, more and more APPs (applications) can be installed on the intelligent electronic devices, and each Application is provided with a large number of controls. Therefore, how to monitor the possible abnormal situation when the user triggers the control in time becomes a key problem in the APP optimization process.
In the prior art, a main method for performing anomaly monitoring is to design different anomaly monitoring logics for different service scenes from a service perspective, that is, to predict an abnormal situation that may occur in a service, and to report related anomaly information to a server for the possible abnormal situation. For example, for an account login interface in an APP, when a user clicks a login button, a determination is made according to specific conditions of a login service, such as whether a password is wrong or not, whether an account has a risk or not, and then, according to a specific abnormal condition, different abnormal monitoring logics are used to report abnormal information to a server. In addition, the abnormal monitoring code is fused with the service code, so that the maintenance difficulty and the cost are high when the abnormal monitoring code is maintained subsequently.
Disclosure of Invention
The embodiment of the application aims to provide an anomaly monitoring method and an anomaly monitoring device, which can solve the problems that the existing anomaly monitoring logic has no universality, cannot monitor potential anomaly conditions, and has higher subsequent maintenance difficulty and higher cost on corresponding monitoring codes.
In a first aspect, an embodiment of the present application provides an anomaly monitoring method, including:
receiving a first input of a user to a first control in an application program;
determining whether response information is monitored within a preset time period in response to the first input; wherein the response information comprises at least one item of page opening information, window pop-up information, message pop-up information or layout change information;
and uploading abnormal information generated when the first control is operated to a server under the condition that the response information is not monitored.
In a second aspect, an embodiment of the present application provides an anomaly monitoring device, including:
the input receiving module is used for receiving first input of a user to a first control in the application program;
the information monitoring module is used for responding to the first input and determining whether response information is monitored in a preset time period; wherein the response information comprises at least one item of page opening information, window pop-up information, message pop-up information or layout change information;
and the information uploading module is used for uploading the abnormal information generated when the first control is operated to a server under the condition that the response information is not monitored.
In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect.
In a fourth aspect, embodiments of the present application provide a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect.
In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.
In the embodiment of the application, from the input-response perspective, that is, after a first input of a user to a first control in an application program is received, it is determined whether at least one piece of response information including page opening information, window pop-up information, message pop-up information, or layout change information is monitored within a preset time period, and abnormal information is uploaded if the response information is not monitored. Therefore, under normal conditions, the application program inevitably has a certain response after the user inputs the information every time, and therefore, if any response information is not monitored, the abnormal condition can be judged to have a high probability, and the abnormal condition can be reported to the server, further, the abnormal monitoring can be carried out without determining which specific service the abnormal condition belongs to, and the unpredictable abnormal condition can also be monitored and reported, so that the abnormal monitoring logic of the embodiment of the application has universality and can identify the potential abnormal condition. In addition, because the abnormal monitoring code is not associated with the service code, the maintenance difficulty of the abnormal monitoring code is low in the embodiment of the application, and the code maintenance cost is reduced.
Drawings
FIG. 1 is one of the flow diagrams of an anomaly monitoring method shown in accordance with an exemplary embodiment;
FIG. 2 is a second flowchart illustrating an anomaly monitoring method according to an exemplary embodiment;
FIG. 3 is a third flowchart illustrating an anomaly monitoring method according to an exemplary embodiment;
FIG. 4 is a block diagram illustrating the structure of an anomaly monitoring device in accordance with an exemplary embodiment;
FIG. 5 is a block diagram illustrating the structure of an electronic device in accordance with an exemplary embodiment;
fig. 6 is a schematic diagram of a hardware structure of an electronic device implementing an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present disclosure.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/", and generally means that the former and latter related objects are in an "or" relationship.
The anomaly monitoring method, the anomaly monitoring device, the electronic device, and the storage medium provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings and application scenarios thereof.
The anomaly monitoring method provided by the application can be applied to a scene for monitoring the abnormal condition occurring when the control is input. In addition, according to the abnormality monitoring method provided by the embodiment of the application, the execution main body may be an abnormality monitoring device, or a control module used for executing the abnormality monitoring method in the abnormality monitoring device. In the embodiment of the present application, an example in which an abnormality monitoring device executes an abnormality monitoring method is taken as an example, to describe the abnormality monitoring method provided in the embodiment of the present application.
FIG. 1 is a flow chart illustrating a method of anomaly monitoring in accordance with an exemplary embodiment.
As shown in fig. 1, the anomaly monitoring method may include the steps of:
step 110, receiving a first input of a user to a first control in an application program.
Here, the first control may be a control set on any page in the application program, and the control may specifically be a button, or may also be another control supporting user input, which is not limited herein. The first input may be a user click input to the first control, for example, on a login page of a chat APP, the user may click a login button, and thus, the device may receive the user click input to the login button.
In response to the first input, it is determined whether response information is monitored within a preset time period, step 120.
Wherein the response information includes at least one of page open information, window pop-up information, message pop-up information, or layout change information. Specifically, the page opening information may be response information for opening a new page based on the currently displayed page; the window pop-up information may be response information received when a new display window is popped up based on the currently displayed page; the message pop-up information may be response information received when a page pop-up prompt message is currently displayed, wherein the pop-up prompt message may be, for example, pop-up Toast; the layout change information may be, for example, response information received when the position of any control in the currently displayed page changes, or the image-text content in the page changes, or the like.
It should be noted that the difference between the window and the message is that the window needs to be closed by manually clicking a close button, and the message automatically disappears after a certain period of time without manually clicking.
In addition, a reaction time, that is, a preset time period, may be set in consideration of the problem of application stuttering. The preset time period may be a preset length of time after the first input is received, for example, the response information is monitored within 3 seconds after the user clicks the button. Specifically, the detection process may be postponed by starting a delay task.
In a specific example, after the user clicks the button, the device may detect whether any one or more of a new page jump, a pop-up window, a pop-up message, and a layout change has occurred within 3 seconds after the button is clicked, and if yes, it is determined that the response information is monitored, and if not, it is determined that the response information is not monitored.
In an optional embodiment, in the case that the response information includes at least one of page opening information, window pop-up information, or message pop-up information, the step 120 may specifically include:
acquiring a first page list of a system; the first page list is used for recording page data of opened pages in the system;
creating a second page list, and copying page data in the first page list into the second page list; the data adding strategy corresponding to the second page list is set to send response information under the condition of adding page data;
replacing the first page list with a second page list;
and monitoring whether the second page list sends response information or not within a preset time period.
Here, for an Android (Android) system, a page list, that is, a first page list, is maintained in the system, and the page list is mainly used for recording page data of all currently opened pages in the system, and whenever a new page, window, or message is opened, corresponding page data is added to the page list.
Because the original page list in the system, that is, the first page list, has no function of notifying when data is added, in the embodiment of the present application, the second page list may be created to replace the first page list, and the code of the data addition interface corresponding to the second page list is modified, so that the second page list can send a notification, that is, send response information, to the outside when page data is added each time. Therefore, whether the abnormal condition occurs can be determined only by monitoring whether the second page list sends the response information in the preset time period.
The method for obtaining the first page list of the system may be to obtain a page list corresponding to a native Window of the system by reflection using a Window Manager (Window Manager).
Therefore, the second page list is created to replace the first page list of the system, so that the response information can be sent in time when new page data is added to the list, and whether the abnormality occurs can be determined only by monitoring whether the second page list sends the response information within a preset time period.
In an optional implementation manner, in the case that the response information includes page opening information, the step 120 may specifically include:
and determining whether page opening information is monitored in a preset time period or not by utilizing a page life cycle callback interface.
Here, when an application program is opened, an Android global application lifecycle (application lifecycle) may be registered first, and then a page lifecycle callback interface (ActivityLife cyclecallback) is used to monitor whether a new page is opened within a preset time period, and whenever a new page is opened, the application layer may receive a corresponding notification, that is, monitor page opening information.
Therefore, the page opening information is monitored in the preset time period by utilizing the page life cycle callback interface, so that the monitoring of the response mode of the new page jump can be realized.
And step 130, uploading abnormal information generated when the first control is operated to a server under the condition that the response information is not monitored.
Here, the exception information generated when the first control is run may specifically include a name and a time of a page where the first control is located when the exception is generated, and a name of the first control.
Exemplarily, under the condition that the response information is not monitored, it is indicated that an abnormal condition may occur, and at this time, information related to the first control may be reported to the server as abnormal information; otherwise, when the response information is monitored, it is indicated that the input of the user is responded, and no abnormal condition occurs, and at this time, the abnormal information may not be reported.
In addition, when the number of the abnormal information corresponding to the same control received by the server is lower than a set value, the abnormal information can be regarded as the abnormal response caused by the personal equipment of the user, and therefore the abnormal information can not be processed; when the quantity of the abnormal information corresponding to the same control received by the server is accumulated to be higher than a set value, an alarm can be automatically sent to background maintenance personnel of the application program, and the background maintenance personnel can be informed to check and maintain the control.
Therefore, from the input-response perspective, that is, after a first input of a user to a first control in an application program is received, whether response information including at least one of page opening information, window pop-up information, message pop-up information or layout change information is monitored within a preset time period is determined, and in the case that the response information is not monitored, abnormal information is uploaded. Therefore, under normal conditions, the application program inevitably has a certain response after the user inputs the information every time, and therefore, if any response information is not monitored, the abnormal condition can be judged to have a high probability, and the abnormal condition can be reported to the server, further, the abnormal monitoring can be carried out without determining which specific service the abnormal condition belongs to, and the unpredictable abnormal condition can also be monitored and reported, so that the abnormal monitoring logic of the embodiment of the application has universality and can identify the potential abnormal condition. In addition, the abnormal monitoring code is not associated with the service code, so that the maintenance difficulty of the abnormal monitoring code is low in the embodiment of the application, and the code maintenance cost is reduced.
Based on this, in an optional implementation manner, after the step 110, the abnormality monitoring method provided in the embodiment of the present application may further include:
acquiring abnormal information generated when a first control is operated;
storing the exception information in a cache region;
correspondingly, before the abnormal information generated when the first control is operated is uploaded to the server, the abnormal monitoring method provided by the embodiment of the application further includes:
and acquiring exception information from the cache region.
Here, whenever the user triggers the first control, the exception information of the first control may be stored in the buffer, so that the exception information related to the first control may be directly uploaded when an exception condition without response occurs.
In a specific example, when a button is clicked, information related to the button (including a current page name, a button name, and the like) may be collected and temporarily stored in a buffer, then a delay task is started, the count is counted down for 3 seconds, and if no response is found within 3 seconds, the information recorded in the buffer is automatically read after 3 seconds, and is reported to the server.
It should be noted that after the abnormal information of the first control is obtained from the cache region and uploaded to the server, the abnormal information of the first control in the cache region may be cleared when the confirmation information returned by the server is received.
Therefore, the abnormal information of the first control is cached in the cache region, so that the information related to the control can be conveniently and timely acquired and reported when the abnormal condition occurs.
In an optional implementation manner, in the case that the response information is monitored, the abnormality monitoring method provided in the embodiment of the present application may further include:
and clearing the abnormal information stored in the cache region.
In a specific example, when a new page, a pop-up window, a pop-up message, or a layout change of the current interface occurs after the button is clicked within 3 seconds, the information record in the buffer area is deleted, the delay task is cancelled, and the current anomaly monitoring process is ended.
Therefore, under the condition that the response is confirmed, the abnormal information stored in the cache region is cleared in time, and the memory resource can be saved.
To better describe the above solution, based on the above embodiments, as a specific example, as shown in fig. 2, the anomaly monitoring method may include steps 210 and 220, which are explained in detail below.
Step 210, clicking a button;
step 220, writing the information corresponding to the button into a cache region;
step 230, counting down for 3 seconds, and determining whether response information is monitored within 3 seconds, if yes, executing step 240, and if not, executing step 250;
step 240, clearing the cache area and canceling countdown;
and step 250, uploading the information in the cache region to a server after counting down for 3 seconds.
Therefore, whether the control triggering process is abnormal or not can be judged from the point of click-response, so that the universality is higher, and meanwhile, the code maintenance cost is reduced.
In addition, before performing the anomaly monitoring, an anomaly monitoring code needs to be inserted into a corresponding control input event, so as to implement the anomaly monitoring process by running the anomaly monitoring code. In one possible embodiment, as shown in fig. 3, before step 110, the anomaly monitoring method provided in the embodiment of the present application may further include: the steps 1101-1102 are specifically as follows:
step 1101, acquiring an event processing function corresponding to a control input event in at least one page opened in an application program.
At least one page comprises a first control.
Here, the control input event may be an input event that can trigger the first control, for example, in a case where the first input to the first control is clicking the first control, the control input event may be a clicking event.
For example, all pages opened in the application program may be first acquired, and then, a control that can be triggered in each page, for example, all buttons that can be clicked, may be automatically found, so that an event handling function of a control input event corresponding to each control, for example, an event handling function corresponding to a click event, may be acquired, and then, an anomaly monitoring code is automatically added to the corresponding event handling function.
It should be noted that the addition process of the exception monitoring code may be permanent addition or temporary addition, that is, the exception monitoring code is added once a page is opened, and when the page is closed or the application program is closed, the exception monitoring code is automatically deleted again, which is not limited herein.
In an optional implementation manner, the step 1101 may specifically include:
acquiring a first page opened in an application program by using a page life cycle callback interface;
acquiring an application program interface corresponding to the first page;
and traversing at least one opened page in the application program interface, and acquiring an event processing function corresponding to the control input event in the at least one page.
Here, in the Android system, when a new page is opened, the system sends a message to the outside, and at this time, the message may be monitored through the page lifecycle callback interface, and when a page is opened, the currently opened page (i.e., Activity) may be acquired.
In addition, in the Android system, all page layouts are derived from one root node nest, wherein the root node can be the largest interface window corresponding to the application, and each child node under the root node can be each page opened in the application. Therefore, the first page which is opened currently can be obtained by calling the page life cycle callback interface, the corresponding application program interface, namely the root node, is obtained through the first page, all child nodes under the root node are sequentially traversed, namely all pages which are opened in the application program interface are traversed, and when a click event exists in a certain child node, an event processing function corresponding to the click event can be obtained.
Therefore, the application program interface corresponding to the page can be obtained through the currently opened first page, all opened pages in the application program interface are sequentially traversed, the event processing function corresponding to the control input event in each page can be obtained, and a foundation is provided for automatic addition of the abnormal monitoring code.
Step 1102, add exception monitoring code before event handling code in the event handling function.
The anomaly monitoring code is used for realizing the anomaly monitoring method.
For example, after the event processing flow corresponding to the control input event in each page is obtained, an exception monitoring code may be added before the original processing flow, and finally the combined flow is reset to the corresponding control.
In this way, by acquiring the event processing function corresponding to the control input event in each opened page and further adding the exception monitoring code to the event processing function, the exception condition can be monitored when the event processing function is used for processing the control input event after the user triggers the control. In addition, the mode of automatically adding codes can save labor and reduce the development cost of the abnormality monitoring function.
Based on the same inventive concept, the application also provides an abnormality monitoring device. The anomaly monitoring device provided by the embodiment of the present application is described in detail below with reference to fig. 4.
Fig. 4 is a block diagram illustrating a configuration of an anomaly monitoring device according to an exemplary embodiment.
As shown in fig. 4, the abnormality monitoring apparatus 400 may include:
the input receiving module 401 is configured to receive a first input of a first control in an application program from a user;
an information monitoring module 402, configured to determine whether response information is monitored within a preset time period in response to a first input; the response information comprises at least one item of page opening information, window pop-up information, message pop-up information or layout change information;
and an information uploading module 403, configured to upload, to the server, abnormal information generated when the first control is operated when the response information is not monitored.
The following describes the abnormality monitoring device 400 in detail, specifically as follows:
in one embodiment, in a case that the response information includes at least one of page opening information, window pop-up information, or message pop-up information, the information monitoring module 402 may specifically include:
the list acquisition submodule is used for acquiring a first page list of the system; the first page list is used for recording page data of opened pages in the system;
the list creating submodule is used for creating a second page list and copying the page data in the first page list into the second page list; the data adding strategy corresponding to the second page list is set to send response information under the condition of adding page data;
the list replacing submodule is used for replacing the first page list with a second page list;
and the information monitoring submodule is used for monitoring whether the second page list sends response information or not in a preset time period.
In one embodiment, in a case that the response information includes page opening information, the information monitoring module 402 may specifically include:
and the interface monitoring submodule is used for calling back the interface by utilizing the life cycle of the page and determining whether page opening information is monitored in a preset time period.
In one embodiment, the anomaly monitoring device 400 may further include:
the information acquisition module is used for acquiring abnormal information generated when a first control in the application program is operated after receiving first input of a user to the first control;
the information cache module is used for storing the abnormal information in a cache region;
the device still includes:
and the information reading module is used for acquiring the abnormal information from the buffer before uploading the abnormal information generated when the first control is operated to the server.
In one embodiment, in the case that the response information is monitored, the abnormality monitoring apparatus 400 may further include:
and the cache clearing module is used for clearing the abnormal information stored in the cache region.
In one embodiment, the anomaly monitoring device 400 may further include:
the function acquisition module is used for acquiring an event processing function corresponding to a control input event in at least one opened page in the application program before receiving first input of a user to a first control in the application program; wherein at least one page comprises a first control;
the code adding module is used for adding an exception monitoring code before an event processing code in the event processing function; the abnormity monitoring code is used for realizing the abnormity monitoring method.
In one embodiment, the function obtaining module may specifically include:
the page acquisition sub-module acquires a first page opened in the application program by using a page life cycle callback interface;
the interface acquisition submodule is used for acquiring an application program interface corresponding to the first page;
and the page traversal submodule is used for traversing at least one page running in the application program interface and acquiring an event processing function corresponding to the control input event in the at least one page.
Therefore, from the input-response perspective, that is, after a first input of a user to a first control in an application program is received, whether response information including at least one of page opening information, window pop-up information, message pop-up information or layout change information is monitored within a preset time period is determined, and in the case that the response information is not monitored, abnormal information is uploaded. Therefore, under normal conditions, the application program inevitably has a certain response after the user inputs the information every time, and therefore, if any response information is not monitored, the abnormal condition can be judged to have a high probability, and the abnormal condition can be reported to the server, further, the abnormal monitoring can be carried out without determining which specific service the abnormal condition belongs to, and the unpredictable abnormal condition can also be monitored and reported, so that the abnormal monitoring logic of the embodiment of the application has universality and can identify the potential abnormal condition. In addition, the abnormal monitoring code is not associated with the service code, so that the maintenance difficulty of the abnormal monitoring code is low in the embodiment of the application, and the code maintenance cost is reduced.
The abnormality monitoring device in the embodiment of the present application may be a device, and may also be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a Network Attached Storage (NAS), a personal computer (personal computer, PC), a Television (TV), a teller machine, a self-service machine, and the like, and the embodiments of the present application are not limited in particular.
The abnormality monitoring device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.
The anomaly monitoring device provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 1 to fig. 3, and is not described here again to avoid repetition.
Optionally, as shown in fig. 5, an electronic device 500 is further provided in this embodiment of the present application, and includes a processor 501, a memory 502, and a program or an instruction stored in the memory 502 and capable of being executed on the processor 501, where the program or the instruction is executed by the processor 501 to implement each process of the foregoing abnormality monitoring method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
It should be noted that the electronic device in the embodiment of the present application includes the mobile electronic device and the non-mobile electronic device described above.
Fig. 6 is a schematic diagram of a hardware structure of an electronic device implementing an embodiment of the present application.
The electronic device 600 includes, but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, a processor 610, and the like.
Those skilled in the art will appreciate that the electronic device 600 may further comprise a power source (e.g., a battery) for supplying power to the various components, and the power source may be logically connected to the processor 610 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The electronic device structure shown in fig. 6 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is omitted here.
The user input unit 607 is configured to receive a first input of a user to a first control in an application program;
a processor 610 for determining, in response to a first input, whether response information is monitored for a preset time period;
the network module 602 is configured to upload, to a server, abnormal information generated when the first control is operated when the response information is not monitored.
Therefore, from the input-response perspective, that is, after a first input of a user to a first control in an application program is received, whether response information including at least one of page opening information, window pop-up information, message pop-up information or layout change information is monitored within a preset time period is determined, and in the case that the response information is not monitored, abnormal information is uploaded. Therefore, under normal conditions, the application program inevitably has a certain response after the user inputs the information every time, and therefore, if any response information is not monitored, the abnormal condition can be judged to have a high probability, and the abnormal condition can be reported to the server, further, the abnormal monitoring can be carried out without determining which specific service the abnormal condition belongs to, and the unpredictable abnormal condition can also be monitored and reported, so that the abnormal monitoring logic of the embodiment of the application has universality and can identify the potential abnormal condition. In addition, because the abnormal monitoring code is not associated with the service code, the maintenance difficulty of the abnormal monitoring code is low in the embodiment of the application, and the code maintenance cost is reduced.
Optionally, the processor 610 is further configured to obtain a first page list of the system; the first page list is used for recording page data of opened pages in the system; creating a second page list, and copying page data in the first page list into the second page list; replacing the first page list with a second page list;
the interface unit 608 is configured to listen whether the second page list sends the response information within a preset time period.
Optionally, the processor 610 is further configured to determine whether page opening information is monitored within a preset time period by using the page lifecycle callback interface.
Optionally, the processor 610 is further configured to obtain exception information generated when the first control is run; storing the exception information in a cache region; and acquiring exception information from the cache region.
Optionally, the processor 610 is further configured to clear the exception information stored in the cache.
Optionally, the processor 610 is further configured to obtain an event handling function corresponding to a control input event in at least one page that has been opened in the application program; exception monitoring code is added before event handling code in the event handling function.
Optionally, the processor 610 is further configured to obtain a first page opened in the application program by using a page lifecycle callback interface; acquiring an application program interface corresponding to the first page; and traversing at least one page running in the application program interface, and acquiring an event processing function corresponding to the control input event in the at least one page.
Therefore, whether the control triggering process is abnormal or not can be judged from the point of click-response, so that the universality is higher, and meanwhile, the code maintenance cost is reduced. In addition, the mode of automatically adding codes can save labor and reduce the development cost of the abnormality monitoring function.
It is to be understood that, in the embodiment of the present application, the input Unit 604 may include a Graphics Processing Unit (GPU) 6041 and a microphone 6042, and the Graphics Processing Unit 6041 processes image data of a still picture or a video obtained by an image capturing apparatus (such as a camera) in a video capturing mode or an image capturing mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 607 includes a touch panel 6071 and other input devices 6072. A touch panel 6071, also referred to as a touch screen. The touch panel 6071 may include two parts of a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein. The memory 609 may be used to store software programs as well as various data including, but not limited to, application programs and an operating system. The processor 610 may integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 610.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing abnormality monitoring method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.
The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the foregoing anomaly monitoring method embodiment, and can achieve the same technical effect, and the details are not repeated here to avoid repetition.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims (8)

1. An anomaly monitoring method, comprising:
receiving a first input of a user to a first control in an application program;
determining whether response information is monitored within a preset time period in response to the first input; wherein the response information comprises at least one item of page opening information, window pop-up information, message pop-up information or layout change information;
uploading abnormal information generated when the first control is operated to a server under the condition that the response information is not monitored;
wherein, in a case that the response information includes at least one of the page opening information, the window pop-up information, or the message pop-up information, the determining whether the response information is monitored within a preset time period includes:
acquiring a first page list of a system; the first page list is used for recording page data of opened pages in the system;
creating a second page list, and copying the page data in the first page list into the second page list; the data adding strategy corresponding to the second page list is set to send the response information under the condition of adding page data;
replacing the first page list with the second page list;
and monitoring whether the second page list sends the response information or not in the preset time period.
2. The method of claim 1, wherein after receiving a first input from a user to a first control in an application, the method further comprises:
acquiring abnormal information generated when the first control is operated;
storing the exception information in a cache region;
before uploading exception information generated when the first control is operated to a server, the method further comprises the following steps:
acquiring the abnormal information from the cache region;
in the case where the response information is monitored, the method further comprises:
and clearing the abnormal information stored in the cache region.
3. The method of claim 1, wherein prior to receiving a first input from a user to a first control in an application, the method further comprises:
acquiring an event processing function corresponding to a control input event in at least one opened page in the application program; wherein the first control is included in the at least one page;
adding exception monitoring code before event handling code in the event handling function; wherein the anomaly monitoring code is used to implement the anomaly monitoring method.
4. The method according to claim 3, wherein the obtaining of the event handling function corresponding to the control input event in the at least one page opened in the application program comprises:
acquiring a first page opened in the application program by using a page life cycle callback interface;
acquiring an application program interface corresponding to the first page;
and traversing at least one opened page in the application program interface, and acquiring an event processing function corresponding to the control input event in the at least one page.
5. An anomaly monitoring device, comprising:
the input receiving module is used for receiving first input of a user to a first control in the application program;
the information monitoring module is used for responding to the first input and determining whether response information is monitored in a preset time period; wherein the response information comprises at least one item of page opening information, window pop-up information, message pop-up information or layout change information;
the information uploading module is used for uploading abnormal information generated when the first control is operated to a server under the condition that the response information is not monitored;
wherein, in a case that the response information includes at least one of the page opening information, the window pop-up information, or the message pop-up information, the information monitoring module includes:
the list acquisition submodule is used for acquiring a first page list of the system; the first page list is used for recording page data of opened pages in the system;
the list creating submodule is used for creating a second page list and copying the page data in the first page list into the second page list; the data adding strategy corresponding to the second page list is set to send the response information under the condition of adding page data;
the list replacing submodule is used for replacing the first page list with the second page list;
and the information monitoring submodule is used for monitoring whether the second page list sends the response information or not in the preset time period.
6. The apparatus of claim 5, further comprising:
the information acquisition module is used for acquiring abnormal information generated when a first control in an application program is operated after receiving first input of a user to the first control;
the information cache module is used for storing the abnormal information in a cache region;
the device further comprises:
the information reading module is used for acquiring abnormal information generated when the first control is operated from the cache region before the abnormal information is uploaded to a server;
in the case where the response information is monitored, the apparatus further comprises:
and the cache clearing module is used for clearing the abnormal information stored in the cache region.
7. The apparatus of claim 5, further comprising:
the function acquisition module is used for acquiring an event processing function corresponding to a control input event in at least one opened page in an application program before receiving a first input of a user to a first control in the application program; wherein the first control is included in the at least one page;
the code adding module is used for adding an exception monitoring code before the event processing code in the event processing function; wherein the anomaly monitoring code is used to implement an anomaly monitoring method.
8. The apparatus of claim 7, wherein the function obtaining module comprises:
the page acquisition sub-module acquires a first page opened in the application program by using a page life cycle callback interface;
the interface acquisition submodule is used for acquiring an application program interface corresponding to the first page;
and the page traversal submodule is used for traversing at least one page running in the application program interface and acquiring an event processing function corresponding to the control input event in the at least one page.
CN202110629730.8A 2021-06-07 2021-06-07 Anomaly monitoring method and device Active CN113312263B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110629730.8A CN113312263B (en) 2021-06-07 2021-06-07 Anomaly monitoring method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110629730.8A CN113312263B (en) 2021-06-07 2021-06-07 Anomaly monitoring method and device

Publications (2)

Publication Number Publication Date
CN113312263A CN113312263A (en) 2021-08-27
CN113312263B true CN113312263B (en) 2022-06-21

Family

ID=77377487

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110629730.8A Active CN113312263B (en) 2021-06-07 2021-06-07 Anomaly monitoring method and device

Country Status (1)

Country Link
CN (1) CN113312263B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115941546A (en) * 2022-11-29 2023-04-07 重庆长安汽车股份有限公司 System interface monitoring method and device, electronic equipment and storage medium

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140082092A1 (en) * 2012-09-14 2014-03-20 International Business Machines Corporation Method of resolving a contact while composing text and/or email message
US10275344B2 (en) * 2014-03-03 2019-04-30 Lg Electronics Inc. Method for verifying operations for common application development of in-vehicle infotainment system and mobile terminal
CN104268055B (en) * 2014-09-01 2017-07-14 腾讯科技(深圳)有限公司 The monitoring method and device of a kind of program exception
CN105912309A (en) * 2015-10-30 2016-08-31 乐视移动智能信息技术(北京)有限公司 Method and device for prohibiting notification in application program window
CN109101297B (en) * 2017-06-20 2021-08-13 北京国双科技有限公司 Page identification method and device
CN109376071A (en) * 2018-09-03 2019-02-22 平安普惠企业管理有限公司 Application software exception feedback method, device, computer equipment and storage medium
CN109445966B (en) * 2018-11-06 2020-11-10 网易传媒科技(北京)有限公司 Event processing method, device, medium and computing equipment

Also Published As

Publication number Publication date
CN113312263A (en) 2021-08-27

Similar Documents

Publication Publication Date Title
CN111176960B (en) User operation behavior tracking method, device, equipment and storage medium
CN104426944B (en) Information feedback method, device and terminal
CN103530235A (en) Method and device for clearing internal storage in mobile terminal
CN111752793A (en) System abnormity monitoring method and device, computer equipment and storage medium
CN105095107A (en) Buffer memory data cleaning method and apparatus
CN104133687A (en) Method for handling unhandled notification event and portable terminal
CN107577471B (en) Application control method and mobile terminal
CN105893471B (en) Data processing method and electronic equipment
CN113312263B (en) Anomaly monitoring method and device
CN113992615B (en) Method and device for displaying withdrawal message, electronic equipment and storage medium
KR20180017168A (en) Method and apparatus for classifying virtual activities of mobile users
CN109086157B (en) Log tracking method and device, electronic equipment and storage medium
CN113114845B (en) Notification message display method and device
CN112416212B (en) Program access method, apparatus, electronic device and readable storage medium
CN112817817B (en) Buried point information query method, buried point information query device, computer equipment and storage medium
CN113791943A (en) Website real-time monitoring method, system, equipment and storage medium
CN106201464A (en) A kind of application icon processing method freezing application and mobile terminal
CN112764628B (en) Content display method, content display device, electronic equipment and storage medium
CN114626813A (en) Task backtracking method and device for scheduling platform, terminal and storage medium
CN113986190A (en) Application processing method and device and electronic equipment
CN113703993A (en) Service message processing method, device and equipment
CN111880698A (en) Information processing method and device of intelligent terminal, electronic equipment and storage medium
CN106155451B (en) Information processing method and electronic equipment
CN112650959A (en) Page loading duration statistical method, device, equipment and storage medium
CN112764638B (en) Display control method, electronic device, 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