CN111782464B - Webpage dynamic anomaly monitoring method and system - Google Patents
Webpage dynamic anomaly monitoring method and system Download PDFInfo
- Publication number
- CN111782464B CN111782464B CN202010576924.1A CN202010576924A CN111782464B CN 111782464 B CN111782464 B CN 111782464B CN 202010576924 A CN202010576924 A CN 202010576924A CN 111782464 B CN111782464 B CN 111782464B
- Authority
- CN
- China
- Prior art keywords
- data
- page
- rendering
- module
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000012544 monitoring process Methods 0.000 title claims abstract description 31
- 238000009877 rendering Methods 0.000 claims abstract description 85
- 230000004044 response Effects 0.000 claims abstract description 28
- 230000000977 initiatory effect Effects 0.000 claims abstract description 8
- 238000007689 inspection Methods 0.000 claims abstract description 6
- 238000001514 detection method Methods 0.000 claims description 42
- 230000008569 process Effects 0.000 claims description 19
- 230000005856 abnormality Effects 0.000 claims description 17
- 230000002159 abnormal effect Effects 0.000 claims description 11
- 238000013499 data model Methods 0.000 claims description 10
- 238000011160 research Methods 0.000 claims description 7
- 230000007246 mechanism Effects 0.000 claims description 5
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000012827 research and development Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
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/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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Abstract
The invention relates to the technical field of web page monitoring, and discloses a web page dynamic anomaly monitoring method and a web page dynamic anomaly monitoring system, wherein the method comprises the following steps: s1, initiating a request to an APP front-end page, and returning data required by page rendering; s2, executing returned data and completing the check of local rules; s3, constructing rendering for the page elements according to the returned data; s4, page rendering inspection, if rendering errors occur, entering a step S5, and if rendering errors do not occur, ending the flow; s5, triggering page fault alarm, and ending the whole flow. The problems that the current webpage loading problem is slow in response and adjustment and missing exists are solved, and the problems that the loading problem log cannot be captured and the feedback of the problems cannot be obtained are solved.
Description
Technical Field
The invention relates to the technical field of web page monitoring, in particular to a web page dynamic anomaly monitoring method and a web page dynamic anomaly monitoring system.
Background
In the development or loading process of the APP front-end page, the problems of page rendering, page loading blocking or crashing often occur. For this type of problem, there are currently two ways to obtain information. For the user feedback to business associates or customer service, the business associates or customer service then butt-joints the problems to products, and then the products are selectively butt-jointed to research and development associates for repairing in a scheduling manner at the emergency of the problems, and updated versions are online. Alternatively, the error report through the APP is logged to the error log to the background. The developer periodically checks the error log. And then periodically repairing.
The prior art has the defects that 1, the response and adjustment of the on-line problems are slow, and missing situations exist. 2. Some problem logs cannot be captured, so that the problems cannot be fed back.
Disclosure of Invention
The invention mainly aims to provide a webpage dynamic anomaly monitoring method and system, which are used for solving the problems that the current webpage loading problem is slow to respond and adjust and missing exists, and also solving the problem that the loading problem log cannot be captured and the feedback cannot be obtained.
In order to achieve the above object, the present invention provides the following techniques:
A web page dynamic anomaly monitoring method comprises the following steps:
s1, initiating a request to an APP front-end page, and returning data required by page rendering;
s2, checking returned data and local checking rules;
S3, constructing rendering for the page elements according to the returned data;
S4, page rendering inspection, if rendering errors occur, entering a step S5, and if rendering errors do not occur, ending the flow;
s5, triggering page fault alarm, and ending the whole flow.
Before the APP front-end page initiates the request data, a match check of data integrity and data type is added to the expected data model.
Further, after the page request response is completed, checking the data integrity and the data type of the response result, and when the response result shows that the data is not matched with the local configuration expected rule, judging that the data is abnormal in return, and triggering a first data abnormality alarm; when the response result shows that the data is matched with the local configuration expected rule, the data is judged to return to normal, and the step S3 is carried out.
Further, in the two false alarms, data anomalies and rendering anomalies are separated, wherein the rendering anomalies are due to data anomalies.
Further, the data exception triggering logic: data error and miss checking logic, page display driven by data; and S01, defining the data type and the data format of the page display in advance before rendering, S02, when the response data is requested to return, checking the data type and the format of the display data by the front end through a preset rule, S03, if the checking is not passed, sending checking information to the service end by the front end, triggering an alarm notification after receiving the checking information of the front end by the service end, and entering a rendering abnormality detection mechanism if the checking is passed.
Further, render exception trigger logic: s11, in the page rendering process, the displayed data and format are specified; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the process is ended; s13, monitoring error reporting caused by page rendering and synchronizing information to a server, wherein the server receives alarm information of the front end to trigger notification logic of data abnormality.
A web page dynamic anomaly monitoring system, comprising: a sending request module, a local configuration module, a data detection module, a rendering detection module and an alarm module,
The sending request module is used for initiating a request to an APP front-end page;
the local configuration module is used for configuring the data model and adding data integrity and data types;
The data detection module is used for comparing the request data sent by the page with the standard data in the local configuration module, and if the request data is not matched with the standard data, the data detection module sends error information to the alarm module;
The rendering detection module is used for comparing the displayed data and the data format with the preset content of the page in the page rendering process, and if the data and the data format are not matched, transmitting error information to the alarm module;
And the alarm module is used for receiving alarm information of the data detection module and the rendering detection module and sending the information to the server.
Further, the system also comprises an information sending module for sending page loading error alarm information to background research personnel.
Further, the system also comprises an updating module which is used for reloading correct contents after the background research personnel modify the front-end page data to the front-end page.
Compared with the prior art, the invention can bring the following technical effects:
The problems that the current webpage loading problem is slow in response and adjustment and missing exists are solved, and the problems that the loading problem log cannot be captured and the feedback of the problems cannot be obtained are solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention, are incorporated in and constitute a part of this specification. The drawings and their description are illustrative of the invention and are not to be construed as unduly limiting the invention. In the drawings:
FIG. 1 is a flow chart of a method for monitoring web page dynamic anomalies in accordance with the present invention;
FIG. 2 is a schematic overall flow chart of a method for monitoring web page dynamic anomalies;
FIG. 3 is a flow chart of a web page dynamic anomaly monitoring system of the present invention;
in the figure: the system comprises a sending request module 10, a local configuration module 20, a data detection module 30, a rendering detection module 40, an alarm module 50, an information sending module 60 and an updating module 70.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe the embodiments of the invention herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In the present invention, the terms "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal" and the like indicate an azimuth or a positional relationship based on that shown in the drawings. These terms are only used to better describe the present invention and its embodiments and are not intended to limit the scope of the indicated devices, elements or components to the particular orientations or to configure and operate in the particular orientations.
Also, some of the terms described above may be used to indicate other meanings in addition to orientation or positional relationships, for example, the term "upper" may also be used to indicate some sort of attachment or connection in some cases. The specific meaning of these terms in the present invention will be understood by those of ordinary skill in the art according to the specific circumstances.
In addition, the term "plurality" shall mean two as well as more than two.
It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be combined with each other. The invention will be described in detail below with reference to the drawings in connection with embodiments.
The error alarm information triggered twice can be automatically notified to research and development personnel at the first time through mails, enterprise WeChat and the like, the research and development personnel receive the alarm detailed information, the research and the development personnel begin to check and repair, and the online updating is timely carried out, and when the user accesses the same page after the updating is finished, the user can normally access the same page. In the two triggering alarms, a sequence exists, rendering abnormality is caused by data abnormality, so that the information appearing in the first alarm is the most important, the correctness and the integrity of the data are ensured as much as possible in the generating environment, and the occurrence of the error and the deletion of important data is avoided, so that the foreground display abnormality is caused.
Example 1
A web page dynamic anomaly monitoring method comprises the following steps:
S1, initiating a request to an APP front-end page, and returning data required by page rendering; before the APP front-end page initiates the request data, a match check of data integrity and data type is added to the expected data model.
S2, executing returned data and completing the check of local rules; after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data is abnormal in return when the data of the response result is not matched with the local configuration expected rule, and triggering a first data abnormality alarm; when the response result shows that the data is matched with the local configuration expected rule, the data is judged to return to normal, and the step S3 is carried out.
S3, constructing rendering for the page elements according to the returned data;
S4, page rendering inspection, if rendering errors occur, entering a step S5, and if rendering errors do not occur, ending the flow;
s5, triggering page fault alarm, and ending the whole flow.
For example, 1, return data detection rule instance, need to detect information such as user name and age filled in by page end:
2. Returning data display instances
If the first data check passes and the second data check fails, triggering data rendering exception notification.
Further, in the two false alarms, data anomalies and rendering anomalies are separated, wherein the rendering anomalies are due to data anomalies.
Further, the data exception triggering logic: data error and miss checking logic, page display driven by data; and S01, defining the data type and the data format of the page display in advance before rendering, S02, when the response data is requested to return, checking the data type and the format of the display data by the front end through a preset rule, S03, if the checking is not passed, sending checking information to the service end by the front end, triggering an alarm notification after receiving the checking information of the front end by the service end, and entering a rendering abnormality detection mechanism if the checking is passed. And synchronizing the checking information to the developer through tools such as mail, enterprise WeChat and the like.
Further, render exception trigger logic: s11, in the page rendering process, the displayed data and format are specified; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the process is ended; s13, monitoring error reporting caused by page rendering and synchronizing information to a server, wherein the server receives alarm information of the front end to trigger notification logic of data abnormality.
A web page dynamic anomaly monitoring system, comprising: a send request module 10, a local configuration module 20, a data detection module 30, a render detection module 40 and an alarm module 50,
A sending request module 10, configured to initiate a request to an APP front end page;
a local configuration module 20 for adding data integrity and data type to the configuration data model;
the data detection module 30 is configured to compare the request data sent by the page with the standard data in the local configuration module 20, and if the request data is not matched with the standard data, send an error message to the alarm module 50;
The rendering detection module 40 is configured to compare the displayed data and the data format with the preset content of the page in the page rendering process, and if the data and the data format are not matched, send an error message to the alarm module 50;
The alarm module 50 receives alarm information of the data detection module 30 and the rendering detection module 40 and transmits the information to the server.
And an information sending module 60 for sending page loading error alarm information to background research personnel.
An update module 70 is also included for the correct content of the front page data after modification by the background developer, reloading to the front page.
Example 2
A web page dynamic anomaly monitoring method comprises the following steps:
S1, initiating a request to an APP front-end page, and returning data required by page rendering; before the APP front-end page initiates the request data, a match check of data integrity and data type is added to the expected data model.
S2, executing returned data and completing the check of local rules; after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data is abnormal in return when the data of the response result is not matched with the local configuration expected rule, and triggering a first data abnormality alarm; when the response result shows that the data is matched with the local configuration expected rule, the data is judged to return to normal, and the step S3 is carried out.
S3, constructing rendering for the page elements according to the returned data;
S4, page rendering inspection, if rendering errors occur, entering a step S5, and if rendering errors do not occur, ending the flow;
s5, triggering page fault alarm, and ending the whole flow.
Further, in the two false alarms, data anomalies and rendering anomalies are separated, wherein the rendering anomalies are due to data anomalies.
For example, 1, returning to a data detection rule instance, and detecting information such as a user name and age filled in a page end, which is the same as that of embodiment 1; 2. the data display example was returned, as in example 1. If the rule above does not pass the first data check and the second pass, a data exception notification is triggered.
Further, the data exception triggering logic: data error and miss checking logic, page display driven by data; and S01, defining the data type and the data format of the page display in advance before rendering, S02, when the response data is requested to return, checking the data type and the format of the display data by the front end through a preset rule, S03, if the checking is not passed, sending checking information to the service end by the front end, triggering an alarm notification after receiving the checking information of the front end by the service end, and entering a rendering abnormality detection mechanism if the checking is passed.
Further, render exception trigger logic: s11, in the page rendering process, the displayed data and format are specified; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the process is ended; s13, monitoring error reporting caused by page rendering and synchronizing information to a server, wherein the server receives alarm information of the front end to trigger notification logic of data abnormality.
A web page dynamic anomaly monitoring system, comprising: a send request module 10, a local configuration module 20, a data detection module 30, a render detection module 40 and an alarm module 50,
A sending request module 10, configured to initiate a request to an APP front end page;
a local configuration module 20 for adding data integrity and data type to the configuration data model;
the data detection module 30 is configured to compare the request data sent by the page with the standard data in the local configuration module 20, and if the request data is not matched with the standard data, send an error message to the alarm module 50;
The rendering detection module 40 is configured to compare the displayed data and the data format with the preset content of the page in the page rendering process, and if the data and the data format are not matched, send an error message to the alarm module 50;
The alarm module 50 receives alarm information of the data detection module 30 and the rendering detection module 40 and transmits the information to the server.
And the information sending module 60 is used for sending the page loading error alarm information to background research personnel.
The updating module 70 is used for reloading the correct content modified by the background developer to the front-end page.
Example 3
A web page dynamic anomaly monitoring method comprises the following steps:
S1, initiating a request to an APP front-end page, and returning data required by page rendering; before the APP front-end page initiates the request data, a match check of data integrity and data type is added to the expected data model.
S2, executing returned data and completing the check of local rules; after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data is abnormal in return when the data of the response result is not matched with the local configuration expected rule, and triggering a first data abnormality alarm; when the response result shows that the data is matched with the local configuration expected rule, the data is judged to return to normal, and the step S3 is carried out.
S3, constructing rendering for the page elements according to the returned data;
S4, page rendering inspection, if rendering errors occur, entering a step S5, and if rendering errors do not occur, ending the flow;
s5, triggering page fault alarm, and ending the whole flow.
Further, in the two false alarms, data anomalies and rendering anomalies are separated, wherein the rendering anomalies are due to data anomalies.
For example, 1, returning to a data detection rule instance, and detecting information such as a user name and age filled in a page end, which is the same as that of embodiment 1; 2. the data display example was returned, as in example 1. If the rule above does not pass the first data check and the second does not pass, then both a data exception and notification of a render exception are triggered.
Further, the data exception triggering logic: data error and miss checking logic, page display driven by data; and S01, defining the data type and the data format of the page display in advance before rendering, S02, when the response data is requested to return, checking the data type and the format of the display data by the front end through a preset rule, S03, if the checking is not passed, sending checking information to the service end by the front end, triggering an alarm notification after receiving the checking information of the front end by the service end, and entering a rendering abnormality detection mechanism if the checking is passed.
Further, render exception trigger logic: s11, in the page rendering process, the displayed data and format are specified; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the process is ended; s13, monitoring error reporting of page rendering and synchronizing information to a server, wherein the server receives alarm information of the front end to trigger notification logic of data abnormality.
A web page dynamic anomaly monitoring system, comprising: a send request module 10, a local configuration module 20, a data detection module 30, a render detection module 40 and an alarm module 50,
A sending request module 10, configured to initiate a request to an APP front end page;
a local configuration module 20 for adding data integrity and data type to the configuration data model;
the data detection module 30 is configured to compare the request data sent by the page with the standard data in the local configuration module 20, and if the request data is not matched with the standard data, send an error message to the alarm module 50;
The rendering detection module 40 is configured to compare the displayed data and the data format with the preset content of the page in the page rendering process, and if the data and the data format are not matched, send an error message to the alarm module 50;
The alarm module 50 receives alarm information of the data detection module 30 and the rendering detection module 40 and transmits the information to the server.
And the information sending module 60 is used for sending the page loading error alarm information to background research personnel.
The updating module 70 is used for reloading the correct content modified by the background developer to the front-end page.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (7)
1. A web page dynamic anomaly monitoring method is characterized by comprising the following steps:
s1, initiating a request to an APP front-end page, returning data required by page rendering, and entering a step S2;
s2, executing returned data and completing the check of local rules; after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data is abnormal when the response result shows that the data is not matched with the local configuration expected rule, triggering a first data abnormal alarm, and synchronizing checking information to a developer through a mail and an enterprise WeChat tool; when the response result shows that the data is matched with the local configuration expected rule, judging that the data returns to normal, and entering step S3;
s3, constructing rendering for the page elements according to the returned data, and entering step S4;
S4, page rendering inspection, if rendering errors occur, entering a step S5, and if rendering errors do not occur, ending the flow;
s5, triggering page fault alarm, and sending page fault alarm information to background research personnel, wherein the whole process is finished;
before the APP front-end page initiates the request data, a match check of data integrity and data type is added to the expected data model.
2. The method for monitoring dynamic anomalies of web pages according to claim 1, wherein the two false alarms are divided into a data anomaly and a render anomaly.
3. The method for monitoring dynamic anomalies of web pages according to claim 1 or claim 2, wherein the data anomaly triggering logic: data error and miss checking logic, page display driven by data; and S01, defining the data type and the data format of the page display in advance before rendering, S02, when the response data is requested to return, checking the data type and the format of the display data by the front end through a preset rule, S03, if the checking is not passed, sending checking information to the service end by the front end, triggering an alarm notification after receiving the checking information of the front end by the service end, and entering a rendering abnormality detection mechanism if the checking is passed.
4. The method for monitoring web page dynamic anomalies as recited in claim 3, wherein the rendering anomaly triggering logic: s11, in the page rendering process, the displayed data and format are specified; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the process is ended; s13, monitoring error reporting caused by page rendering and synchronizing information to a server, wherein the server receives alarm information of the front end to trigger notification logic of data abnormality.
5. A web page dynamic anomaly monitoring system, comprising: a sending request module, a local configuration module, a data detection module, a rendering detection module and an alarm module,
The sending request module is used for initiating a request to an APP front-end page;
the local configuration module is used for configuring the data model and adding data integrity and data types;
The data detection module is used for comparing the request data sent by the page with the standard data in the local configuration module, and if the request data is not matched with the standard data, the data detection module sends error information to the alarm module;
The rendering detection module is used for comparing the displayed data and the data format with the preset content of the page in the page rendering process, and if the data and the data format are not matched, transmitting error information to the alarm module;
And the alarm module is used for receiving alarm information of the data detection module and the rendering detection module and sending the information to the server.
6. The web page dynamic anomaly monitoring system of claim 5, further comprising an information sending module for sending page load error alarm information to a background developer.
7. The system of claim 5 or 6, further comprising an update module for reloading the front page with correct contents of the front page data modified by the background developer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010576924.1A CN111782464B (en) | 2020-06-22 | 2020-06-22 | Webpage dynamic anomaly monitoring method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010576924.1A CN111782464B (en) | 2020-06-22 | 2020-06-22 | Webpage dynamic anomaly monitoring method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111782464A CN111782464A (en) | 2020-10-16 |
| CN111782464B true CN111782464B (en) | 2024-04-26 |
Family
ID=72757136
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010576924.1A Active CN111782464B (en) | 2020-06-22 | 2020-06-22 | Webpage dynamic anomaly monitoring method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111782464B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112835764A (en) * | 2021-02-01 | 2021-05-25 | 长沙市到家悠享网络科技有限公司 | Front-end monitoring method, device, equipment and medium |
| CN113645062A (en) * | 2021-07-13 | 2021-11-12 | 阿里巴巴新加坡控股有限公司 | Page data processing method and device and electronic equipment |
| CN114996103A (en) * | 2022-08-03 | 2022-09-02 | 平安银行股份有限公司 | Page abnormity detection method and device, electronic equipment and storage medium |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101788950A (en) * | 2010-01-27 | 2010-07-28 | 浪潮(山东)电子信息有限公司 | Data item calibration method based on JSP page |
| CN102799690A (en) * | 2012-08-13 | 2012-11-28 | 南京莱斯信息技术股份有限公司 | Method for verifying page input by using database technology |
| CN103729477A (en) * | 2014-01-26 | 2014-04-16 | 飞狐信息技术（天津）有限公司 | Webpage data format detection method and device |
| CN104978529A (en) * | 2015-03-10 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Exception handling method, exception handling system and exception handling server for webpage front end |
| CN107133240A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | Page monitoring method, apparatus and system |
| CN107609156A (en) * | 2017-09-26 | 2018-01-19 | 微梦创科网络科技（中国）有限公司 | The method and device that a kind of page is built |
| CN108153663A (en) * | 2016-12-02 | 2018-06-12 | 阿里巴巴集团控股有限公司 | Page data processing method and device |
| CN109271600A (en) * | 2018-08-16 | 2019-01-25 | 微梦创科网络科技（中国）有限公司 | A kind of monitoring method of performance data, system and device |
| WO2019037762A1 (en) * | 2017-08-23 | 2019-02-28 | 中兴通讯股份有限公司 | Information processing method, apparatus and virtual reality device |
| CN109408497A (en) * | 2018-09-20 | 2019-03-01 | 阿里巴巴集团控股有限公司 | A kind of rendering method of data, device and equipment |
| CN110109818A (en) * | 2019-03-15 | 2019-08-09 | 平安城市建设科技(深圳)有限公司 | Monitoring method, device, terminal and the readable storage medium storing program for executing of back end interface data |
| CN110198324A (en) * | 2018-02-26 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Data monitoring method, device, browser and terminal |
| CN110209978A (en) * | 2019-01-28 | 2019-09-06 | 腾讯科技（深圳）有限公司 | A kind of data processing method and relevant apparatus |
| CN110287056A (en) * | 2019-07-04 | 2019-09-27 | 郑州悉知信息科技股份有限公司 | Webpage error message acquisition methods and device |
| CN110572355A (en) * | 2019-07-23 | 2019-12-13 | 平安科技（深圳）有限公司 | Webpage data monitoring method and device, computer equipment and storage medium |
| CN110825479A (en) * | 2019-11-05 | 2020-02-21 | 江苏满运软件科技有限公司 | Page processing method and device, terminal equipment, server and storage medium |
-
2020
- 2020-06-22 CN CN202010576924.1A patent/CN111782464B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101788950A (en) * | 2010-01-27 | 2010-07-28 | 浪潮(山东)电子信息有限公司 | Data item calibration method based on JSP page |
| CN102799690A (en) * | 2012-08-13 | 2012-11-28 | 南京莱斯信息技术股份有限公司 | Method for verifying page input by using database technology |
| CN103729477A (en) * | 2014-01-26 | 2014-04-16 | 飞狐信息技术（天津）有限公司 | Webpage data format detection method and device |
| CN104978529A (en) * | 2015-03-10 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Exception handling method, exception handling system and exception handling server for webpage front end |
| CN107133240A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | Page monitoring method, apparatus and system |
| CN108153663A (en) * | 2016-12-02 | 2018-06-12 | 阿里巴巴集团控股有限公司 | Page data processing method and device |
| WO2019037762A1 (en) * | 2017-08-23 | 2019-02-28 | 中兴通讯股份有限公司 | Information processing method, apparatus and virtual reality device |
| CN107609156A (en) * | 2017-09-26 | 2018-01-19 | 微梦创科网络科技（中国）有限公司 | The method and device that a kind of page is built |
| CN110198324A (en) * | 2018-02-26 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Data monitoring method, device, browser and terminal |
| CN109271600A (en) * | 2018-08-16 | 2019-01-25 | 微梦创科网络科技（中国）有限公司 | A kind of monitoring method of performance data, system and device |
| CN109408497A (en) * | 2018-09-20 | 2019-03-01 | 阿里巴巴集团控股有限公司 | A kind of rendering method of data, device and equipment |
| CN110209978A (en) * | 2019-01-28 | 2019-09-06 | 腾讯科技（深圳）有限公司 | A kind of data processing method and relevant apparatus |
| CN110109818A (en) * | 2019-03-15 | 2019-08-09 | 平安城市建设科技(深圳)有限公司 | Monitoring method, device, terminal and the readable storage medium storing program for executing of back end interface data |
| CN110287056A (en) * | 2019-07-04 | 2019-09-27 | 郑州悉知信息科技股份有限公司 | Webpage error message acquisition methods and device |
| CN110572355A (en) * | 2019-07-23 | 2019-12-13 | 平安科技（深圳）有限公司 | Webpage data monitoring method and device, computer equipment and storage medium |
| CN110825479A (en) * | 2019-11-05 | 2020-02-21 | 江苏满运软件科技有限公司 | Page processing method and device, terminal equipment, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111782464A (en) | 2020-10-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111782464B (en) | Webpage dynamic anomaly monitoring method and system | |
| AU2017203498B2 (en) | Software testing integration | |
| CN103246574B (en) | The method of calibration of data accuracy and device | |
| US20130311977A1 (en) | Arrangement and method for model-based testing | |
| EP3376389B1 (en) | Data processing method and device | |
| US7734774B2 (en) | In-operation system check processing device, method, and program thereof | |
| US20030093516A1 (en) | Enterprise management event message format | |
| CN107707415B (en) | SaltStack-based automatic monitoring and warning method for server configuration | |
| US11281522B2 (en) | Automated detection and classification of dynamic service outages | |
| CN108847998B (en) | Report monitoring method and device, computer equipment and storage medium | |
| CN109783356A (en) | A kind of automated testing method and terminal | |
| CN110851471A (en) | Distributed log data processing method, device and system | |
| CN110119325A (en) | Server failure processing method, device, equipment and computer readable storage medium | |
| CN107153595A (en) | The fault detection method and its system of distributed data base system | |
| CN111367934B (en) | Data consistency checking method, device, server and medium | |
| CN112463883A (en) | Reliability monitoring method, device and equipment based on big data synchronization platform | |
| CN110069382B (en) | Software monitoring method, server, terminal device, computer device and medium | |
| Becker et al. | A practical approach to failure mode, effects and criticality analysis (FMECA) for computing systems | |
| EP3895015B1 (en) | Collecting repeated diagnostics data from across users participating in a document collaboration session | |
| CN113656003A (en) | Software package management method and related equipment | |
| CN110825635B (en) | Test method, test device and computer-readable storage medium | |
| CN111026619A (en) | Page monitoring method and device and storage medium | |
| CN111444032A (en) | Computer system fault repairing method, system and equipment | |
| US20150154498A1 (en) | Methods for identifying silent failures in an application and devices thereof | |
| CN116719660A (en) | Page content detection method and device, electronic equipment and 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 |