Front-end page monitoring method, computer equipment and computer readable storage medium

By registering data retrieval events on the front-end page and reporting them to the server for processing, page issues encountered by users during access are resolved, user experience is quickly identified and optimized, and data security is improved.

CN118939509APending Publication Date: 2024-11-12SHENZHEN XIAOBURUN TECH CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202411154953.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-22
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

When users visit the front-end page, problems such as unreasonable interaction design, unintuitive operation process, resource loading failure or rendering error may lead to user churn and webpage display errors. Existing technologies are unable to quickly identify and solve these problems.

Method used

When the front-end page is opened, data acquisition events are registered, including error data events and access data events. The event type mapping table and the list of ignored event types are used to determine the events that need to be reported. Event information is acquired and reported to the server. The server processes the information and generates error details, which are then pushed to the page maintenance terminal for optimization.

Benefits of technology

It enables rapid identification of front-end page issues, reduces the scope of the problem's impact, improves user experience, and enhances data security through code obfuscation technology.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939509A_ABST
    Figure CN118939509A_ABST
Patent Text Reader

Abstract

The invention relates to the field of front-end page monitoring, in particular to a front-end page monitoring method, computer equipment and a computer readable storage medium. A specific implementation mode of the method comprises the steps that when a front-end page is opened, a data acquisition event is registered at a front end, and the data acquisition event comprises an error data event monitoring mode and an access data event; when a user accesses a front-end page to trigger a report event, the following processing steps are executed: determining a trigger event type of a current event according to a preset event type mapping table; determining whether the current event needs to be reported or not according to a neglect event type list and a trigger event type in preset parameters; and in response to determining that the current event needs to be reported, obtaining event reporting information of the current event according to a preset reporting parameter. According to the embodiment, the problem can be quickly known by implementing the front-end monitoring strategy, and the information generated by the problem is automatically notified to the corresponding server.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of front-end page monitoring, and in particular to a front-end page monitoring method, a computer device and a computer-readable storage medium. Background Art

[0002] When users visit the front-end page, if there are problems such as unreasonable interaction design and unintuitive operation process, they may lose interest and cause user loss. Or if there are problems such as resource loading failure and rendering errors, the web page may display errors or fail to perform the next operation normally. Summary of the invention

[0003] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0004] Some embodiments of the present disclosure propose a front-end page monitoring method, a computer device, and a computer-readable storage medium to solve the technical problems mentioned in the above background technology section.

[0005] In a first aspect, some embodiments of the present disclosure provide a front-end page monitoring method, the method comprising: when the front-end page is opened, the front-end registers a data acquisition event, wherein the data acquisition event comprises an error data event and an access data event, wherein the error data event comprises a registered document object model error handling hook, a registered application framework error handling hook and an active error reporting event, and the access data event comprises page exposure, element exposure and element click; when the front-end responds to a user accessing the front-end page to trigger a reporting event, the front-end performs the following processing steps: determining the trigger event type of the current event according to a preset event type mapping table; determining whether the current event needs to be reported according to the ignored event type list in the preset parameters and the trigger event type; in response to determining that the current event needs to be reported, obtaining event reporting information of the current event according to the preset reporting parameters, wherein the event reporting information comprises application information, scenario information and user information; reporting the event reporting information to an associated server; in response to receiving the event reporting information, the server adds the event reporting information to an associated event reporting information message queue.

[0006] In a second aspect, the present disclosure further provides a computer device, comprising a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, the method described in any implementation of the first aspect is implemented.

[0007] In a third aspect, the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, wherein when the computer program is executed by a processor, the method described in any implementation manner of the first aspect is implemented.

[0008] The above-mentioned embodiments of the present disclosure have the following beneficial effects: by implementing the front-end monitoring strategy, problems can be quickly known, and the information generated by the problem can be automatically notified to the corresponding server, so as to facilitate and quickly solve the problem and reduce the scope of the problem. The user's usage can be intuitively known, and based on this, the interaction logic can be optimized and adjusted in a targeted manner to improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above and other features, advantages and aspects of the embodiments of the present invention will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar figure labels represent the same or similar elements. It should be understood that the drawings are schematic and that the components and elements are not necessarily drawn to scale.

