CN111782464A - Webpage dynamic abnormity monitoring method and system - Google Patents
Webpage dynamic abnormity monitoring method and system Download PDFInfo
- Publication number
- CN111782464A CN111782464A CN202010576924.1A CN202010576924A CN111782464A CN 111782464 A CN111782464 A CN 111782464A CN 202010576924 A CN202010576924 A CN 202010576924A CN 111782464 A CN111782464 A CN 111782464A
- Authority
- CN
- China
- Prior art keywords
- data
- page
- rendering
- module
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000012544 monitoring process Methods 0.000 title claims abstract description 31
- 238000009877 rendering Methods 0.000 claims abstract description 90
- 230000004044 response Effects 0.000 claims abstract description 29
- 230000008569 process Effects 0.000 claims abstract description 24
- 230000000977 initiatory effect Effects 0.000 claims abstract description 8
- 238000001514 detection method Methods 0.000 claims description 40
- 238000012827 research and development Methods 0.000 claims description 11
- 230000002159 abnormal effect Effects 0.000 claims description 10
- 238000013499 data model Methods 0.000 claims description 10
- 230000007246 mechanism Effects 0.000 claims description 5
- 230000001960 triggered effect Effects 0.000 claims description 4
- 230000004048 modification Effects 0.000 claims description 3
- 238000012986 modification Methods 0.000 claims description 3
- 230000000903 blocking effect Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Databases & Information Systems (AREA)
- Mathematical Physics (AREA)
- Data Mining & Analysis (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the technical field of webpage monitoring, and discloses a method and a system for monitoring dynamic abnormity of a webpage, 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 the return data and finishing the check of the local rule; s3, according to the returned data, rendering is built on the page elements; s4, page rendering check, if rendering error occurs, the step S5 is entered, if no rendering error occurs, the flow is ended; and S5, triggering page fault alarm, and ending the whole process. The problems that the response and the adjustment of the current webpage loading problem are slow, the omission exists and the problem that the log of the loading problem cannot be captured and the problem that the existing problem cannot be fed back are solved.
Description
Technical Field
The invention relates to the technical field of webpage monitoring, in particular to a method and a system for monitoring dynamic abnormity of a webpage.
Background
In the development or loading process of an APP front-end page, the problems of page rendering, page loading blocking or breakdown often occur. For such problems, there are currently two ways to obtain information. One is that the user feeds back to the business colleagues or customer service, the business colleagues or customer service then butt-joint the problems to the products, then the products are selectively butt-jointed to the research and development colleagues in terms of scheduling the emergency degree of the problems, the repairing is carried out, and the version is updated to be on-line. And the other is to report and record an error log to a background through the error of the APP. Developers regularly check the error log. And then periodically repaired.
The prior art has the defects that 1, the response and the adjustment to the problems on the line are slow, and the missing situation exists. 2. Some problems are caused that the log cannot be captured, and the problems cannot be fed back.
Disclosure of Invention
The invention mainly aims to provide a method and a system for monitoring dynamic abnormity of a webpage, which are used for solving the problems that the response and adjustment of the current webpage loading problem are slow, the webpage loading problem is missed, and the problem that the log cannot be captured in the loading problem, so that the problems cannot be fed back is solved.
In order to achieve the above object, the present invention provides the following techniques:
a webpage dynamic abnormity 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 the return data and the local checking rule;
s3, according to the returned data, rendering is built on the page elements;
s4, page rendering check, if rendering error occurs, the step S5 is entered, if no rendering error occurs, the flow is ended;
and S5, triggering page fault alarm, and ending the whole process.
Before the APP front-end page initiates the request data, data integrity and data type matching check is added in the expected data model.
Further, after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data return is abnormal when the data is not matched with the expected rule of local configuration in the response result, and triggering a first data abnormity alarm; when the response result shows that the data matches the local configuration expectation rule, it is determined that the data returns to normal, and the process proceeds to step S3.
Further, in the two error alarms, the data exception and the rendering exception are divided, wherein the rendering exception is caused by the data exception.
Further, the data exception triggers logic to: data error and miss checking logic, page display driven by data; s01, defining the data type and data format of the page display in advance before rendering, S02, when the request response data is returned, the front end checks the data type and format of the display data by using a preset rule, S03, if the check is not passed, the front end sends check information to the server, the server receives the check information of the front end, triggers an alarm notification, and if the check is passed, enters a rendering abnormity detection mechanism.
Further, rendering exception triggering logic: s11, specifying the display data and format in the page rendering process; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the flow is ended; s13, by monitoring the error report of page rendering and synchronizing the information to the server, the server side receives the alarm information of the front end to trigger the notification logic of data abnormity.
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 request sending module is used for initiating a request to an APP front-end page;
the local configuration module is used for adding data integrity and data types in the configuration data model;
the data detection module is used for comparing request data sent by the page with standard data in the local configuration module, and if the request data are not matched with the standard data, sending 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, sending error information to the alarm module;
and the alarm module receives the alarm information of the data detection module and the rendering detection module and sends the information to the server.
Further, the system also comprises an information sending module used for sending the page loading error alarm information to background research and development personnel.
Furthermore, the system also comprises an updating module, which is used for reloading the correct content of the modified front-end page data to the front-end page by background research personnel.
Compared with the prior art, the invention can bring the following technical effects:
the problems that the response and the adjustment of the current webpage loading problem are slow, the omission exists and the problem that the log of the loading problem cannot be captured and the problem that the existing problem cannot be fed back are solved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, are included to provide a further understanding of the invention and to enable other features, objects and advantages of the invention to be more fully apparent. The drawings and their description illustrate the invention by way of example and are not intended to limit the invention. In the drawings:
FIG. 1 is a flow chart of a method for monitoring dynamic web page anomalies according to the present invention;
FIG. 2 is a schematic overall flow chart of a method for monitoring dynamic web page anomalies according to the present invention;
FIG. 3 is a flow chart of a web page dynamic anomaly monitoring system according to 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 to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged under appropriate circumstances in order to facilitate the description of 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", "center", "vertical", "horizontal", "lateral", "longitudinal", and the like indicate an orientation or positional relationship based on the orientation or positional relationship shown in the drawings. These terms are used primarily to better describe the invention and its embodiments and are not intended to limit the indicated devices, elements or components to a particular orientation or to be constructed and operated in a particular orientation.
Moreover, some of the above terms may be used to indicate other meanings besides the orientation or positional relationship, for example, the term "on" may also be used to indicate some kind of attachment or connection relationship in some cases. The specific meanings of these terms in the present invention can be understood by those skilled in the art as appropriate.
In addition, the term "plurality" shall mean two as well as more than two.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
The two times of triggering of the false alarm information can automatically notify research and development personnel through mails, enterprise WeChat and the like at the first time, the research and development personnel receive the alarm detailed information, start to check and repair, and timely update online, and after the update is finished, the user can normally access the same page. In the two times of triggering alarm, the two times of triggering alarm have a sequence, rendering abnormity is caused by data abnormity, 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 under the generation environment, and the foreground display abnormity caused by the error and the loss of important data is avoided.
Example 1
A webpage dynamic abnormity 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, data integrity and data type matching check is added in the expected data model.
S2, executing the return data and finishing the check of the local rule; after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data return is abnormal when the data of the response result is not matched with the expected rule of local configuration, and triggering a first data abnormity alarm; when the response result shows that the data matches the local configuration expectation rule, it is determined that the data returns to normal, and the process proceeds to step S3.
S3, according to the returned data, rendering is built on the page elements;
s4, page rendering check, if rendering error occurs, the step S5 is entered, if no rendering error occurs, the flow is ended;
and S5, triggering page fault alarm, and ending the whole process.
For example, 1, returning a data detection rule example, information such as name and age of a user filled in a page end needs to be detected:
2. return data display example
If the first data check passes and the second does not pass, then a data rendering exception notification is triggered.
Further, in the two error alarms, the data exception and the rendering exception are divided, wherein the rendering exception is caused by the data exception.
Further, the data exception triggers logic to: data error and miss checking logic, page display driven by data; s01, defining the data type and data format of the page display in advance before rendering, S02, when the request response data is returned, the front end checks the data type and format of the display data by using a preset rule, S03, if the check is not passed, the front end sends check information to the server, the server receives the check information of the front end, triggers an alarm notification, and if the check is passed, enters a rendering abnormity detection mechanism. And synchronizing the inspection information to developers through tools such as mails, enterprise WeChats and the like.
Further, rendering exception triggering logic: s11, specifying the display data and format in the page rendering process; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the flow is ended; s13, by monitoring the error report of page rendering and synchronizing the information to the server, the server side receives the alarm information of the front end to trigger the notification logic of data abnormity.
A web page dynamic anomaly monitoring system, comprising: a request to send module 10, a local configuration module 20, a data detection module 30, a render detection module 40 and an alert module 50,
a request sending module 10, configured to initiate a request to an APP front-end page;
a local configuration module 20, configured to add data integrity and data type to the data model;
the data detection module 30 is used for comparing 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 in the local configuration module 20, sending error information 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;
and the alarm module 50 receives the alarm information of the data detection module 30 and the rendering detection module 40 and sends the information to the server.
The system further comprises an information sending module 60, which is used for sending the page loading error alarm information to the background research and development personnel.
The system further comprises an updating module 70, which is used for the background research and development personnel to reload the front-end page with the correct content after the front-end page data is modified.
Example 2
A webpage dynamic abnormity 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, data integrity and data type matching check is added in the expected data model.
S2, executing the return data and finishing the check of the local rule; after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data return is abnormal when the data of the response result is not matched with the expected rule of local configuration, and triggering a first data abnormity alarm; when the response result shows that the data matches the local configuration expectation rule, it is determined that the data returns to normal, and the process proceeds to step S3.
S3, according to the returned data, rendering is built on the page elements;
s4, page rendering check, if rendering error occurs, the step S5 is entered, if no rendering error occurs, the flow is ended;
and S5, triggering page fault alarm, and ending the whole process.
Further, in the two error alarms, the data exception and the rendering exception are divided, wherein the rendering exception is caused by the data exception.
For example, 1, returning a data detection rule instance, which needs to detect the user name, age and other information filled in the page end, is the same as that in embodiment 1; 2. returning to the data display example, the same as in embodiment 1. If the first data check fails and the second passes, then a data exception notification is triggered.
Further, the data exception triggers logic to: data error and miss checking logic, page display driven by data; s01, defining the data type and data format of the page display in advance before rendering, S02, when the request response data is returned, the front end checks the data type and format of the display data by using a preset rule, S03, if the check is not passed, the front end sends check information to the server, the server receives the check information of the front end, triggers an alarm notification, and if the check is passed, enters a rendering abnormity detection mechanism.
Further, rendering exception triggering logic: s11, specifying the display data and format in the page rendering process; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the flow is ended; s13, by monitoring the error report of page rendering and synchronizing the information to the server, the server side receives the alarm information of the front end to trigger the notification logic of data abnormity.
A web page dynamic anomaly monitoring system, comprising: a request to send module 10, a local configuration module 20, a data detection module 30, a render detection module 40 and an alert module 50,
a request sending module 10, configured to initiate a request to an APP front-end page;
a local configuration module 20, configured to add data integrity and data type to the data model;
the data detection module 30 is used for comparing 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 in the local configuration module 20, sending error information 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;
and the alarm module 50 receives the alarm information of the data detection module 30 and the rendering detection module 40 and sends the information to the server.
And the information sending module 60 is used for sending the page loading error alarm information to the background research and development personnel.
And the updating module 70 is used for reloading the correct content of the modified front-end page data to the front-end page by the background research and development personnel.
Example 3
A webpage dynamic abnormity 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, data integrity and data type matching check is added in the expected data model.
S2, executing the return data and finishing the check of the local rule; after the page request response is completed, checking the data integrity and the data type of the response result, judging that the data return is abnormal when the data of the response result is not matched with the expected rule of local configuration, and triggering a first data abnormity alarm; when the response result shows that the data matches the local configuration expectation rule, it is determined that the data returns to normal, and the process proceeds to step S3.
S3, according to the returned data, rendering is built on the page elements;
s4, page rendering check, if rendering error occurs, the step S5 is entered, if no rendering error occurs, the flow is ended;
and S5, triggering page fault alarm, and ending the whole process.
Further, in the two error alarms, the data exception and the rendering exception are divided, wherein the rendering exception is caused by the data exception.
For example, 1, returning a data detection rule instance, which needs to detect the user name, age and other information filled in the page end, is the same as that in embodiment 1; 2. returning to the data display example, the same as in embodiment 1. If the first data check fails and the second fails, then notification of both a data exception and a render exception is triggered.
Further, the data exception triggers logic to: data error and miss checking logic, page display driven by data; s01, defining the data type and data format of the page display in advance before rendering, S02, when the request response data is returned, the front end checks the data type and format of the display data by using a preset rule, S03, if the check is not passed, the front end sends check information to the server, the server receives the check information of the front end, triggers an alarm notification, and if the check is passed, enters a rendering abnormity detection mechanism.
Further, rendering exception triggering logic: s11, specifying the display data and format in the page rendering process; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the flow is ended; s13, by monitoring the error report of page rendering and synchronizing the information to the server, the server side receives the alarm information of the front end to trigger the notification logic of data abnormity.
A web page dynamic anomaly monitoring system, comprising: a request to send module 10, a local configuration module 20, a data detection module 30, a render detection module 40 and an alert module 50,
a request sending module 10, configured to initiate a request to an APP front-end page;
a local configuration module 20, configured to add data integrity and data type to the data model;
the data detection module 30 is used for comparing 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 in the local configuration module 20, sending error information 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;
and the alarm module 50 receives the alarm information of the data detection module 30 and the rendering detection module 40 and sends the information to the server.
And the information sending module 60 is used for sending the page loading error alarm information to the background research and development personnel.
And the updating module 70 is used for reloading the correct content of the modified front-end page data to the front-end page by the background research and development personnel.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A webpage dynamic abnormity 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 step S2;
s2, executing the return data and finishing the check of the local rule, and entering the step S3;
s3, according to the returned data, rendering is built on the page elements, and the step S4 is carried out;
s4, page rendering check, if rendering error occurs, the step S5 is entered, if no rendering error occurs, the flow is ended;
and S5, triggering page fault alarm, and ending the whole process.
2. The method for monitoring dynamic anomaly of web pages as claimed in claim 1, wherein before the APP front end page initiates the request for data, a matching check of data integrity and data type is added to the expected data model.
3. The method for monitoring the dynamic abnormity of the webpage according to claim 1 or 2, characterized in that after the response of the webpage request is completed, the data integrity and the data type of the response result are checked, when the data of the response result is not matched with the expected rule of local configuration, the data return is judged to be abnormal, and meanwhile, the first data abnormity alarm is triggered; when the response result shows that the data matches the local configuration expectation rule, it is determined that the data returns to normal, and the process proceeds to step S3.
4. The method for monitoring dynamic web page anomalies according to claim 3, characterized in that in two false alarms, there are data anomalies and rendering anomalies.
5. The method for monitoring dynamic web page exceptions of claim 1 or 4, wherein the data exception trigger logic: data error and miss checking logic, page display driven by data; s01, defining the data type and data format of the page display in advance before rendering, S02, when the request response data is returned, the front end checks the data type and format of the display data by using a preset rule, S03, if the check is not passed, the front end sends check information to the server, the server receives the check information of the front end, triggers an alarm notification, and if the check is passed, enters a rendering abnormity detection mechanism.
6. The method of claim 5, wherein the rendering exception triggering logic: s11, specifying the display data and format in the page rendering process; s12, if the data return is abnormal, the page rendering is wrong, and if the data return is normal, the flow is ended; s13, by monitoring the error report of page rendering and synchronizing the information to the server, the server side receives the alarm information of the front end to trigger the notification logic of data abnormity.
7. 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 request sending module is used for initiating a request to an APP front-end page;
the local configuration module is used for adding data integrity and data types in the configuration data model;
the data detection module is used for comparing request data sent by the page with standard data in the local configuration module, and if the request data are not matched with the standard data, sending 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, sending error information to the alarm module;
and the alarm module receives the alarm information of the data detection module and the rendering detection module and sends the information to the server.
8. The system for monitoring dynamic web page anomalies as claimed in claim 7, further comprising an information sending module for sending a page loading error alarm message to background research and development personnel.
9. The method for monitoring dynamic web page anomalies as claimed in claim 7 or 8, further comprising an update module for a background developer to reload to the front-end page the correct content after modification of the front-end page data.
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 true CN111782464A (en) | 2020-10-16 |
| CN111782464B 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) |
Cited By (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 |
Cited By (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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111782464B (en) | 2024-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111782464A (en) | Webpage dynamic abnormity monitoring method and system | |
| EP3376389B1 (en) | Data processing method and device | |
| CN107678936B (en) | Business system pre-inspection method, server and computer readable storage medium | |
| CN106844730B (en) | Method and device for displaying file content | |
| CN109783356A (en) | A kind of automated testing method and terminal | |
| CN109088773B (en) | Fault self-healing method and device, server and storage medium | |
| WO2021097824A1 (en) | Code quality and defect analysis method, server and storage medium | |
| CN111309505B (en) | Page exception handling method and device and electronic equipment | |
| CN113448862B (en) | Software version testing method and device and computer equipment | |
| CN112256593B (en) | Program processing method and device, computer equipment and readable storage medium | |
| CN110362416B (en) | Page component loading method and device, electronic equipment and storage medium | |
| CN110704462A (en) | Data change notification method, electronic device, computer device, and storage medium | |
| CN110968779A (en) | Processing method and device for crawling webpage information | |
| CN115269424A (en) | Automatic regression testing method, device, equipment and storage medium for production flow | |
| CN113656003A (en) | Software package management method and related equipment | |
| CN112765188A (en) | Configuration information processing method, configuration management system, electronic device, and storage medium | |
| CN112269594A (en) | Project code quality evaluation method, device, equipment and storage medium | |
| CN116719660A (en) | Page content detection method and device, electronic equipment and storage medium | |
| US20220138386A1 (en) | Method and apparatus for setting wafer script, device and storage medium | |
| CN113037570B (en) | Alarm processing method and equipment | |
| CN112631845A (en) | Server order checking method, system, equipment and medium | |
| CN113722221A (en) | Method and device for automatically detecting source codes and putting source codes into storage | |
| CN117640357A (en) | Processing method and device for network element data acquisition abnormality and related equipment | |
| CN114035835A (en) | System backspacing risk assessment method | |
| CN115185802A (en) | Linkage evaluation method, linkage evaluation device, electronic device, 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 |