CN111722992A - Front-end error positioning method and device - Google Patents
Front-end error positioning method and device Download PDFInfo
- Publication number
- CN111722992A CN111722992A CN202010534016.6A CN202010534016A CN111722992A CN 111722992 A CN111722992 A CN 111722992A CN 202010534016 A CN202010534016 A CN 202010534016A CN 111722992 A CN111722992 A CN 111722992A
- Authority
- CN
- China
- Prior art keywords
- user
- data
- event
- information
- behavior data
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004140 cleaning Methods 0.000 claims abstract description 15
- 238000001914 filtration Methods 0.000 claims abstract description 13
- 238000004806 packaging method and process Methods 0.000 claims abstract description 12
- 230000006399 behavior Effects 0.000 claims description 79
- 230000004044 response Effects 0.000 claims description 30
- 230000001960 triggered effect Effects 0.000 claims description 14
- 230000003068 static effect Effects 0.000 claims description 13
- 230000007246 mechanism Effects 0.000 claims description 8
- 230000008569 process Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 4
- 230000004807 localization Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 238000000844 transformation Methods 0.000 description 2
- 238000001545 Page's trend test Methods 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/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/3438—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 monitoring of user actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Abstract
The invention discloses a front-end error positioning method and a device, wherein the method comprises the following steps: continuously collecting user track data of a front-end page; classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model; filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data; reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy; and acquiring the access log at the back end, and analyzing and displaying the effective behavior data in the access log to locate and reproduce the error generated at the front end. The invention can accurately master the user behavior to pertinently execute error positioning and recurrence, and improve the working efficiency and the customer experience.
Description
Technical Field
The present invention relates to the field of server front-end, and more particularly, to a front-end error location method and apparatus.
Background
When a server user manages the server daily, the BMC (baseboard management controller) is controlled through a WEB (webpage end) management system. But once the server comes online, many operations of online users on the page are opaque to us.
In the prior art, when the problems on the BMC WEB line are positioned, the problem that the page cannot be reproduced is most afraid. The main causes of the problem difficult to locate are: the problems can not be analyzed by breakpoint positioning, browser log analysis and packet capturing on a machine of a client, and only user description is used as a judgment basis.
Due to the complexity of the front-end page, in many cases, the front-end page is not only related to a program, but also related to machine configuration, a system and a browser of a client, and sometimes real error information cannot be located through description of a problem, operation and error page by a user. Some errors are caused by complicated jump and backspacing of the page, so that a tester is difficult to reproduce the problem, and only can know that the error occurs in the last stop page, so that the problem of positioning the WEB page is difficult. In addition, under the condition of abnormal interfaces, a plurality of functions are completed by the cooperation of the foreground and the background, but because the overtime time is limited on the page, although the data of the background returns normally, the cooperation time of the foreground and the background exceeds the overtime time, the foreground problem, the background problem, the network problem and the like cannot be positioned.
Therefore, when a developer positions a problem, the developer can only guess or eliminate the positioning by the null, so that the actual problem is difficult to position, and the final solution may be to clear page cache, restart equipment and the like, which lacks pertinence, causes poor positioning efficiency and effect, is difficult to reproduce, and affects the customer experience.
Aiming at the problem that positioning in the prior art is lack of pertinence, so that the error positioning efficiency and the effect are poor, no effective solution is available at present.
Disclosure of Invention
In view of this, an object of the embodiments of the present invention is to provide a front-end error positioning method and apparatus, which can accurately grasp user behaviors to perform error positioning and recurrence in a targeted manner, thereby improving work efficiency and customer experience.
In view of the above, a first aspect of the embodiments of the present invention provides a front-end error location method, including the following steps:
continuously collecting user track data of a front-end page;
classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model;
filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data;
reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy;
and acquiring the access log at the back end, and analyzing and displaying the effective behavior data in the access log to locate and reproduce the error generated at the front end.
In some embodiments, the document object model includes a plurality of node elements, and each node element has node object information; the user operation event comprises an event source, an event object pointing to one or more node elements, an event listener and an event operation triggered according to a callback mechanism;
the method further comprises the following steps: event objects in the front-end page are converted from static to dynamic in response to triggering event operations.
In some embodiments, classifying and encapsulating user trajectory data into a plurality of different user behavior data includes:
based on node object information of a plurality of node elements and event operation triggered by an event object, user track data is divided into four types of operation environment, user operation behavior, request response information and error reporting information, and the four types of operation environment data, the user operation behavior data, the request response information data and the error reporting information data are respectively packaged.
In some embodiments, the white list characterizing the valid information includes at least one of: specific operation, valid user, valid address; the blacklist describing the invalid information characteristics comprises at least one of the following: specific operation, invalid user, invalid address.
In some embodiments, the method further comprises: the reverse proxy server clears the access log every predetermined time or in response to the resources occupied by storing or accessing the access log being too high.
A second aspect of an embodiment of the present invention provides a front-end error locating apparatus, including:
a processor; and
a memory storing program code executable by the processor, the program code when executed performing the steps of:
continuously collecting user track data of a front-end page;
classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model;
filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data;
reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy;
and acquiring the access log at the back end, and analyzing and displaying the effective behavior data in the access log to locate and reproduce the error generated at the front end.
In some embodiments, the document object model includes a plurality of node elements, and each node element has node object information; the user operation event comprises an event source, an event object pointing to one or more node elements, an event listener and an event operation triggered according to a callback mechanism;
the method also comprises the following steps: event objects in the front-end page are converted from static to dynamic in response to triggering event operations.
In some embodiments, classifying and encapsulating user trajectory data into a plurality of different user behavior data includes: based on node object information of a plurality of node elements and event operation triggered by an event object, user track data is divided into four types of operation environment, user operation behavior, request response information and error reporting information, and the four types of operation environment data, the user operation behavior data, the request response information data and the error reporting information data are respectively packaged.
In some embodiments, the white list characterizing the valid information includes at least one of: specific operation, valid user, valid address; the blacklist describing the invalid information characteristics comprises at least one of the following: specific operation, invalid user, invalid address.
In some embodiments, the steps further comprise: the reverse proxy server clears the access log every predetermined time or in response to the resources occupied by storing or accessing the access log being too high.
The invention has the following beneficial technical effects: according to the front-end error positioning method and device provided by the embodiment of the invention, the user track data of the front-end page is continuously acquired; classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model; filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data; reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy; the technical scheme of acquiring the access log at the back end, analyzing and displaying the effective behavior data in the access log to position and reproduce the error generated at the front end can accurately master the user behavior to pertinently execute error positioning and reproduction, and improve the working efficiency and the customer experience.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic flow chart of a front-end error location method according to the present invention;
FIG. 2 is a detailed flowchart of a front-end error location method provided by the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
In view of the above-mentioned objects, a first aspect of the embodiments of the present invention proposes an embodiment of a method capable of accurately grasping user behavior to perform error localization and reproduction with pertinence. Fig. 1 is a schematic flow chart of a front-end error location method provided by the present invention.
The front-end error positioning method, as shown in fig. 1, includes the following steps:
step S101: continuously collecting user track data of a front-end page;
step S103: classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model;
step S105: filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data;
step S107: reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy;
step S109: and acquiring the access log at the back end, and analyzing and displaying the effective behavior data in the access log to locate and reproduce the error generated at the front end.
According to the method and the device, the effective data are reported by acquiring the track data of the online user, filtering through the white list, cleaning the data and the like, so that developers can conveniently and rapidly restore the effective data on site according to the track, and the problem of the system is located.
The method integrates and classifies the user track data required to be acquired, analyzes the user behavior data required to be acquired for positioning problems based on a tree structure and an event driven model, and packages the user behavior data into an operation environment object, a user operation behavior object, a request response information object and an error reporting information object; cleaning the acquired user track data, and reporting the data by filtering the data through white list information and black list information because a plurality of junk data exist in the acquired data; the amount of concurrency is relatively high due to the large amount of data of the user behavior. Therefore, in consideration of the excellent performance of nginx, the nginx log pair is used for recording, and in addition, the access and maintenance cost is low, so that the data performance pressure is relieved.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program to instruct relevant hardware to perform the processes, and the processes can be stored in a computer readable storage medium, and when executed, the processes can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a Random Access Memory (RAM), or the like. Embodiments of the computer program may achieve the same or similar effects as any of the preceding method embodiments to which it corresponds.
In some embodiments, the document object model includes a plurality of node elements, and each node element has node object information; the user operation events include event sources, event objects pointing to one or more node elements, event listeners, and event operations triggered according to a callback mechanism. The method further comprises the following steps: event objects in the front-end page are converted from static to dynamic in response to triggering event operations.
In some embodiments, classifying and encapsulating user trajectory data into a plurality of different user behavior data includes: based on node object information of a plurality of node elements and event operation triggered by an event object, user track data is divided into four types of operation environment, user operation behavior, request response information and error reporting information, and the four types of operation environment data, the user operation behavior data, the request response information data and the error reporting information data are respectively packaged.
In some embodiments, the white list characterizing the valid information includes at least one of: specific operation, valid user, valid address; the blacklist describing the invalid information characteristics comprises at least one of the following: specific operation, invalid user, invalid address.
In some embodiments, the method further comprises: the reverse proxy server clears the access log every predetermined time or in response to the resources occupied by storing or accessing the access log being too high.
The method disclosed according to an embodiment of the present invention may also be implemented as a computer program executed by a CPU, which may be stored in a computer-readable storage medium. The computer program, when executed by the CPU, performs the above-described functions defined in the method disclosed in the embodiments of the present invention. The above-described method steps and system elements may also be implemented using a controller and a computer-readable storage medium for storing a computer program for causing the controller to implement the functions of the above-described steps or elements.
The track behavior of the online user of the BMC WEB system is restored, and two aspects can be considered: dynamic information and static information. Due to the contact with GUI (graphical interface) programs, basically two principles are based, tree structures and event driven models.
Tree structure: the front-end page is generally implemented by a document and elements in the document, where the document is a typical tree structure with a hierarchical structure and includes sibling node elements, and parent node elements. For each node in the tree structure, there is a related attribute recording the related information of the node, including type, name, value. The node object can be obtained through the document method and the related attribute of the node.
Event-driven model: when an external event occurs, a corresponding operation is triggered through a callback mechanism, and the mode mainly comprises three elements, namely an event source, an event object and an event listener. The abstract of "events" is most intuitive for graphical interface applications, such as common click and drag events. And pages basically realize related operations through the model.
By analyzing the operation mode of the front-end page, the whole can be controlled, and the source and the target of the page test can be determined. When a page problem is located, information of some nodes (or some elements) in a page and a triggered event in the process need to be recorded in the problem occurrence process, so that a relevant scene is confirmed, analyzed and located.
Static information refers to pages, elements, etc. rendered by a node. The dynamic information means that when a user performs a certain operation and triggers a certain event, the callback function bound to the time starts to execute. Static and dynamic are based on two representations of the current page.
Static page: the developer sets the elements and tags through a tree structure based on the page. The page content is the same, and invariable, regardless of who sees it at any time.
Dynamic page: the content is generally generated by a program at a server side, different people access the page at different times, and the displayed content may be different. This uses the above described concept of page driver to obtain background data through interaction between the front end and the background and render the front end page.
Based on the above consideration, when a problem occurs at the front end, it is necessary to record the page scene during the problem occurrence process. Because pages are basically static and dynamic, recording requires recording under each scene: static elements and tree information of the page, dynamic operation and request information of the user, and response information of a background after the user operates. Besides, some error information exists in the page, which is also a key factor of the positioning problem.
Information is therefore encapsulated into four categories: the operation environment (basic) class, the user operation behavior class, the request response information class and the error reporting information class.
Reporting data: after the data are collected, filtering is carried out according to a white list (designated operation, effective users and effective urls), garbage data are cleaned regularly according to a cleaning strategy, and reporting is carried out according to a reporting strategy.
White list: the white list mainly includes valid user data, valid url data, valid operation data, and the like. In view of performance issues, it is unlikely that all operations will be recorded, so only valid data that meets the white list rules will be transferred to the background, and the remaining garbage data will be discarded.
Cleaning strategy: and backing up and cleaning the data within a specified time to prevent unnecessary stress on the server.
Data query and display: and the reported data is inquired and displayed, so that developers can conveniently solve the online problem.
The following further illustrates embodiments of the invention in terms of specific examples as shown in fig. 2.
Firstly, acquiring user behavior information:
the runtime environment (base) class includes: the system of the client, the type of the client, the client system, the version of a browser of the client, the type of an account number, a user name and a password are recorded through JavaScript, and basic information is stored.
The user operation behavior classes include: the unique UUID number of the user access page, the page access times, the upper entry of the page, and the page operation (button clicking, sliding, page scrolling, resource loading, xpath information of some necessary components, and the like).
The request response information class includes: request type, request parameters, requested data, request link, response data, http status code, request initiation time point, request response time point.
The error information category includes: error code, error description, error type, error file, error time, error row and column position, error timestamp.
Processing the four types of information, rewriting window.
According to the method, the running environment of the page in the client is obtained through the attributes and methods of the user agent and the platForm; the Js error generated in the page is saved by the Js error object JavaScriptErrorInfo. Wherein setCommonProperty is used to set the generic properties of all log objects; acquiring static DOM attributes: monitoring an event callback on the document through an event agent, and passing through the callback; and all attributes on the current dom are acquired through attributes, so that partial track data of the user is acquired.
Then reporting the user behavior:
the online user performs the operation and reports on the page once, which undoubtedly causes performance pressure to the online user, and a lot of junk data exist, which may cause data pollution, so that the data needs to be cleaned first, and the data is filtered and cleaned through a white list mechanism.
And after initialization, inquiring whether the current data is in a white list or not, and if so, reporting. And if the JS report is wrong and the emergency situation is met, directly reporting the JS report.
And finally, executing background data processing, data query and display:
due to the large amount of data of online user behavior, the concurrency is high. Log was therefore processed periodically every five minutes using the rontab of nginx. The collected data are polled at the background regularly, pushed to a foreground page for display, specific positioning information is displayed, page URL and user query are supported, and retrieval results are further focused.
It can be seen from the foregoing embodiments that, in the front-end error location method provided by the embodiments of the present invention, user trajectory data of a front-end page is continuously collected; classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model; filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data; reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy; the technical scheme of acquiring the access log at the back end, analyzing and displaying the effective behavior data in the access log to position and reproduce the error generated at the front end can accurately master the user behavior to pertinently execute error positioning and reproduction, and improve the working efficiency and the customer experience.
It should be particularly noted that, the steps in the embodiments of the front-end error locating method described above can be mutually intersected, replaced, added, or deleted, and therefore, these reasonable permutation and combination transformations to the front-end error locating method should also belong to the scope of the present invention, and should not limit the scope of the present invention to the described embodiments.
In view of the above-mentioned objects, a second aspect of the embodiments of the present invention proposes an embodiment of an apparatus capable of accurately grasping user behavior to perform error localization and reproduction with pertinence. The front-end error locating device includes:
a processor; and
a memory storing program code executable by the processor, the program code when executed performing the steps of:
continuously collecting user track data of a front-end page;
classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model;
filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data;
reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy;
and acquiring the access log at the back end, and analyzing and displaying the effective behavior data in the access log to locate and reproduce the error generated at the front end.
In some embodiments, the document object model includes a plurality of node elements, and each node element has node object information; the user operation events include event sources, event objects pointing to one or more node elements, event listeners, and event operations triggered according to a callback mechanism. The method also comprises the following steps: event objects in the front-end page are converted from static to dynamic in response to triggering event operations.
In some embodiments, classifying and encapsulating user trajectory data into a plurality of different user behavior data includes: based on node object information of a plurality of node elements and event operation triggered by an event object, user track data is divided into four types of operation environment, user operation behavior, request response information and error reporting information, and the four types of operation environment data, the user operation behavior data, the request response information data and the error reporting information data are respectively packaged.
In some embodiments, the white list characterizing the valid information includes at least one of: specific operation, valid user, valid address; the blacklist describing the invalid information characteristics comprises at least one of the following: specific operation, invalid user, invalid address.
In some embodiments, the steps further comprise: the reverse proxy server clears the access log every predetermined time or in response to the resources occupied by storing or accessing the access log being too high.
It can be seen from the foregoing embodiments that, the front-end error positioning apparatus provided in the embodiments of the present invention continuously acquires user trajectory data of a front-end page; classifying and packaging user track data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model; filtering and cleaning user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data; reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy; the technical scheme of acquiring the access log at the back end, analyzing and displaying the effective behavior data in the access log to position and reproduce the error generated at the front end can accurately master the user behavior to pertinently execute error positioning and reproduction, and improve the working efficiency and the customer experience.
It should be particularly noted that the embodiment of the front-end error locating apparatus described above employs the embodiment of the front-end error locating method to specifically describe the working process of each module, and those skilled in the art can easily think that these modules are applied to other embodiments of the front-end error locating method. Of course, since the steps in the embodiment of the front-end error locating method can be mutually intersected, replaced, added, or deleted, the front-end error locating device with these reasonable permutation and combination transformations shall also belong to the scope of the present invention, and shall not limit the scope of the present invention to the embodiment.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items. The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of an embodiment of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (10)
1. A front-end error location method is characterized by comprising the following steps:
continuously collecting user track data of a front-end page;
classifying and packaging the user trajectory data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model;
filtering and cleaning the user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data;
reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy;
and acquiring the access log at the back end, analyzing and displaying the effective behavior data in the access log to position and reproduce errors occurring at the front end.
2. The method of claim 1, wherein the document object model comprises a plurality of node elements, and each of the node elements has node object information; the user operation event comprises an event source, an event object pointing to one or more node elements, an event listener and an event operation triggered according to a callback mechanism;
the method further comprises the following steps: converting the event object in the front-end page from static to dynamic in response to triggering the event operation.
3. The method of claim 2, wherein classifying and encapsulating the user trajectory data into a plurality of different user behavior data comprises:
and dividing the user track data into four types of operation environment, user operation behavior, request response information and error reporting information according to the node object information of the plurality of node elements and the event operation triggered by the event object, and respectively packaging the four types of operation environment data, the user operation behavior data, the request response information data and the error reporting information data.
4. The method of claim 1, wherein the white list describing valid information features comprises at least one of: specific operation, valid user, valid address; the blacklist characterizing invalid information includes at least one of: specific operation, invalid user, invalid address.
5. The method of claim 1, further comprising: the reverse proxy server clears the access log every predetermined time or clears the access log in response to too high resources being occupied to store or access the access log.
6. A front-end error locating device, comprising:
a processor; and
a memory storing program code executable by the processor, the program code when executed performing the steps of:
continuously collecting user track data of a front-end page;
classifying and packaging the user trajectory data into various different user behavior data according to a document object model of a front-end page and a user operation event related to the document object model;
filtering and cleaning the user behavior data by using a white list recording valid information characteristics and/or a black list recording invalid information characteristics to obtain valid behavior data;
reporting the effective behavior data to an access log of a reverse proxy server based on a pre-specified reporting strategy;
and acquiring the access log at the back end, analyzing and displaying the effective behavior data in the access log to position and reproduce errors occurring at the front end.
7. The apparatus of claim 6, wherein the document object model comprises a plurality of node elements, and wherein each of the node elements has node object information; the user operation event comprises an event source, an event object pointing to one or more node elements, an event listener and an event operation triggered according to a callback mechanism;
the steps further include: converting the event object in the front-end page from static to dynamic in response to triggering the event operation.
8. The apparatus of claim 7, wherein classifying and encapsulating the user trajectory data into a plurality of different user behavior data comprises:
and dividing the user track data into four types of operation environment, user operation behavior, request response information and error reporting information according to the node object information of the plurality of node elements and the event operation triggered by the event object, and respectively packaging the four types of operation environment data, the user operation behavior data, the request response information data and the error reporting information data.
9. The apparatus of claim 6, wherein the white list describing valid information features comprises at least one of: specific operation, valid user, valid address; the blacklist characterizing invalid information includes at least one of: specific operation, invalid user, invalid address.
10. The apparatus of claim 6, wherein the steps further comprise: the reverse proxy server clears the access log every predetermined time or clears the access log in response to too high resources being occupied to store or access the access log.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010534016.6A CN111722992A (en) | 2020-06-12 | 2020-06-12 | Front-end error positioning method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010534016.6A CN111722992A (en) | 2020-06-12 | 2020-06-12 | Front-end error positioning method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111722992A true CN111722992A (en) | 2020-09-29 |
Family
ID=72568004
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010534016.6A Withdrawn CN111722992A (en) | 2020-06-12 | 2020-06-12 | Front-end error positioning method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111722992A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20240069908A1 (en) * | 2022-08-29 | 2024-02-29 | Hewlett-Packard Development Company, L.P. | Pull request review based on event-trace streams |
-
2020
- 2020-06-12 CN CN202010534016.6A patent/CN111722992A/en not_active Withdrawn
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20240069908A1 (en) * | 2022-08-29 | 2024-02-29 | Hewlett-Packard Development Company, L.P. | Pull request review based on event-trace streams |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220147411A1 (en) | Session triage and remediation systems and methods | |
| CN110309130A (en) | A kind of method and device for host performance monitor | |
| CN110020339B (en) | Webpage data acquisition method and device based on non-buried point | |
| CN111382023B (en) | Code fault positioning method, device, equipment and storage medium | |
| CN107632920A (en) | A kind of power transmission and transforming equipment monitoring device deep monitored method | |
| CN113760652B (en) | Method, system, device and storage medium for full link monitoring based on application | |
| CN104410671A (en) | Snapshot capturing method and data monitoring tool | |
| CN111722992A (en) | Front-end error positioning method and device | |
| CN112506733B (en) | Fine analysis method, device, equipment and medium for user behavior data | |
| US10706108B2 (en) | Field name recommendation | |
| US10644971B2 (en) | Graph search in structured query language style query | |
| CN116070049B (en) | Method, device and equipment for backtracking page data and readable storage medium | |
| CN111552872A (en) | Method and system for restoring user behavior, electronic device and storage medium | |
| CN109684220A (en) | A kind of browser compatibility analysis method based on event replay | |
| CN115563423A (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN113868005A (en) | Method and device for monitoring webpage abnormity | |
| Li et al. | Modeling web application for cross-browser compatibility testing | |
| Amalfitano et al. | Comprehending Ajax Web applications by the DynaRIA tool | |
| CN116737514B (en) | Automatic operation and maintenance method based on log and probe analysis | |
| US10805411B2 (en) | Interprogram communication with event handling for metric overlays | |
| US10949605B2 (en) | Interprogram communication with event handling for online enhancements | |
| US9916190B1 (en) | Interprogram communication with event handling for subscription tagging | |
| CN115904904A (en) | Web application exception handling method and system based on embedded points | |
| Zhu et al. | Automatic Testing Methods for Response Time of Information Systems | |
| CN116800628A (en) | Log processing method, device, electronic equipment and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200929 |