[0010] Figure 1 is a flow chart of some embodiments of the front-end page monitoring method according to the present disclosure; Figure 2 It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION

[0011] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0012] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0013] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0014] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0015] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0016] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0017] Figure 1 1 is a flow chart of some embodiments of the front-end page monitoring method according to the present disclosure. 100 of some embodiments of the front-end page monitoring method according to the present disclosure is shown. The front-end page monitoring method includes the following steps: Step 101, the front end registers a data acquisition event when the front end page is opened.

[0018] In some embodiments, the front end may register a data acquisition event when the front end page is opened. The above data acquisition event includes: an error data event monitoring method and an access data event. The above error data event monitoring method includes: registering a document object model error handling hook, registering an application framework error handling hook, and actively reporting an error event. The above access data event includes: page exposure, element exposure, and element click. Registering a document object model error handling hook may refer to registering a DOM error handling hook. Actively reporting an error event may represent an active reporting interface, where developers actively report errors. Page exposure may refer to page loading completion events such as onload or route switching of an application framework. Element exposure may be triggered when a specified element enters the visible range. Element click may refer to a user clicking on a specified element to trigger.

[0019] Step 102: When the front end triggers a reporting event in response to a user accessing the front end page, the front end performs the following processing steps: Step 1021: Determine the triggering event type of the current event according to a preset event type mapping table.

[0020] In some embodiments, the front end can determine the trigger event type of the current event according to a preset event type mapping table. The event type mapping table may refer to a mapping table of specific events and event types corresponding to each event. For example, the trigger event type may include: registering a document object model error handling hook, registering an application framework error handling hook, actively reporting an error event, page exposure, element exposure, and element click.

[0021] Step 1022: Determine whether the current event needs to be reported based on the ignored event type list in the preset parameters and the trigger event type.

[0022] In some embodiments, the front end can determine whether the current event needs to be reported based on the ignored event type list in the preset parameters and the above-mentioned trigger event type. The ignored event type list can refer to a type list of trigger events that do not require alarms. That is, when the trigger event type is different from the ignored event type in the ignored event type list, it is determined that the current event needs to be reported. When the trigger event type is the same as the ignored event type in the ignored event type list, it is determined that the current event does not need to be reported.

[0023] Step 1023: in response to determining that the current event needs to be reported, event reporting information of the current event is obtained according to preset reporting parameters.

[0024] In some embodiments, the front end may obtain event reporting information of the current event according to preset reporting parameters in response to determining that the current event needs to be reported. The event reporting information includes: application information, scene information and user information. The reporting parameters may refer to relevant parameter information of the event. The application information may refer to the application information of the front-end page. The scene information may refer to the current scene of the front-end page. The user information may refer to the information of the user who accesses the front-end page.

[0025] Step 1024: Report the above event reporting information to the associated server.

[0026] In some embodiments, the front end may report the event reporting information to an associated server, which may be a server that manages the front end page.

[0027] In an actual application scenario, the front end can report the above event reporting information to the associated server through the following steps: The first step is to determine whether the target data reporting interface is supported based on the user's browser compatibility. The browser compatibility may refer to the compatibility information of the browser used by the user to browse the front-end page. The target data reporting interface may refer to the Navigator.sendBeacon() API interface.

[0028] In the second step, in response to determining that the target data reporting interface is supported, the event reporting information is reported to the associated server through the target data reporting interface. If the target data reporting interface is not supported, a virtual Image element is created to send the reported data to the server.

[0029] Step 103: In response to receiving the event reporting information, the server adds the event reporting information to an associated event reporting information message queue.

[0030] In some embodiments, the server may, in response to receiving the event reporting information, add the event reporting information to an associated event reporting information message queue.

[0031] Furthermore, the server performs the following processing steps for each event reporting information in the event reporting information message queue: The first step is to determine whether the event type corresponding to the above event reporting information is an error type.

