CN112783734A - System suitable for front-end page performance and error index acquisition - Google Patents

System suitable for front-end page performance and error index acquisition Download PDF

Info

Publication number
CN112783734A
CN112783734A CN202110143242.6A CN202110143242A CN112783734A CN 112783734 A CN112783734 A CN 112783734A CN 202110143242 A CN202110143242 A CN 202110143242A CN 112783734 A CN112783734 A CN 112783734A
Authority
CN
China
Prior art keywords
module
probe
probe unit
page
performance
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.)
Pending
Application number
CN202110143242.6A
Other languages
Chinese (zh)
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.)
Beijing Bite Yipai Information Technology Co ltd
Original Assignee
Beijing Bite Yipai Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Bite Yipai Information Technology Co ltd filed Critical Beijing Bite Yipai Information Technology Co ltd
Priority to CN202110143242.6A priority Critical patent/CN112783734A/en
Publication of CN112783734A publication Critical patent/CN112783734A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0775—Content or structure details of the error report, e.g. specific table structure, specific error fields
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data

Abstract

The application discloses a system suitable for front-end page performance and error index acquisition, which comprises a probe unit, a collected data summarizing module, a rear-end interface and a remote server, wherein one end of the probe unit is connected with a browser, the other end of the probe unit is connected with the collected data summarizing module, the collected data summarizing module is connected with a plurality of rear-end interfaces, and the plurality of rear-end interfaces are connected to the remote server; the probe unit is connected with one end of a probe configuration control module, and the other end of the probe configuration control module is connected with a probe initialization configuration module and a default configuration module; the probe unit is also connected with one end of the SDK tool module. The method has the advantages that when a white screen or JS file error occurs, the information to be acquired is reported to a remote server through the acquisition formula, so that the problem of passively perceiving the occurrence of the client browser is solved. It is not intrusive to the business system, just as introducing a JS file.

Description

