CN108334429A - Method, apparatus and system for investigating front end page problem - Google Patents
Method, apparatus and system for investigating front end page problem Download PDFInfo
- Publication number
- CN108334429A CN108334429A CN201710044404.4A CN201710044404A CN108334429A CN 108334429 A CN108334429 A CN 108334429A CN 201710044404 A CN201710044404 A CN 201710044404A CN 108334429 A CN108334429 A CN 108334429A
- Authority
- CN
- China
- Prior art keywords
- monitoring information
- page
- information
- end page
- requested
- 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
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
- G06F11/3082—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting the data filtering being achieved by aggregating or compressing the monitored data
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Computer Hardware Design (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the present application discloses a kind of method and device for investigating front end page problem and a kind of method and device providing front end page monitoring information and a kind of system for investigating front end page problem.The method includes：Receive the monitoring information about front end page that client device uploads；It is stored into database about the monitoring information of front end page described in receiving；The monitoring information for reading page requested from the database according to inquiry request carries out problem investigation for developer to the page requested.Using the above method, the problem of existing front end developer is difficult to carry out investigation to the page to go wrong is solved the problems, such as.
Description
Technical Field
The embodiment of the application relates to the technical field of front-end pages, in particular to a method and a device for troubleshooting front-end page problems, a method and a device for providing front-end page monitoring information, and a system for troubleshooting front-end page problems.
Background
With the development of application services, service logic is also complicated, and a front-end page may need to be displayed in different environments, for example, different systems (IOS, Android, etc.), different clients, webviews of different manufacturers, and the like.
Because the front-end page needs to adapt to various different scenes, the difficulty of front-end developers in developing the front-end page is increased, and the problems to be considered are increased. In some scenarios, if a problem (for example, a style or logic problem) occurs in the front-end page during the display process, since the front-end developer cannot know the relevant information of the front-end page during the display process, it is difficult to perform problem troubleshooting on the page with the problem, and particularly, the troubleshooting difficulty is greater for the front-end page with the even-appearing problem.
How to obtain the relevant information of the front-end page in the display process and provide developers to use the information to investigate problem pages becomes a problem to be solved urgently.
Disclosure of Invention
The embodiment of the application provides a method for troubleshooting a front-end page problem, and aims to solve the problem that an existing front-end developer is difficult to troubleshoot a problem of a page with a problem.
The method for checking the front-end page problem comprises the following steps:
receiving monitoring information about a front-end page uploaded by client equipment;
storing the received monitoring information about the front-end page in a database;
and reading the monitoring information of the requested page from the database according to the query request, so that a developer can perform problem troubleshooting on the requested page.
Optionally, the step of reading the monitoring information of the requested page from the database according to the query request for a developer to perform problem troubleshooting on the requested page includes:
and reading the monitoring information of the requested page from the database according to the query request, and displaying the monitoring information of the requested page for a developer to perform problem troubleshooting on the requested page.
Optionally, the monitoring information of the requested page at least includes: screenshot of the requested page;
the displaying the monitoring information of the requested page comprises:
and reproducing the display process of the requested page on the client device at least by displaying the screenshot of the requested page.
Optionally, the number of the screenshots of the requested page is two or more, and each screenshot corresponds to a different acquisition time point;
the reproducing the presentation process of the requested page on the client device at least by displaying the screenshot of the requested page comprises:
and at least displaying the screenshots of the requested page in sequence according to the acquisition time point to reproduce the display process of the requested page on the client equipment in an animation effect.
Optionally, the monitoring information of the requested page further includes the following auxiliary information: html content of the page, page user events, page memory, CPU utilization rate, and/or debugging information;
the reproducing the presentation process of the requested page on the client device at least by displaying the screenshot of the requested page comprises:
and reproducing the display process of the requested page on the client equipment by displaying the screenshot of the requested page and the auxiliary information.
Optionally, the receiving monitoring information about a front-end page uploaded by the client device includes:
receiving monitoring information about the front-end page uploaded by a JS script of the front-end page; and/or the presence of a gas in the gas,
and receiving monitoring information about the front-end page uploaded by a client displaying the front-end page.
Optionally, the receiving monitoring information about a front-end page uploaded by the client device includes:
receiving monitoring information about a front-end page uploaded by the client equipment at regular time; or,
and periodically receiving monitoring information about a front-end page uploaded by the client equipment.
Optionally, the information carried by the query request at least includes: a URL of the requested page and an identification of a client device that is presenting the requested page; or the URL of the requested page, and the user identification using the requested page.
Optionally, the information carried by the query request further includes: the time point or time period is collected.
Optionally, after reading the monitoring information of the requested page from the database according to the query request, before the developer performs problem troubleshooting on the requested page, the method further includes:
and if the read monitoring information comprises partial information subjected to oversampling processing and/or compression processing, carrying out corresponding reduction processing on the partial information.
An embodiment of the present application further provides a device for troubleshooting front-end page problems, the device includes:
the receiving information unit is used for receiving monitoring information about a front-end page uploaded by the client equipment;
the storage information unit is used for storing the monitoring information about the front-end page received by the receiving unit into a database;
and the query information unit is used for reading the monitoring information of the requested page from the database according to the query request, so that a developer can perform problem troubleshooting on the requested page.
The embodiment of the present application further provides a method for providing front-end page monitoring information, which is characterized by including:
in the process of displaying a front-end page, acquiring monitoring information about the front-end page based on a JS script inserted in the front-end page;
and uploading the monitoring information to a server side for a developer to perform problem troubleshooting.
Optionally, the obtaining of the monitoring information about the front end page based on the JS script inserted into the front end page includes:
acquiring the monitoring information by using a JS script inserted in the front-end page; and/or the presence of a gas in the gas,
and calling an interface provided by a client through a JS script inserted in the front-end page to acquire the monitoring information.
Optionally, before the step of uploading the monitoring information to the server, the method further includes:
performing data processing on the monitoring information to reduce the uploaded data volume;
the uploading the monitoring information to a server includes: and uploading the monitoring information subjected to data processing to a server.
Optionally, the performing data processing on the monitoring information includes:
if similar monitoring information corresponding to the same monitoring item exists in the monitoring information, sampling the similar monitoring information, wherein the similarity between one monitoring information and each other monitoring information in the similar monitoring information is greater than a preset threshold value; and/or the presence of a gas in the gas,
and compressing the repeated data and/or the screenshots in the monitoring information.
Optionally, in the process of displaying the front end page, before acquiring the monitoring information about the front end page based on the JS script inserted in the front end page, the method includes:
and configuring the monitoring items included in the monitoring information by using the JS script.
Optionally, the uploading the monitoring information to a server includes:
uploading the monitoring information to a server by the JS script; and/or the presence of a gas in the gas,
and uploading the monitoring information to a server by the client.
Optionally, the uploading, by the client, the monitoring information to the server includes:
the JS script calls an interface provided by a client to store the monitoring information in the local part of the client;
and the client uploads the stored monitoring information to the server.
Optionally, the uploading the monitoring information to a server includes:
uploading the monitoring information to a server at regular time; or,
and uploading the monitoring information to a server periodically.
The embodiment of the application also provides a device for providing front-end page monitoring information, which comprises
The information acquisition unit is used for acquiring monitoring information about a front-end page based on a JS script inserted in the front-end page in the process of displaying the front-end page;
and the uploading information unit is used for uploading the monitoring information acquired by the acquiring information unit to a server side for a developer to perform problem troubleshooting.
An embodiment of the present application further provides a system for troubleshooting front-end page problems, the system includes: the device for checking the front-end page problem, the device for providing the front-end page monitoring information and the database for storing the front-end page monitoring information are described above. .
Compared with the prior art, the embodiment of the application has the following advantages:
the embodiment of the application provides a method for checking front-end page problems, which comprises the following steps: receiving monitoring information about a front-end page uploaded by client equipment; storing the received monitoring information about the front-end page in a database; and reading the monitoring information of the requested page from the database according to the query request, so that a developer can perform problem troubleshooting on the requested page.
According to the method for troubleshooting the front-end page problems, the monitoring information about the front-end page is uploaded to the server side through the client side device, the monitoring information is stored in the database through the server side, when the front-end page has problems or even occasional problems with low probability, developers can conveniently troubleshoot the problems by querying the monitoring information of the front-end page with the problems from the database. Therefore, the problem that the existing front-end developer is difficult to perform problem troubleshooting on the page with the problems is solved, and the efficiency of performing problem troubleshooting on the front-end page is remarkably improved.
Drawings
Fig. 1 is a flowchart of a method for providing front-end page monitoring information according to a first embodiment of the present application.
FIG. 2 is a flow chart of a method for troubleshooting front-end page problems provided by a second embodiment of the present application;
fig. 3 is a schematic diagram of an apparatus for providing front-end page monitoring information according to a third embodiment of the present application.
Fig. 4 is a schematic diagram of an apparatus for troubleshooting front-end page problems according to a fourth embodiment of the present application.
Fig. 5 is a schematic diagram of a system for troubleshooting front-end page problems according to a fifth embodiment of the present application.
Fig. 6 is a schematic diagram of a specific example of a system for troubleshooting front-end page problems provided in a fifth embodiment of the present application.
Detailed Description
In the following description, numerous specific details are set forth to provide a thorough understanding of embodiments of the present application. The embodiments of this application are capable of embodiments in many different forms than those described herein and can be similarly generalized by those skilled in the art without departing from the spirit and scope of the embodiments of this application and, therefore, the embodiments of this application are not limited to the specific embodiments disclosed below.
A first embodiment of the present application provides a method for providing front-end page monitoring information. Referring to fig. 1, a flowchart of a method for providing front-end page monitoring information according to a first embodiment of the present application is shown. This is explained in detail below with reference to fig. 1. The method provided by the embodiment is implemented by the client device.
And step S101, in the process of displaying the front end page, acquiring monitoring information about the front end page based on the JS script inserted in the front end page.
In the step, monitoring information about a front-end page is acquired by inserting a JS script (JavaScript script) into the front-end page, which is the basis for uploading the monitoring information.
The front-end page generally refers to a page displayed on the client device for the user to browse.
The JS script may be a remote monitoring JS script inserted into the front-end page and used for acquiring monitoring information of the front-end page. By inserting the remote monitoring JS script into the front-end page, the remote monitoring JS script can acquire monitoring information about the front-end page in the process of displaying the front-end page.
The monitoring information may include data about the front-end page acquired by the remote monitoring JS script having authority or acquired by calling the client interface. The monitoring information may include information corresponding to the following monitoring items: the method comprises the steps of page screenshot (screenshot for short), html content of a page, page user events, page memory, CPU utilization rate, JS stack and debugging information. The debugging information (also called debug information) may include log information recorded actively and prompt information such as an error and a warning reported by a browser kernel.
For each front-end page, information corresponding to all of the listed monitoring items may be obtained, or information corresponding to any one or more of the listed monitoring items may be obtained.
Preferably, in order to flexibly acquire the monitoring information, before acquiring the monitoring information about the front-end page based on the JS script inserted into the front-end page, the monitoring items included in the monitoring information may be configured by using the JS script according to a specific requirement.
Specifically, a remote monitoring object may be generated by using the remote monitoring JS script, and a monitoring item included in the monitoring information is configured by using the remote monitoring object, for example, whether a page screenshot is included, whether a page user event is included, whether debugging information is included, whether a page memory is included, and the like. In specific implementation, a corresponding monitoring item may be configured in the configuration information of the remote monitoring object, if a certain monitoring item is not included, the configuration information of the monitoring item may be set to false or 0, and if a certain monitoring item is included, the configuration information of the monitoring item may be set to true or 1. For example, if the page screenshot and the debugging information need to be acquired, the configuration information of the corresponding two monitoring items is set to true, and the configuration information of the other monitoring items is set to false.
In specific implementation, in the process of performing configuration by using the remote monitoring JS script, whether to perform sampling or compression processing on the acquired monitoring information may also be configured (for a description of the sampling and compression processing, refer to the relevant description in step S102).
Acquiring monitoring information about the front end page based on the JS script inserted into the front end page may include: the monitoring information is acquired by using the JS script inserted into the front-end page, and the monitoring information may further include: and calling an interface provided by a client through a JS script inserted in the front-end page to acquire the monitoring information. The client described in this embodiment generally refers to a container for displaying a front-end page, and may be an APP for displaying the front-end page, for example.
For example, an html2canvas () function or a similar function may be called in the remote monitoring JS script to obtain a page screenshot of the front-end page, or the page screenshot may be obtained in the remote JS script by calling an interface (e.g., a Hybrid interface) provided by the client and utilizing the capability of the client; for another example, the monitoring information about the page memory, the CPU utilization, and the like may be obtained by calling an interface provided by the client.
In practical application, the monitoring information of the front-end page can be obtained by adopting any one of the two modes, or the two modes can be combined for use. In an application scene without a client, the monitoring information of a front-end page can be acquired only by using the remote monitoring JS script, so that the implementation difficulty is simplified; in an application scenario with a client, the monitoring information of the front-end page can be preferably acquired by using an interface provided by the client, so that the information acquisition process can be more efficient by using the capability of the client.
The process of acquiring the monitoring information of the front-end page, which may also be referred to as a process of acquiring the monitoring information, may further record a corresponding acquisition time point when acquiring the monitoring information corresponding to each monitoring item in specific implementation, that is, the monitoring information about the front-end page may further include: the time point (also called timestamp) is collected, so that the problem troubleshooting of the front-end page is convenient for developers according to the time point.
The embodiment of this step has been described above by taking an example in which an independent remote monitoring JS script is inserted into the front page. In specific implementation, the functions of configuring the monitoring item, obtaining the monitoring information, and uploading the monitoring information related to step 102 may be performed by an independent remote monitoring JS script, or may be dispersed in a plurality of JS scripts inserted into the front-end page, for example: it is also possible to insert into a plurality of JS scripts for performing business functions.
And S102, uploading the monitoring information to a server side for a developer to perform problem troubleshooting.
In this step, the monitoring information about the front-end page acquired in step S101 is uploaded to the server. Specifically, the monitoring information may be uploaded to the server by the client device through an interface provided by the server.
The client device may be a device that displays a front-end page, such as a personal computer, a tablet computer, a smart phone, and the like. And the server is used for receiving the monitoring information of the front-end page and storing the monitoring information in the database. The interface provided by the server side can be an interface based on an HTTP protocol or an HTTPS protocol.
In this step, the JS script inserted into the front-end page and the interface provided by the server can upload the monitoring information to the server, or the client can upload the monitoring information to the server by using the interface provided by the server. The monitoring information is uploaded to the server by the client, the acquired monitoring information can be stored locally at the client by calling an interface provided by the client through a JS script inserted into a front-end page, and then the stored monitoring information is uploaded to the server by the client.
For example, a front page screenshot obtained by canvas and other technologies can be directly uploaded to the server by the JS script; the JS script may also be used to call an interface provided by the client to store the front-end screenshot on a storage medium local to the client, for example: and uploading the screenshot to a server by the client.
In specific implementation, an implementation mode that monitoring information is uploaded by a JS script can be adopted; the embodiment of storing the monitoring information in the client and uploading the monitoring information by the client can also be adopted; it is also possible to combine the two modes, that is, it is also possible that part of the monitoring information is uploaded by the JS script and part of the monitoring information is uploaded by the client.
In specific implementation, the uploading timing of the monitoring information may be preconfigured, and the uploading operation may be executed according to the configured timing in this step.
Taking the uploading of the monitoring information by using the JS script as an example, if the remote monitoring object is configured to upload the monitoring information in a timed or periodic manner in the life cycle of the front-end page in advance, the step may upload the acquired monitoring information of the front-end page to the server in a timed or periodic manner.
In specific implementation, the timed or periodic uploading mode may be combined with the real-time uploading mode, for example: the screenshot for the front-end page may be uploaded every 5s, for page user events, for example: and if the user clicks the event of the button, uploading the user click event to the server in the JS script corresponding to the onclick event in real time.
Similarly, for the implementation of uploading the monitoring information by the client, the client may also be configured in advance to use a regular, timed, and/or active uploading manner, so that in this step, the client may upload the stored monitoring information to the server in a corresponding manner.
Preferably, in order to reduce the amount of uploaded data and reduce the occupation of network bandwidth, this embodiment further provides a preferred implementation manner of performing data processing on the monitoring information acquired in step 101 to reduce the amount of uploaded data. Namely: before uploading the monitoring information to the server, data processing may be performed on the monitoring information to reduce the amount of data to be uploaded. Because the more data uploaded to the server by the client device, the more network bandwidth is occupied, and the higher the probability of uploading failure is, the data is optimized before the monitoring information is uploaded, and the data uploading amount is reduced. In a specific implementation, the data processing may be performed by a JS script or a client that prepares to perform the upload operation.
And carrying out data processing on the monitoring information, wherein the data processing comprises the following steps: compressing and/or sampling the monitoring information according to the similarity calculation result. The embodiment of sampling the monitoring information according to the similarity calculation result may be as follows: if similar monitoring information corresponding to the same monitoring item exists in the monitoring information, sampling the similar monitoring information, wherein the similarity between one monitoring information (hereinafter referred to as reference monitoring information) in the similar monitoring information and other monitoring information is greater than a preset threshold value. The specific sampling processing may be that, for the similar monitoring information, only the complete content of the reference monitoring information is retained in the monitoring data, and the other monitoring information may be replaced by identification information representing that the content of the other monitoring information is similar to the reference monitoring information, so that all the contents of the similar monitoring information may not be uploaded. In a specific implementation, the preset threshold may be set according to a requirement, for example, set to 99%.
For example, after the front-end page is loaded and displayed, the client uploads debug information of the front-end page every 10 seconds, if the acquired monitoring information in 10 seconds contains debug information acquired 5 times in sequence, and through similarity calculation, it is found that the similarity between the debug information acquired 4 times later and the debug information acquired for the first time exceeds a preset threshold, then the debug information acquired 5 times is similar monitoring information, and in this case, sampling processing can be performed, that is: only the first acquired debug information (corresponding to the acquisition time point t1) is reserved in the monitoring information to be uploaded, and the later 4 debug information is replaced by identification information, which represents that the acquired debug information is similar to the debug information acquired at the time point t 1. The method has the advantages that sampling is performed only once within 10s, so that the data volume of monitoring information uploading is reduced, the occupation of network bandwidth is reduced, and the uploading failure probability is reduced.
The compression processing may be to compress the repeated data and/or the screenshot in the monitoring information. For example, a compression representation mode may be adopted for repeated data in the monitoring information, and a corresponding image compression algorithm may be adopted for compressing the screenshot.
After the data processing operation is executed, the processed monitoring information can be uploaded to the server side for storage by the server side, so that developers can inquire and refer when checking the front-end page problems.
In specific implementation, the information uploaded to the server in this step generally includes not only monitoring information, but also identification information for identifying a corresponding front-end page, where the identification information may be: the URL information of the front-end page and the client device identifier, or the URL information of the front-end page and the user identifier using the front-end page (the information may be obtained from cookie data), so that the front-end page and the monitoring information may be stored in a server side in a corresponding manner, so as to query the corresponding monitoring information according to the front-end page identifier.
So far, through the above steps S101 to S102, the embodiment of the method for providing front-end page monitoring information provided in this embodiment is described. As can be seen from the above description, the embodiment realizes the collection of the monitoring information about the front-end page and uploads the collected monitoring information to the server, thereby providing a data base for the developers to query and troubleshoot problems.
A second embodiment of the present application provides a method for troubleshooting front-end page problems. Referring to fig. 2, a flowchart of a method for troubleshooting front-end page problems provided in accordance with a second embodiment of the present application is shown. This is explained in detail below with reference to fig. 2. The method for troubleshooting the front-end page problem provided by the embodiment is usually implemented at the server.
Step S201, receiving monitoring information about a front-end page uploaded by a client device.
The client device refers to a client device displaying a front-end page.
The uploaded monitoring information about the front-end page may include: the monitoring method comprises the following steps of page screenshot, html content of a page, page user events, page memory, CPU utilization rate and/or debugging information, wherein each monitoring information can have corresponding acquisition time point information. The uploaded information may also include information identifying the corresponding front-end page, such as URL information and client device identification of the front-end page, or URL information and user identification of the front-end page using the front-end page.
The receiving of the monitoring information about the front-end page uploaded by the client device includes: receiving the monitoring information uploaded by the JS script of the front-end page; and/or receiving the monitoring information uploaded by the client displaying the front-end page. Specifically, the monitoring information about the front-end page uploaded by the client device can be received through an interface provided by the server (for example, an interface based on the HTTP protocol or the HTTPs protocol).
The receiving of the monitoring information about the front-end page uploaded by the client device may include periodically or periodically receiving the monitoring information about the front-end page uploaded by the client device. Receiving regularly or periodically, depending on the uploading mode of the client device, and if the client device uploads the monitoring information in a regular uploading mode, the server receives the monitoring information regularly; and if the client equipment adopts a regular uploading mode, the server side receives the monitoring information regularly.
Step S202, storing the received monitoring information about the front-end page in a database.
In this step, the monitoring information about the front-end page received in step S201 is stored in a database, so that a developer can query and troubleshoot problems when a problem occurs on a certain front-end page.
The database, generally referred to as a repository, organizes, stores, and manages data according to a data structure. The database includes a relational database, such as Oracle, SQL Server, which may be used to query information from the database using database query statements. The database and the service end can be deployed on the same physical server, and in order to ensure the safety of data storage, the database and the service end can also be deployed on different physical servers.
Since the information stored in the database may include the JS script inserted into the front-end page and/or the monitoring information about the front-end page obtained by the client displaying the front-end page, when a problem occurs on a certain front-end page, even if the problem occurs occasionally, a developer may quickly locate and troubleshoot the problem by querying the monitoring information in the database, so as to improve the efficiency of troubleshooting the front-end page, and refer to the description in step S203 specifically.
Step S203, reading the monitoring information of the requested page from the database according to the query request, so that a developer can perform problem troubleshooting on the requested page.
After the received monitoring information about the front-end page is stored in the database, a developer can inquire the monitoring information in the database according to requirements and perform problem troubleshooting on the front-end page according to the acquired monitoring information.
The requested page may be a front-end page on which a developer needs to obtain relevant monitoring information, and generally refers to a front-end page on which problems occur and need to be checked.
When a developer needs to perform problem troubleshooting on a front-end page with a problem, the front-end page can be used as a requested page to initiate a query request to a server, for example: the query request for the requested page is entered using the keyboard. The information carried by the query request may include identification information of the requested page, for example: a URL of the requested page and an identification of a client device that is presenting the requested page; or the URL of the requested page, and the user identification using the requested page. In this step, the received query request may be converted into a corresponding database query statement (e.g., SQL statement), and then the database query statement is sent to the database for storing the monitoring information, and the query result returned by the database is received, so as to obtain the monitoring information of the requested page.
The information carried by the query request may further include: the time point or time period is collected. Because the monitoring information of the requested page is usually large in data volume, and the time when the requested page has a problem can be generally known, developers can acquire the monitoring information of the requested page at a certain time point or in a certain time period by carrying the acquisition time point or the time period in the request information. For example, not only the identification information of the requested page but also "2017/1/115: 00-15: 10" is carried in the query request, the monitoring information collected in the time period of "2017/1/115: 00-15: 10" for the requested page can be obtained from the database.
It should be noted that, after the monitoring information of the requested page is read from the database according to the query request, if the read monitoring information includes partial information that is subjected to oversampling processing and/or compression processing, corresponding restoration processing may be performed on the partial information.
For example, if the monitoring information of the requested page includes debug information subjected to oversampling, the complete debug information serving as a sampling reference may be acquired according to the corresponding identification information in the monitoring information, and the complete debug information is used to replace the corresponding identification information, so that the debug information in the monitoring information is restored; if the requested page monitoring information contains the compressed screenshot picture, the compressed picture can be decompressed by adopting a corresponding decompression algorithm, so that the screenshot in the monitoring information is restored.
After obtaining the monitoring information of the requested page, the developer may perform problem troubleshooting on the requested page by using the monitoring information, for example, may analyze the read monitoring information by using some data analysis tools, and further determine a problem.
Preferably, in order to facilitate more intuitive problem troubleshooting, the present embodiment also provides a preferred implementation of displaying the monitoring information. That is, after the monitoring information of the requested page is read from the database according to the query request, the read monitoring information of the requested page may be displayed on a display device, so that the developer may perform problem troubleshooting more intuitively.
Further preferably, when the monitoring information of the requested page is displayed, if the monitoring information of the requested page includes a screenshot of the requested page, a presentation process of the requested page on the client device may be reproduced by displaying the screenshot of the requested page. According to the reproduced screenshot, a developer can intuitively know the specific display condition of the page when the requested page has a problem, and the problem troubleshooting is facilitated.
In specific implementation, if the monitoring information of the requested page includes not only the screenshot but also one or any combination of the following auxiliary information: the method comprises the steps that html content of a page, page user events, page memory, CPU utilization rate and debug information are displayed, and therefore when the display process of a requested page on the client device is reproduced, screenshots and auxiliary information of the requested page can be displayed. By combining and displaying the screenshot of the requested page and the auxiliary information, a developer can fully utilize the displayed information to perform problem troubleshooting, so that the problem positioning is quicker.
In specific implementation, if the number of the screenshots of the requested page acquired from the database is two or more, and each screenshot corresponds to a different acquisition time point, when the presentation process of the requested page on the client device is reproduced, the presentation process of the requested page on the client device can be reproduced in an animation effect by sequentially displaying the screenshots of the requested page according to the acquisition time points. For example, the monitoring information of the requested page includes a plurality of page shots that are different from each other due to a user operation (clicking, sliding, or panning, etc.), and each frame of page shot may be reproduced in an animation effect when a presentation process of the requested page is reproduced. Therefore, developers can visually see various changes of the front-end page in the display process, and the problem troubleshooting is facilitated.
In the same way, when the display process of the requested page on the client device is reproduced, the display process of the requested page on the client device can be reproduced in an animation manner by sequentially displaying the screenshot of the requested page and the corresponding auxiliary information according to the acquisition time point. The auxiliary information corresponding to a certain screenshot may be auxiliary information acquired synchronously with the screenshot (i.e., the same acquisition time point), or auxiliary information acquired between the screenshot and the next screenshot. By adopting the method, the display condition of the requested page, which operations are executed by the user aiming at the requested page, which changes are caused to the requested page, the debug information corresponding to each screenshot and the like can be intuitively reproduced, so that the information of the requested page can be displayed for developers from various angles.
The following illustrates the presentation of the requested page on the client device with an animation. For example: on the client device, a first frame screenshot of a certain front-end page is acquired at a first acquisition time point, a user clicks a 'details' button, details are further shown in the front-end page, a second frame screenshot containing the details shown in the front-end page is acquired at a second acquisition time point, then the user slides up through a finger to cause the front-end page to roll upwards, a third frame screenshot of the front-end page is acquired at a third acquisition time point, and the three frames of screenshots and user events (clicking the button and sliding up the finger) are uploaded to a server as monitoring information of the front-end page. When a developer learns that the front-end page displayed by the client device between the first time point and the third time point has a problem, an inquiry request for the front-end page can be input at the server, and a time period indication from the first time point to the third time point is carried in the inquiry request, so that the server can acquire stored monitoring information from a database according to the inquiry request of a user, including three screenshots and a user event, and sequentially display the information in an animation form, namely: firstly, displaying a first frame screenshot, and displaying that a user executes the operation of clicking a detail button; then displaying a second frame screenshot, and displaying that the user executes finger sliding operation; and finally, displaying the third frame screenshot.
According to the preferred scheme, after the monitoring information of the requested page is read from the database according to the query request, the read monitoring information of the requested page is displayed, the page screenshots at different acquisition time points can be displayed in an animation mode, other information contained in the monitoring information is synchronously displayed, and therefore developers can conveniently and intuitively perform problem troubleshooting.
So far, through the above steps S201 to S203, the embodiment of the method for troubleshooting the front-end page problem provided by the present embodiment is described. As can be seen from the above description, when a problem occurs in a front-end page, a developer can read monitoring information of a requested page from the database according to a requirement, which is helpful for positioning and troubleshooting the problem.
Corresponding to the method for providing the front-end page monitoring information, the embodiment of the application also provides a device for providing the front-end page monitoring information. Since the embodiments of the apparatus are substantially similar to the embodiments of the method, they are described in a relatively simple manner, and reference may be made to the description of the embodiments of the method for relevant points. The device embodiments described below are merely illustrative. The embodiment of the device for providing the front-end page monitoring information comprises the following steps:
referring to fig. 3, a schematic diagram of an apparatus for providing front-end page monitoring information according to a third embodiment of the present application is shown.
The device for providing front-end page monitoring information comprises: an information acquisition unit 301 and an information uploading unit 302.
An obtaining information unit 301, configured to, during presentation of a front end page, obtain monitoring information on the front end page based on a JS script inserted in the front end page;
and an upload information unit 302, configured to upload the monitoring information acquired by the information acquisition unit to a server, so that a developer may perform problem troubleshooting.
Optionally, the information obtaining unit includes:
the JS script acquisition information subunit is used for acquiring the monitoring information by using the JS script inserted in the front-end page; and/or the presence of a gas in the gas,
and the client interface acquisition information subunit is used for calling the interface provided by the client to acquire the monitoring information through the JS script inserted in the front-end page.
Optionally, the apparatus further comprises:
the data processing unit is used for carrying out data processing on the monitoring information before the information uploading unit works so as to reduce the uploaded data volume;
the upload information unit is specifically configured to upload the monitoring information subjected to data processing to the server.
Optionally, the data processing unit includes:
the sampling processing subunit is configured to, if similar monitoring information corresponding to the same monitoring item exists in the monitoring information, perform sampling processing on the similar monitoring information, where the similarity between one monitoring information existing in the similar monitoring information and each of the other monitoring information is greater than a preset threshold; and/or the presence of a gas in the gas,
and the compression processing subunit is used for compressing the repeated data and/or the screenshot in the monitoring information.
Optionally, the monitoring information includes information corresponding to the following monitoring items:
page screenshots, html content of a page, page user events, page memory, CPU utilization, and/or debugging information.
Optionally, the apparatus further includes:
and the configuration unit is used for configuring the monitoring items included in the monitoring information by using the JS script before the information acquisition unit works.
Optionally, the upload information unit includes:
the JS script uploading information subunit is used for uploading the monitoring information to the server by the JS script; and/or the presence of a gas in the gas,
and the client side information uploading subunit is used for uploading the monitoring information to the server side by the client side.
Optionally, the client upload information subunit includes:
the information storage subunit is used for calling an interface provided by a client by the JS script to store the monitoring information in the local part of the client;
and the uploading information subunit is used for uploading the stored monitoring information to the server side by the client side.
Optionally, the upload information unit includes:
the timed uploading information subunit is used for uploading the monitoring information to a server at a fixed time; or,
and the regular uploading information subunit is used for regularly uploading the monitoring information to a server.
Corresponding to the method for checking the front-end page problem provided above, the embodiment of the present application further provides an apparatus for checking the front-end page problem. Since the embodiments of the apparatus are substantially similar to the embodiments of the method, they are described in a relatively simple manner, and reference may be made to the description of the embodiments of the method for relevant points. The device embodiments described below are merely illustrative. The device for checking the front-end page problem comprises the following embodiments:
referring to fig. 4, a schematic diagram of an apparatus for troubleshooting front-end page problems according to a fourth embodiment of the present application is shown.
The device for checking the front end page problem comprises: a received information unit 401, a stored information unit 402, and a query information unit 403.
A receive information unit 401, configured to receive monitoring information about a front-end page uploaded by a client device;
a storing information unit 402, configured to store the monitoring information about the front-end page received by the receiving unit in a database;
and an information query unit 403, configured to read monitoring information of the requested page from the database according to the query request, so that a developer performs problem troubleshooting on the requested page.
Optionally, the query information unit includes:
the query information subunit is used for reading the monitoring information of the requested page from the database according to the query request;
and the display subunit is used for displaying the monitoring information of the requested page so as to provide developers for performing problem troubleshooting on the requested page.
Optionally, the display subunit includes:
and the reproduction subunit is used for reproducing the presentation process of the requested page on the client device at least by displaying the screenshot of the requested page when the monitoring information of the requested page at least comprises the screenshot of the requested page.
Optionally, the reproducing subunit includes:
and the animation display subunit is used for displaying the screenshots of the requested page in sequence according to the acquisition time points at least when the number of the screenshots of the requested page is two or more and each screenshot corresponds to different acquisition time points, so as to reproduce the display process of the requested page on the client equipment in an animation effect.
Optionally, the monitoring information of the requested page further includes the following auxiliary information: html content of the page, page user events, page memory, CPU utilization rate, and/or debugging information;
the reproducing subunit includes:
and the screenshot and auxiliary information display subunit is used for reproducing the display process of the requested page on the client equipment by displaying the screenshot of the requested page and the auxiliary information.
Optionally, the information receiving unit includes:
the JS script information receiving subunit is used for receiving monitoring information about the front-end page uploaded by the JS script of the front-end page; and/or the presence of a gas in the gas,
and the client information receiving subunit is used for receiving the monitoring information about the front-end page uploaded by the client displaying the front-end page.
Optionally, the information receiving unit includes:
the timing receiving subunit is used for receiving the monitoring information about the front-end page uploaded by the client device at regular time; or,
and the regular receiving subunit is used for regularly receiving the monitoring information about the front-end page uploaded by the client device.
Optionally, the monitoring information includes: page screenshots, html content of a page, page user events, page memory, CPU utilization, and/or debugging information.
Optionally, the information carried by the query request at least includes: a URL of the requested page and an identification of a client device that is presenting the requested page; or the URL of the requested page, and the user identification using the requested page.
Optionally, the information carried by the query request further includes: the time point or time period is collected.
Optionally, the query information unit is specifically configured to: and reading the monitoring information of the requested page from the database according to the query request, if the read monitoring information comprises partial information subjected to oversampling processing and/or compression processing, performing corresponding reduction processing on the partial information, and providing the reduced monitoring information for developers to perform problem troubleshooting on the requested page.
An embodiment of the present application further provides a system for troubleshooting front-end page problems, as shown in fig. 5, the system includes the apparatus 501 for providing front-end page monitoring information, the apparatus 502 for troubleshooting front-end page problems, and the database 503 for storing front-end page monitoring information, which are described in the foregoing embodiments. The device for providing the front-end page monitoring information can be deployed in a personal computer or a mobile terminal device (such as a smart phone). The device for checking the front-end page problem can be deployed on one server or two servers: one of the pages is used for receiving and storing monitoring information related to a front-end page, and the other page is used for reading the monitoring information of a requested page from a database according to a query request. The database storing the front-end page monitoring information may be deployed on the same server as the device for troubleshooting front-end page problems (if the device for troubleshooting front-end page problems is deployed on two servers, the database may be deployed on any one of the servers), or may be deployed on a different physical server from the device for troubleshooting front-end page problems.
Fig. 6 is a schematic diagram of a specific example of a system for troubleshooting front-end page problems according to a fifth embodiment of the present application, where the device for providing front-end page monitoring information is deployed in a smartphone, the device for troubleshooting front-end page problems is deployed in two servers a and B, the server a is configured to store monitoring information about a front-end page uploaded by the smartphone, the server B is configured to query and display the monitoring information about the front-end page, and the database for storing the front-end page monitoring information is deployed in the server C.
The processing flow of the system for checking front-end page problems provided by the embodiment is as follows: 1) in the process of displaying a front-end page, the smart phone acquires monitoring information about the front-end page by using a JS script inserted in the front-end page, and then uploads the monitoring information to a server A; 2) after receiving monitoring information about a front-end page, the server A stores the monitoring information about the front-end page into a database of a server C; 3) when a certain front-end page has a problem, the server B queries from the server C according to the query request of a developer to obtain a page screenshot of the problem page and other auxiliary information; 4) and the server B displays the inquired screenshot of the page and the auxiliary information on a display for a developer to perform problem troubleshooting.
Although the preferred embodiments of the present invention have been disclosed in the foregoing description, the preferred embodiments of the present invention are not limited thereto, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the embodiments of the present invention.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Claims (21)
1. A method for troubleshooting front-end page problems, comprising:
receiving monitoring information about a front-end page uploaded by client equipment;
storing the received monitoring information about the front-end page in a database;
and reading the monitoring information of the requested page from the database according to the query request, so that a developer can perform problem troubleshooting on the requested page.
2. The method according to claim 1, wherein the step of reading the monitoring information of the requested page from the database according to the query request for a developer to perform problem troubleshooting on the requested page comprises:
and reading the monitoring information of the requested page from the database according to the query request, and displaying the monitoring information of the requested page for a developer to perform problem troubleshooting on the requested page.
3. The method of claim 2, wherein the monitoring information of the requested page comprises at least: screenshot of the requested page;
the displaying the monitoring information of the requested page comprises:
and reproducing the display process of the requested page on the client device at least by displaying the screenshot of the requested page.
4. The method according to claim 3, wherein the number of the screenshots of the requested page is two or more, and each screenshot corresponds to a different acquisition time point;
the reproducing the presentation process of the requested page on the client device at least by displaying the screenshot of the requested page comprises:
and at least displaying the screenshots of the requested page in sequence according to the acquisition time point to reproduce the display process of the requested page on the client equipment in an animation effect.
5. The method of claim 3, wherein the monitoring information of the requested page further comprises auxiliary information listed as follows: html content of the page, page user events, page memory, CPU utilization rate, and/or debugging information;
the reproducing the presentation process of the requested page on the client device at least by displaying the screenshot of the requested page comprises:
and reproducing the display process of the requested page on the client equipment by displaying the screenshot of the requested page and the auxiliary information.
6. The method of claim 1, wherein receiving the monitoring information about the front-end page uploaded by the client device comprises:
receiving monitoring information about the front-end page uploaded by a JS script of the front-end page; and/or the presence of a gas in the gas,
and receiving monitoring information about the front-end page uploaded by a client displaying the front-end page.
7. The method of claim 1, wherein receiving the monitoring information about the front-end page uploaded by the client device comprises:
receiving monitoring information about a front-end page uploaded by the client equipment at regular time; or,
and periodically receiving monitoring information about a front-end page uploaded by the client equipment.
8. The method of claim 1, wherein the information carried by the query request at least comprises: a URL of the requested page and an identification of a client device that is presenting the requested page; or the URL of the requested page, and the user identification using the requested page.
9. The method of claim 8, wherein the information carried by the query request further comprises: the time point or time period is collected.
10. The method according to claim 1, after reading the monitoring information of the requested page from the database according to the query request, before the requested page is subjected to problem troubleshooting by a developer, further comprising:
and if the read monitoring information comprises partial information subjected to oversampling processing and/or compression processing, carrying out corresponding reduction processing on the partial information.
11. An apparatus for troubleshooting front end page problems, comprising:
the receiving information unit is used for receiving monitoring information about a front-end page uploaded by the client equipment;
the storage information unit is used for storing the monitoring information about the front-end page received by the receiving unit into a database;
and the query information unit is used for reading the monitoring information of the requested page from the database according to the query request, so that a developer can perform problem troubleshooting on the requested page.
12. A method for providing front-end page monitoring information, comprising:
in the process of displaying a front-end page, acquiring monitoring information about the front-end page based on a JS script inserted in the front-end page;
and uploading the monitoring information to a server side for a developer to perform problem troubleshooting.
13. The method of claim 12, wherein obtaining monitoring information about the front-end page based on the JS script inserted within the front-end page comprises:
acquiring the monitoring information by using a JS script inserted in the front-end page; and/or the presence of a gas in the gas,
and calling an interface provided by a client through a JS script inserted in the front-end page to acquire the monitoring information.
14. The method according to claim 12, further comprising, before the step of uploading the monitoring information to a server:
performing data processing on the monitoring information to reduce the uploaded data volume;
the uploading the monitoring information to a server includes: and uploading the monitoring information subjected to data processing to a server.
15. The method of claim 14, wherein the data processing the monitoring information comprises:
if similar monitoring information corresponding to the same monitoring item exists in the monitoring information, sampling the similar monitoring information, wherein the similarity between one monitoring information and each other monitoring information in the similar monitoring information is greater than a preset threshold value; and/or the presence of a gas in the gas,
and compressing the repeated data and/or the screenshots in the monitoring information.
16. The method according to claim 12, wherein in the process of showing the front page, before acquiring the monitoring information about the front page based on the JS script inserted in the front page, the method comprises:
and configuring the monitoring items included in the monitoring information by using the JS script.
17. The method of claim 12, wherein uploading the monitoring information to a server comprises:
uploading the monitoring information to a server by the JS script; and/or the presence of a gas in the gas,
and uploading the monitoring information to a server by the client.
18. The method of claim 17, wherein uploading the monitoring information to the server by the client comprises:
the JS script calls an interface provided by a client to store the monitoring information in the local part of the client;
and the client uploads the stored monitoring information to the server.
19. The method of claim 12, wherein uploading the monitoring information to a server comprises:
uploading the monitoring information to a server at regular time; or,
and uploading the monitoring information to a server periodically.
20. An apparatus for providing front-end page monitoring information, comprising
The information acquisition unit is used for acquiring monitoring information about a front-end page based on a JS script inserted in the front-end page in the process of displaying the front-end page;
and the uploading information unit is used for uploading the monitoring information acquired by the acquiring information unit to a server side for a developer to perform problem troubleshooting.
21. A system for troubleshooting front-end page problems, comprising: the apparatus for troubleshooting front end page problems of claim 11, the apparatus for providing front end page monitoring information of claim 20, and a database for storing the front end page monitoring information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710044404.4A CN108334429A (en) | 2017-01-19 | 2017-01-19 | Method, apparatus and system for investigating front end page problem |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710044404.4A CN108334429A (en) | 2017-01-19 | 2017-01-19 | Method, apparatus and system for investigating front end page problem |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108334429A true CN108334429A (en) | 2018-07-27 |
Family
ID=62922163
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710044404.4A Pending CN108334429A (en) | 2017-01-19 | 2017-01-19 | Method, apparatus and system for investigating front end page problem |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108334429A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110865843A (en) * | 2018-08-09 | 2020-03-06 | 阿里巴巴集团控股有限公司 | Page backtracking, information backup and problem solving method, system and equipment |
| CN110955438A (en) * | 2019-12-03 | 2020-04-03 | 北京博睿宏远数据科技股份有限公司 | Method, device and equipment for monitoring performance of small program and storage medium |
| CN111381847A (en) * | 2018-12-29 | 2020-07-07 | 阿里巴巴集团控股有限公司 | Information processing method and device |
| CN112256524A (en) * | 2020-09-27 | 2021-01-22 | 湖南映客互娱网络信息有限公司 | Web front-end monitoring method and system based on screen recording playback |
| CN114138863A (en) * | 2021-11-29 | 2022-03-04 | 挂号网（杭州）科技有限公司 | Troubleshooting method, device, electronic device and storage medium |
| CN115270035A (en) * | 2022-07-25 | 2022-11-01 | 神策网络科技（北京）有限公司 | Method, device, device and storage medium for processing abnormal page data |
| CN119902955A (en) * | 2024-12-30 | 2025-04-29 | 北京五八信息技术有限公司 | Information processing method, device, storage medium and program product |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101193008A (en) * | 2007-03-29 | 2008-06-04 | 腾讯科技（深圳）有限公司 | A method and system for replaying user webpage access track |
| CN104182327A (en) * | 2013-05-23 | 2014-12-03 | 携程计算机技术（上海）有限公司 | Client error log collecting method and client error log collecting system |
| CN104572043A (en) * | 2013-10-16 | 2015-04-29 | 阿里巴巴集团控股有限公司 | Method and device for embedding points for controls of client application in real time |
| CN104750471A (en) * | 2013-12-30 | 2015-07-01 | 上海格尔软件股份有限公司 | WEB page performance detection and analysis plug-in and method based on browser |
| CN105490869A (en) * | 2015-11-19 | 2016-04-13 | 浪潮(北京)电子信息产业有限公司 | Monitoring data acquisition method, device and system |
-
2017
- 2017-01-19 CN CN201710044404.4A patent/CN108334429A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101193008A (en) * | 2007-03-29 | 2008-06-04 | 腾讯科技（深圳）有限公司 | A method and system for replaying user webpage access track |
| CN104182327A (en) * | 2013-05-23 | 2014-12-03 | 携程计算机技术（上海）有限公司 | Client error log collecting method and client error log collecting system |
| CN104572043A (en) * | 2013-10-16 | 2015-04-29 | 阿里巴巴集团控股有限公司 | Method and device for embedding points for controls of client application in real time |
| CN104750471A (en) * | 2013-12-30 | 2015-07-01 | 上海格尔软件股份有限公司 | WEB page performance detection and analysis plug-in and method based on browser |
| CN105490869A (en) * | 2015-11-19 | 2016-04-13 | 浪潮(北京)电子信息产业有限公司 | Monitoring data acquisition method, device and system |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110865843A (en) * | 2018-08-09 | 2020-03-06 | 阿里巴巴集团控股有限公司 | Page backtracking, information backup and problem solving method, system and equipment |
| CN110865843B (en) * | 2018-08-09 | 2024-03-26 | 阿里巴巴集团控股有限公司 | Page backtracking, information backup and problem solving method, system and equipment |
| CN111381847A (en) * | 2018-12-29 | 2020-07-07 | 阿里巴巴集团控股有限公司 | Information processing method and device |
| CN111381847B (en) * | 2018-12-29 | 2023-04-25 | 阿里巴巴集团控股有限公司 | Information processing method and device |
| CN110955438A (en) * | 2019-12-03 | 2020-04-03 | 北京博睿宏远数据科技股份有限公司 | Method, device and equipment for monitoring performance of small program and storage medium |
| CN112256524A (en) * | 2020-09-27 | 2021-01-22 | 湖南映客互娱网络信息有限公司 | Web front-end monitoring method and system based on screen recording playback |
| CN114138863A (en) * | 2021-11-29 | 2022-03-04 | 挂号网（杭州）科技有限公司 | Troubleshooting method, device, electronic device and storage medium |
| CN115270035A (en) * | 2022-07-25 | 2022-11-01 | 神策网络科技（北京）有限公司 | Method, device, device and storage medium for processing abnormal page data |
| CN119902955A (en) * | 2024-12-30 | 2025-04-29 | 北京五八信息技术有限公司 | Information processing method, device, storage medium and program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108334429A (en) | Method, apparatus and system for investigating front end page problem | |
| CN113687974B (en) | Client log processing method and device and computer equipment | |
| CN111818123B (en) | Network front-end remote playback method, device, equipment and storage medium | |
| CN110362547B (en) | Method and device for encoding, analyzing and storing log file | |
| US11526413B2 (en) | Distributed tracing of huge spans for application and dependent application performance monitoring | |
| CN112749059A (en) | Front-end abnormity monitoring method, device and system | |
| CN109359109B (en) | Data processing method and system based on distributed stream computing | |
| CN113378036B (en) | Page operation analysis, embedding method, device, equipment and storage medium | |
| CN112416775B (en) | Software automatic test method and device based on artificial intelligence and electronic equipment | |
| US10346281B2 (en) | Obtaining and analyzing a reduced metric data set | |
| CN112364267B (en) | Front-end data acquisition method and device | |
| CN111752834A (en) | Automated testing method and device | |
| CN111475423A (en) | Data entry method and device, electronic equipment and readable storage medium | |
| CN113419932B (en) | Equipment performance analysis method and device | |
| CN110582016A (en) | video information display method, device, server and storage medium | |
| US10498616B1 (en) | System and method for implementing a client performance capture tool | |
| CN119292885A (en) | Performance analysis method, electronic device, storage medium and program product | |
| CN117950955A (en) | Method and device for reporting page fault, electronic equipment and storage medium | |
| CN112380115A (en) | Regression testing method and device, electronic equipment and storage medium | |
| CN115460288B (en) | Method and device for detecting call link | |
| CN112416735A (en) | Application program detection method and device, terminal equipment and storage medium | |
| CN110347597A (en) | Interface test method, device, storage medium and the mobile terminal of picture servers | |
| CN117034255A (en) | Application error reporting repair method, device, equipment and medium | |
| CN109756393B (en) | Information processing method, system, medium, and computing device | |
| CN116069535A (en) | Abnormality monitoring method and device, equipment and medium thereof |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180727 |