[0032] In the second step, in response to determining that the event type corresponding to the event report information is an error type, determine whether the event report information meets a preset alarm condition. The alarm condition may refer to a preset event alarm condition. For example, the alarm condition may be: the same page level error immediately alarms or the warning level error is triggered M times within N minutes.

[0033] The third step is to generate error details information corresponding to the event report information in response to determining that the event report information meets the preset alarm condition, and send the error details information to the associated page maintenance terminal. The error details information may include but is not limited to: page information / user information / event information.

[0034] As an example, if the event type is an error type and meets the preset alarm strategy, such as (immediate alarm for fatal level errors on the same page or M times for warning level errors within N minutes), the error details will be sent to the page maintenance terminal of the corresponding development team. The notification threshold of this type of error will be updated to prevent repeated notifications.

[0035] Furthermore, the server performs the following analysis steps for each associated page: The first step is to determine the page views, unique visitors and page conversion rate of the above page within a preset time period. The associated page may refer to the front-end page managed by the server.

[0036] The second step is to count the click heat maps corresponding to the above pages within the preset time period.

[0037] The third step is to determine the page error information of the above page within a preset time period, wherein the above page error information includes: the number of errors, the error rate and the error resolution time, and the error level of each error event.

[0038] The fourth step is to push the page views, number of unique visitors, conversion rate, click heat map and the above page error information to the monitoring display terminal corresponding to the above page.

[0039] Furthermore, in response to receiving the update instruction of the corresponding front-end page, the server executes the processing update step: The first step is to obtain the page code file corresponding to the above front-end page. The page code file may be a program file of the front-end page to be obfuscated. For example, the page code file may be a file for storing program functions that ensure the normal operation of the front-end page.

[0040] The second step is to generate a program function call graph corresponding to the page code file. The program function call graph includes: a program function node set and a call relationship edge set, and the call relationship edge represents the function call relationship between the program function nodes and the program functions. The program function nodes correspond to the program functions. For example, the program function call graph is a directed graph. Since some program functions do not have a call relationship with other program functions, they are represented as isolated program function nodes in the program function call graph. For example, the page code file can be scanned to determine the program functions included in the page code file, and the program function call graph can be generated according to the call relationship between the program functions. As an example, the page code file may include: program function A, program function B, program function C, program function D, and program function E. The execution of program function B depends on program function A. The execution of program function A depends on program function C. Therefore, the program function call graph includes: program function node A, program function node B, program function node C, program function node D, and program function node E. Among them, program function node A corresponds to program function A, program function node B corresponds to program function B, program function node C corresponds to program function C, program function node D corresponds to program function D, and program function node E corresponds to program function E. Among them, there is a call relationship edge between program function node A and program function node B, from program function node B to program function node A. There is a call relationship edge between program function node A and program function node C, from program function node A to program function node C.

[0041] The third step is to generate a program function call path set and a first program function node set according to the call relationship edge set and the program function node set. The program function call path represents a function call relationship between at least two program function nodes corresponding to the program functions, and the first program function node is a program function node for which there is no function call relationship with the corresponding program function.

[0042] As an example, the page code file may include: program function A, program function B, program function C, program function D, program function E. Among them, the execution of program function B depends on program function A. The execution of program function A depends on program function C. Therefore, the program function call graph includes: program function node A, program function node B, program function node C, program function node D, program function node E. Among them, program function node A corresponds to program function A, program function node B corresponds to program function B, program function node C corresponds to program function C, program function node D corresponds to program function D, and program function node E corresponds to program function E. Among them, there is a call relationship edge between program function node A and program function node B, from program function node B to program function node A. There is a call relationship edge between program function node A and program function node C, from program function node A to program function node C. Therefore, the program function call path may include: program function node B, program function node A, and program node C. The first program function node set may include: program function node D and program function node E.

[0043] The third step may include the following sub-steps: Sub-step 1: Determine the node in-degree value and node out-degree value corresponding to each program function node in the program function node set according to the call relationship edge set.