System suitable for front-end page performance and error index acquisition
Technical Field
The application relates to a system for error collection, in particular to a system suitable for collecting front-end page performance and error indexes.
Background
The browser is an application program used for retrieving, displaying and transmitting Web information resources; the Web information resource is marked by a uniform resource identifier, and is a webpage, a picture, a video or any content presented on the Web; the user can browse the information associated with each other through a browser by means of Hyperlinks (Hyperlinks).
When the existing browser is used, errors are easy to occur; a user can use a browser to access a front page of a website; when a front-end page is in a white screen or has errors, the front-end page cannot usually sense the problems, so that the requirement on front-end monitoring is very strong; the basic schemes in the industry are as follows:
according to the first scheme, analysis and investigation are carried out on local page performance and error logs of a user by using a Perform and a Console tab of a GoogleChrome browser;
performing performance calculation on the page by using data provided by a native API of a window.
The third scheme is as follows: performing local error information monitoring by using methods provided by native APIs of a window.
The defects and shortcomings of the scheme are that the scheme is limited when being used for analyzing problems, and the problems can be found only by checking various performance indexes by relying on a computer of a user; the second problem is that when the API, window, performance, of the second scheme is used for analyzing the problem, only one set of data is provided, if one index result is required to be obtained, the result can be calculated by subtracting a plurality of indexes, and the use is not facilitated; the native APIs of the two browsers of the third problem and the third usage scenario are capable of acquiring error information, but the error result is obviously different according to the different browsers used by users. Therefore, a system suitable for front-end page performance and error index acquisition is proposed to solve the above problems.
Disclosure of Invention
A system suitable for front-end page performance and error index acquisition comprises a probe unit, an acquired data summarizing module, a rear-end interface and a remote server, wherein one end of the probe unit is connected with a browser, the other end of the probe unit is connected with the acquired data summarizing module, the acquired data summarizing module is connected with a plurality of rear-end interfaces, and the rear-end interfaces are all connected to the remote server; the probe unit is connected with one end of a probe configuration control module, and the other end of the probe configuration control module is connected with a probe initialization configuration module and a default configuration module; the probe unit is also connected with one end of the SDK tool module.
Furthermore, a script abnormity acquisition module, a resource loading abnormity acquisition module and a page performance acquisition module are arranged in the probe unit.
Furthermore, the browser is connected with a website access module.
Furthermore, one end of the SDK tool module is connected with a browser.
Further, the remote server is connected with a database.
Further, the probe unit is a < script > tag, and the probe unit is connected with a probe producer, which is arranged inside the probe configuration control module.
Furthermore, the script exception acquisition module and the resource loading exception acquisition module are internally provided with an event monitor of < error, unhandedreject >.
Further, a tool operation module is connected to the probe unit.
Furthermore, the script exception acquisition module, the resource loading exception acquisition module and the page performance acquisition module are all connected to the acquired data summarizing module.
Further, the probe initialization configuration module is connected with the default configuration module.
The beneficial effect of this application is:
firstly, collecting the performance and abnormal data of the browser and the H5 page, classifying the data and reporting the classified data to a server side to provide data analysis.
Secondly, the service system is hardly required to be modified, the access mode is the same as that of introducing one JS file, and the access cost of the service system is greatly reduced.
And thirdly, the stability of the service system is guaranteed, and the normal use of the page cannot be influenced when the acquisition end has errors.
In summary, the invention of the patent is to solve the problem that when a user has a white screen or JS file error when accessing a front-end page, the information to be acquired is reported to a remote server through an acquisition formula, so that the user can passively sense the occurrence of a client browser. It is not intrusive to the business system, just as introducing a JS file.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
FIG. 1 is a schematic overall structure diagram of an embodiment of the present application;
FIG. 2 is a flow chart of exception acquisition according to an embodiment of the present application;
fig. 3 is a flow chart of performance collection according to an embodiment of the present application.
In the figure: 1. the system comprises a probe unit, 101, a script exception acquisition module, 102, a resource loading exception acquisition module, 103, a page performance acquisition module, 2, an acquired data summarization module, 3, a rear-end interface, 4, a remote server, 5, a database, 6, a probe configuration control module, 7, a probe initialization configuration module, 8, a default configuration module, 9, a website access module, 10, a browser, 11, a tool operation module, 12 and an SDK tool module.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all 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 application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application 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 should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be used. 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 this application, the terms "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal", and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings. These terms are used primarily to better describe the present application and its embodiments, and are not used 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 meaning of these terms in this application will be understood by those of ordinary skill in the art as appropriate.
Furthermore, the terms "mounted," "disposed," "provided," "connected," and "sleeved" are to be construed broadly. For example, it may be a fixed connection, a removable connection, or a unitary construction; can be a mechanical connection, or an electrical connection; may be directly connected, or indirectly connected through intervening media, or may be in internal communication between two devices, elements or components. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Referring to fig. 1-3, a system suitable for front-end page performance and error index acquisition includes a probe unit 1, an acquired data summarization module 2, a backend interface 3, and a remote server 4, where one end of the probe unit 1 is connected to a browser 10, the other end of the probe unit 1 is connected to the acquired data summarization module 2, the acquired data summarization module 2 is connected to a plurality of backend interfaces 3, and the plurality of backend interfaces 3 are all connected to the remote server 4;
the probe unit 1 is connected with one end of a probe configuration control module 6, and the other end of the probe configuration control module 6 is connected with a probe initialization configuration module 7 and a default configuration module 8;
the probe unit 1 is also connected to one end of the SDK tool module 12.
A script abnormity acquisition module 101, a resource loading abnormity acquisition module 102 and a page performance acquisition module 103 are arranged in the probe unit 1, and the script abnormity acquisition module 101 and the resource loading abnormity acquisition module 102 are functional modules for monitoring errors of the browser 10 and resource abnormity; the page performance acquisition module 103 is configured to acquire performance information acquired when a user accesses a page.
The browser 10 is connected with a website access module 9.
One end of the SDK tool module 12 is connected to the browser 10, and the SDK tool module 12 is an entry file of the acquisition end.
The remote server 4 is connected with a database 5.
The probe unit 1 is a < script > tag, and the probe unit 1 is connected with a probe producer, which is disposed inside the probe configuration control module 6.
The script exception collecting module 101 and the resource loading exception collecting module 102 are internally provided with an event listener of < error, unhandredreject >.
The probe unit 1 is connected to a tool operation module 11, and is configured to provide core tools, such as configuration, data processing tool, and data reporting, and is configured to control operations to change.
The script exception acquisition module 101, the resource loading exception acquisition module 102 and the page performance acquisition module 103 are all connected to the acquired data summarization module 2.
The probe initialization configuration module 7 is connected with a default configuration module 8.
The process of introducing the probe and collecting and reporting is as follows:
(1) configuration of the probe unit 1: the probe unit 1 provides a plurality of acquisition functions, including a script exception acquisition module 101, a resource loading exception acquisition module 102 and a page performance acquisition module 103; these acquisition categories may be enabled and disabled by the probe configuration control module 6.
(2) Introducing a probe: this stage serves to introduce the acquisition probe unit 1 to the page.
(3) Index collection: when the user accesses the target page, the probe unit 1 is executed, and the probe monitors corresponding information according to the configuration items.
(4) And (3) reporting indexes: the classification according to the collected indexes (according to the collection and collection module, by classifying, collecting and sorting the collected indexes) will report the content to the corresponding back-end interface 3.
For the above stage, the system proposes the following detailed design scheme:
(1) in order to reduce the business system transformation caused by introducing the probe unit 1, the system introduces the probe unit 1 into a target page as a < script > tag.
(2) Initializing the probe, wherein the probe judges whether the configuration is transmitted or not during initialization; if the probe is not configured, the probe default built-in configuration (i.e. default configuration module 8) is used. If a configuration is entered when the probe unit 1 is initialized (probe initialization configuration module 7), the entered configuration overrides the default configuration. The final initialisation configuration and the default configuration are merged into a final configuration, wherein the configuration is controlled by the probe configuration control module 6.
(3) The probe unit 1 starts or closes the corresponding acquisition function (the script exception acquisition module 101, the resource loading exception acquisition module 102, and the page performance acquisition module 103) according to the final configuration.
If exception collection (i.e., script exception collection module 101, resource load exception collection module 102) is enabled, then data collection for resource exceptions and error exceptions is turned on, and then its execution steps are as shown in FIG. 2.
The steps of anomaly collection are as follows:
(1) registers the listener of the < error, unhanddrejection > event for the browser 10.
(2) Preparing a data structure to be reported and setting a corresponding exception type.
(3) The browser 10 used for accessing the target page is detected, and different processes are performed according to the browser 10 differences.
(4) If the browser 10 is the browser 10 of the IE kernel, or the browser 10 accesses the page in the IE mode, the data is collected by using the API supported by the IE, and the collected data is the IE data.
(5) If the browser 10 is a Webkit kernel, or the browser 10 supports the W3C standard, the probe will collect data with the standard API of W3C, and the collected data is W3C data.
(6) The IE data and the W3C data are merged and gathered into the same data structure.
(7) And reporting the summarized abnormal information data.
As can be seen from the above, the system detects whether the browser 10 is abnormal according to the < error, unhandedreject > event of the browser 10, and is compatible with the old versions of browsers 10 such as IE, so that the data structures of abnormal data in different browsers 10 are unified, and the pressure on data processing in the later period is reduced.
If page performance collection (page performance collection module 103) is enabled, then it performs the steps as shown in FIG. 3.
(1) And detecting whether the browser 10 contains a performanceAPI, and if not, determining that the browser 10 is a legacy browser and not collecting performance data.
(2) A data structure is prepared for the performance data.
(3) And judging whether the browser is the Chrome browser 10, and if so, additionally acquiring a white screen index, a first screen index and a maximum content rendering index besides the general performance index. If not, only the general performance index is collected. The collection logic of the general performance index is as follows:
(3.1) the first byte time, which is calculated by the formula:
timing.responseStart-timing.requestStart。
(3.2) the Dom Ready time, which is calculated by the formula:
timing.domContentLoadedEventEnd-timing.fetchStart。
(3.3) the page full load time, which is calculated by the formula:
timing.loadEventStart-timing.fetchStart。
(3.4) DNS query time, which is calculated by the formula:
timing.domainLookupEnd-timing.domainLookupStart。
(3.5) the TCP connection time is calculated according to the formula:
timing.connectEnd-timing.connectStart。
(3.6) SSL connection time, which is calculated by the formula:
timing.secureConnectionStart>0timing.connectEnd-timing.secure ConnectionStart):0。
(3.7) a content transmission time, which is calculated by the formula:
timing.responseEnd-timing.responseStart。
(3.8) DOM resolution time, which is calculated by the formula:
timing.domInteractive-timing.responseEnd。
(3.9) the resource loading consumes time, and the calculation formula is as follows:
timing.loadEventStart-timing.domContentLoadedEventEnd。
(3.10) requesting a response, which is calculated by the formula:
timing.responseStart-timing.requestStart。
(3.11) the interaction can be carried out for the first time, and the calculation formula is as follows:
timing.domInteractive-timing.fetchStart。
(3.12) the first packet time is calculated according to the formula:
timing.responseStart-timing.domainLookupStart。
(3.13) white screen time, which is calculated by the formula:
performance.getEntriesByType('paint')[0]。
(3.14) drawing the first effective content, wherein the calculation formula is as follows:
performance.getEntriesByType('paint')。
(3.15) drawing time of the first-screen large content, wherein the calculation formula is as follows:
PerformanceObserver('largest-contentful-paint')。
(3.16) the quick opening ratio is calculated by the formula:
the page full load duration is less than or equal to 100% of the samples PV/total samples PV of a certain duration (e.g. 2 s).
(3.17) slow on ratio, which is calculated by the formula:
the page full load duration is greater than or equal to 100% of the samples PV/total samples PV of a certain duration (e.g., 5 s).
It can be seen from the above that, according to the difference of the browsers 10, the system can adopt different performance acquisition schemes, and is compatible with the browsers 10 of the old versions such as IE, so that the data structures of abnormal data in different browsers 10 are unified, and the pressure of the data processing in the later period is reduced.
The using method comprises the following steps: when the whole system runs, a user accesses the module 9 through a website, uses the browser 10 for accessing a webpage, monitors in real time through the probe unit 1 during access, performs script exception acquisition, resource loading exception acquisition and page performance acquisition, collects data through the collected data collecting module 2, generates the remote server 4 through the rear-end interface 3, and stores the data into the database 5.
It is well within the skill of those in the art to implement, without undue experimentation, the present application is not directed to software and process improvements, as they relate to circuits and electronic components and modules.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (10)

1. A system suitable for front-end page performance and error index acquisition is characterized in that: the system comprises a probe unit (1), a collected data summarizing module (2), a rear-end interface (3) and a remote server (4), wherein one end of the probe unit (1) is connected with a browser (10), the other end of the probe unit (1) is connected with the collected data summarizing module (2), the collected data summarizing module (2) is connected with a plurality of rear-end interfaces (3), and the plurality of rear-end interfaces (3) are connected to the remote server (4);
the probe unit (1) is connected with one end of a probe configuration control module (6), and the other end of the probe configuration control module (6) is connected with a probe initialization configuration module (7) and a default configuration module (8);
the probe unit (1) is also connected with one end of the SDK tool module (12).
2. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: the probe unit (1) is internally provided with a script exception acquisition module (101), a resource loading exception acquisition module (102) and a page performance acquisition module (103).
3. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: the browser (10) is connected with a website access module (9).
4. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: one end of the SDK tool module (12) is connected with the browser (10).
5. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: the remote server (4) is connected with a database (5).
6. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: the probe unit (1) is a < script > tag, and the probe unit (1) is connected with a probe producer, and the probe producer is arranged inside the probe configuration control module (6).
7. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: the script exception acquisition module (101) and the resource loading exception acquisition module (102) are internally provided with event monitors of < error, unhandedreject >.
8. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: the probe unit (1) is connected with a tool operation module (11).
9. The system of claim 2, wherein the system is adapted to collect performance and error indicators of front-end pages, and further comprising: the script exception acquisition module (101), the resource loading exception acquisition module (102) and the page performance acquisition module (103) are all connected to the acquired data summarizing module (2).
10. The system of claim 1, wherein the system is adapted to collect performance and error indicators of a front-end page: the probe initialization configuration module (7) is connected with the default configuration module (8).
CN202110143242.6A 2021-02-02 2021-02-02 System suitable for front-end page performance and error index acquisition Pending CN112783734A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110143242.6A CN112783734A (en) 2021-02-02 2021-02-02 System suitable for front-end page performance and error index acquisition

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110143242.6A CN112783734A (en) 2021-02-02 2021-02-02 System suitable for front-end page performance and error index acquisition