[0044] The node in-degree value represents the number of program functions that call the program function corresponding to the program function node. The node in-degree value represents the number of program functions called by the program function corresponding to the program function node.

[0045] As an example, the program function corresponding to program function node A is called by program function B, program function C, and program function D, so the node in-degree value of program function node A is 3. The program function corresponding to program function node B calls program function E, program function F, program function G, and program function H, so the node out-degree value of program function node B is 4.

[0046] Sub-step 2: Filter out program function nodes whose corresponding node in-degree value is 0 and whose corresponding node out-degree value is 0 from the program function node set as first program function nodes to obtain the first program function node set.

[0047] In practice, there are program functions that do not need to call other program functions when the function is executed. In this case, the node out-degree value and node in-degree value corresponding to the program function are both 0.

[0048] Sub-step 3: determining the set difference between the first program function node set and the program function node set to obtain a second program function node set.

[0049] Among them, the second program function node set = program function node set - first program function node set. For example, since there is no function call relationship between the program function corresponding to the first program function node, the traversal of the first program function node can be excluded in the subsequent defective program function call path, thereby improving the traversal speed.

[0050] Sub-step 4, for each second program function node in the above-mentioned second program function node set, take the above-mentioned second program function node as the starting node, and perform a deep graph traversal on the above-mentioned program function call graph according to the above-mentioned call relationship edge set to determine the candidate program function call path.

[0051] Sub-step 5, merging overlapping paths of the candidate program function call paths in the obtained candidate program function call path set to generate a program function call path and obtain the above program function call path set. Wherein, overlapping path merging is merging candidate program function call paths with path subset relationship to obtain a program function call path.

[0052] In the fourth step, for each first program function node in the first program function node set, code obfuscation is performed on the program function corresponding to the first program function node according to the program function node description information corresponding to the first program function node. The program function node description information may include: program function name, program function return value type, program function input parameter list, program function return value parameter, and program function return value type. The program function input parameter list includes: input parameters of the program function and parameter types of the input parameters. The program function node description information may include: function variable description information set and function constant description information set. Among them, the function variable description information is used to describe the function variables within the scope of the program function. Function constants are used to describe function constants within the scope of the program function. For example, in the function body of the program function, it is often necessary to define at least one program variable such as the input parameter of the program function, the return value parameter of the program function, a temporary program variable, etc. The function constant description information is used to describe the function constant within the function domain of the program function. The function variable description information may include: function variable type, function variable position, and function variable name. The function variable position represents the relative position of the function variable within the scope of the program function. Function constant description information may include: function constant type, function constant name, function constant value, and function constant position. The function constant position represents the relative position of the function constant within the scope of the program function.

[0053] As an example, the code obfuscation of the program function corresponding to the first program function node may be performed through the following steps: 1. The sum of the number of function variable description information included in the function variable description information set and the number of function constant description information included in the function constant description information set is determined as the target number.

[0054] 2. In response to the target number being less than a preset number, add pseudocode and pseudo-comment to the program function corresponding to the first program function node. The pseudocode may be a code segment that does not affect the operation of the first program function node. For example, pseudocode and pseudo-comment may be randomly selected from a pre-built pseudocode library and pseudo-comment library and added to the program function corresponding to the first program function node. The pseudocode may be an empty program function that does not have a specific function. The pseudo-comment may be an invalid code comment that uses a comment method that matches the file type.

[0055] 3. In response to the target number being greater than or equal to the preset number, for each function variable description information in the function variable description information set included in the program function node description information corresponding to the first program function node, perform the following first code obfuscation step: First, the function variable type included in the function variable description information can be used as the current variable type to obtain a compatible variable type. The current variable type of the function variable is "int" type, and the compatible variable type can be "float" type or "double" type. Then, the variable type of the function variable corresponding to the function variable description information can be updated to a compatible variable type. Afterwards, the function variable corresponding to the function variable description information can be renamed using the Caesar cipher algorithm. Among them, the variable name renaming is reversible in the reverse code obfuscation process, that is, it can be converted from the renamed function variable name to the original function variable name.