Publications (1)

Publication Number Publication Date
CN112783734A true CN112783734A (en) 2021-05-11

Family

ID=75760518

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110143242.6A Pending CN112783734A (en) 2021-02-02 2021-02-02 System suitable for front-end page performance and error index acquisition

Country Status (1)

Country Link
CN (1) CN112783734A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107622015A (en) * 2017-09-25 2018-01-23 北京因特睿软件有限公司 A kind of dataflow analysis method, device, equipment and medium
CN108628719A (en) * 2018-04-19 2018-10-09 杭州朗和科技有限公司 Using the acquisition methods of data, medium, device and computing device
US10135936B1 (en) * 2017-10-13 2018-11-20 Capital One Services, Llc Systems and methods for web analytics testing and web development
CN109739725A (en) * 2018-12-29 2019-05-10 云智慧（北京）科技有限公司 Monitoring method, device and system based on browser and storage medium
CN110309029A (en) * 2019-06-29 2019-10-08 深圳乐信软件技术有限公司 Acquisition method, device, computer equipment and the storage medium of abnormal data
CN110765189A (en) * 2019-09-18 2020-02-07 苏宁云计算有限公司 Exception management method and system for Internet products

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107622015A (en) * 2017-09-25 2018-01-23 北京因特睿软件有限公司 A kind of dataflow analysis method, device, equipment and medium
US10135936B1 (en) * 2017-10-13 2018-11-20 Capital One Services, Llc Systems and methods for web analytics testing and web development
CN108628719A (en) * 2018-04-19 2018-10-09 杭州朗和科技有限公司 Using the acquisition methods of data, medium, device and computing device
CN109739725A (en) * 2018-12-29 2019-05-10 云智慧（北京）科技有限公司 Monitoring method, device and system based on browser and storage medium
CN110309029A (en) * 2019-06-29 2019-10-08 深圳乐信软件技术有限公司 Acquisition method, device, computer equipment and the storage medium of abnormal data
CN110765189A (en) * 2019-09-18 2020-02-07 苏宁云计算有限公司 Exception management method and system for Internet products

Similar Documents

Publication Publication Date Title
CN101292867B (en) Physiological multi-parameter remote monitoring system based on B/S structure
US7739282B1 (en) Method and system for tracking client software use
JP4146347B2 (en) Access log analysis apparatus and access log analysis method
US8335845B2 (en) Web application management method and web system
US9792365B2 (en) Method and system for tracking and gathering multivariate testing data
CN106886494A (en) A kind of automatic interface testing method and its system
CN101324860B (en) Mainboard test system and test method
CN100452792C (en) Method of and system for collecting information about analyzing apparatuses, and the analyzing apparatus
CN101778307A (en) Device for testing functions of set top box
CN104750471A (en) WEB page performance detection and analysis plug-in and method based on browser
CN107483443B (en) Advertisement information processing method, client, storage medium and electronic device
CN101072131A (en) Network operation monitoring method and system
US20080091775A1 (en) Method and apparatus for parallel operations on a plurality of network servers
CN103577034A (en) Method and unit for accessing functional modules of client
US20050144264A1 (en) Diagnosis system for at least one technical system
CN106250397B (en) User behavior characteristic analysis method and device
CN111258904A (en) Webpage element testing method and related device
CN109726011A (en) A kind of network security test macro and implementation method based on embedded artificial intelligence
CN112783734A (en) System suitable for front-end page performance and error index acquisition
CN106447369A (en) Network access data processing method, terminal equipment, and server
CN115757963A (en) User behavior image drawing method based on distributed log analysis
CN115952020A (en) Page abnormity detection method, medium, device and computing equipment
Edmonds et al. Instrumenting the dynamic web
Atterer Logging usage of AJAX applications with the" UsaProxy" HTTP proxy
CN113704344A (en) Data filing method, device, equipment and storage medium based on form template

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