[0056] 4. For each function constant description information in the function constant description information set included in the program function node description information corresponding to the first program function node, perform the following second code obfuscation step: First, the current constant type of the function constant can be updated to a compatible constant type. Then, the current constant type and the constant value of the function constant are concatenated and encrypted using an asymmetric encryption algorithm. The compatible constant type is a variable type that is type-compatible with the current constant type of the function constant corresponding to the function constant description information.

[0057] In the fifth step, for each program function calling path in the program function calling path set, code obfuscation is performed on the program function corresponding to the program function node contained in the program function calling path according to the path type and path depth of the program function calling path.

[0058] The fifth step may include the following sub-steps: Sub-step 1, in response to the path type of the program function call path being a recursive path type, generating an intermediate program function set according to the number of recursions, wherein the number of intermediate program functions in the intermediate program function set is the number of recursions, the function names of the intermediate program functions in the intermediate program function set are different, and there is a function call relationship between the intermediate program functions in the intermediate program function set in a recursive order.

[0059] Sub-step 2: Based on the above intermediate program function set, the function bodies of the program functions corresponding to the program function nodes included in the above program function call path are obfuscated.

[0060] Sub-step 3, in response to the path type of the program function call path being a non-recursive path type and the path depth being less than a preset path depth, performing function parameter obfuscation on the program function corresponding to the program function node included in the program function call path. Function parameter obfuscation can be performed on the program function corresponding to the program function node included in the program function call path according to the first code obfuscation step.

[0061] Sub-step 4, in response to the path type of the program function call path being a non-recursive path type and the path depth being greater than or equal to the above-mentioned preset path depth, the program function is replaced according to the function call relationship between the program functions corresponding to the program function nodes contained in the program function call path.

[0062] Step 6: Send the obfuscated page code file to the above front end.

[0063] Therefore, according to the function call relationship, the program functions on the entire call path are obfuscated from the function call behavior. Various forms of code obfuscation are implemented, which increases the difficulty of cracking and reduces the risk of code exposure, thereby ensuring data security.

[0064] Figure 2 A schematic block diagram of the structure of a computer device provided in an embodiment of the present disclosure. The computer device may be a terminal.

[0065] like Figure 2 As shown, the computer device includes a processor, a memory, and a network interface connected via a system bus, wherein the memory may include a non-volatile storage medium and an internal memory.

[0066] The non-volatile storage medium can store an operating system and a computer program. The computer program includes program instructions, and when the program instructions are executed, the processor can execute any front-end page monitoring method.

[0067] The processor is used to provide computing and control capabilities and support the operation of the entire computer equipment.

[0068] The internal memory provides an environment for the operation of the computer program in the non-volatile storage medium. When the computer program is executed by the processor, the processor can execute any front-end page monitoring method.

[0069] The network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art will understand that Figure 2 The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of the present disclosure, and does not constitute a limitation on the computer device to which the scheme of the present disclosure is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0070] It should be understood that the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0071] In one embodiment, the processor is used to run a computer program stored in a memory to implement the following steps: when the front-end page is opened, the front-end registers a data acquisition event, wherein the data acquisition event includes: an error data event monitoring method and an access data event, and the error data event monitoring method includes: registering a document object model error handling hook, registering an application framework error handling hook, and actively reporting an error event, and the access data event includes: page exposure, element exposure, and element click; when the front-end responds to the user accessing the front-end page to trigger a reporting event, the front-end performs the following processing steps: determining the trigger event type of the current event according to a preset event type mapping table; determining whether the current event needs to be reported according to the ignored event type list in the preset parameters and the trigger event type; in response to determining that the current event needs to be reported, obtaining event reporting information of the current event according to the preset reporting parameters, wherein the event reporting information includes: application information, scene information, and user information; reporting the event reporting information to the associated server; in response to receiving the event reporting information, the server adds the event reporting information to the associated event reporting information message queue.

[0072] The embodiments of the present disclosure also provide a computer-readable storage medium, on which a computer program is stored. The computer program includes program instructions. The method implemented when the program instructions are executed can refer to the various embodiments of the front-end page monitoring method of the present disclosure.

[0073] The computer-readable storage medium may be an internal storage unit of the computer device in the aforementioned embodiment, such as a hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (SmartMediaCard, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc., provided on the computer device.

[0074] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0075] The serial numbers of the embodiments of the present disclosure are only for description and do not represent the advantages and disadvantages of the embodiments. The above description is only a specific implementation mode of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present disclosure, and these modifications or replacements should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be based on the protection scope of the claims.

Claims

1. A front-end page monitoring method, the method comprising: When the front-end page is opened, the front-end registers a data acquisition event, wherein the data acquisition event includes: an error data event monitoring method and an access data event, the error data event monitoring method includes: registering a document object model error handling hook, registering an application framework error handling hook and actively reporting an error event, and the access data event includes: page exposure, element exposure and element click; When the front end triggers a reporting event in response to a user accessing the front end page, the front end performs the following processing steps: According to the preset event type mapping table, determine the trigger event type of the current event; Determine whether the current event needs to be reported according to the ignored event type list in the preset parameters and the trigger event type; In response to determining that the current event needs to be reported, obtaining event reporting information of the current event according to preset reporting parameters, wherein the event reporting information includes: application information, scene information and user information; Report the event reporting information to the associated server; In response to receiving the event reporting information, the server adds the event reporting information to the associated event reporting information message queue.

2. The front-end page monitoring method according to claim 1, characterized in that: The method further comprises: The server performs the following processing steps for each event reporting information in the event reporting information message queue: Determine whether the event type corresponding to the event reporting information is an error type; In response to determining that the event type corresponding to the event reporting information is an error type, determining whether the event reporting information meets a preset alarm condition; In response to determining that the event report information satisfies a preset alarm condition, error detail information corresponding to the event report information is generated, and the error detail information is sent to an associated page maintenance terminal.

3. The front-end page monitoring method according to claim 2, characterized in that: The method further comprises: The server performs the following analysis steps for each associated page: Determine the page views, unique visitors and page conversion rate of the page within a preset time period; Count the click heat map corresponding to the page within a preset time period; Determine page error information of the page within a preset time period, wherein the page error information includes: error quantity, error rate and error resolution time, and error level of each error event; The page views, number of unique visitors, page conversion rate, click heat map and the page error information are pushed to the monitoring display terminal corresponding to the page.

4. The front-end page monitoring method according to claim 1, characterized in that: The reporting of the event reporting information to the associated server includes: Determine whether the target data reporting interface is supported based on the user's browser compatibility; In response to determining that the target data reporting interface is supported, the event reporting information is reported to the associated server through the target data reporting interface.

5. The front-end page monitoring method according to claim 1, characterized in that: The method further comprises: In response to receiving the update instruction of the corresponding front-end page, the server executes the processing update step: Obtaining the page code file corresponding to the front-end page; Generate a program function call graph corresponding to the page code file, wherein the program function call graph includes: a program function node set and a call relationship edge set, and the call relationship edge represents the function call relationship between the program function nodes and the program functions; Generate a program function call path set and a first program function node set according to the call relationship edge set and the program function node set, wherein the program function call path represents a function call relationship between program functions corresponding to at least two program function nodes, and the first program function node is a program function node for which no function call relationship exists with respect to the corresponding program function; For each first program function node in the first program function node set, performing code obfuscation on a program function corresponding to the first program function node according to program function node description information corresponding to the first program function node; For each program function call path in the program function call path set, according to the path type and path depth of the program function call path, code obfuscation is performed on the program function corresponding to the program function node included in the program function call path; The obfuscated page code file is sent to the front end.

6. A computer device, wherein: The computer device comprises a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 5 are implemented.

7. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Citation Information

Patent Citations

  • Front-end performance monitoring method and computer readable storage medium

    CN116932329A

  • Front-end page monitoring method and device, computer equipment and storage medium

    CN117331804A

  • Method and device for reporting page error, electronic equipment and storage medium

    CN117950955A