A page monitoring method, apparatus, computer equipment, and storage medium

Abstract

This application discloses a page monitoring method, apparatus, computer device, and storage medium. The method includes: in response to the start of page loading, obtaining monitoring rule configuration; in response to page operation, obtaining page operation status information, and parsing the page operation status information based on the monitoring rule configuration to determine the page operation status; according to the page operation status, extracting the corresponding monitoring rule from the monitoring rule configuration, and determining the execution parameters corresponding to the page operation status based on the matched monitoring rule; according to the execution parameters, collecting page operation data, processing the operation data, generating processing results, and reporting them. This method can reduce the coupling between monitoring logic and front-end business code, and improve the flexibility, scalability, and efficiency of anomaly identification and handling in front-end page monitoring.

Description

Technical Field

[0001] This application relates to the field of page monitoring technology, and in particular to a page monitoring method, apparatus, computer equipment, and storage medium. Background Technology

[0002] With the expansion of internet applications, front-end systems are increasingly exhibiting a multi-business domain parallel development model. Different business pages place higher demands on monitoring capabilities in terms of performance, stability, and user behavior. Front-end monitoring technology is used to collect and analyze error messages, performance data, and user actions during page operation, and is a crucial technical means to ensure system stability and user experience.

[0003] Existing front-end monitoring solutions are mostly implemented independently by each business system, typically requiring the embedding of monitoring logic into the business code. This results in high coupling between business and monitoring, hindering unified management and scalability. Furthermore, different businesses employ inconsistent monitoring methods and data standards, leading to fragmented monitoring data that makes it difficult to establish a unified analysis and alerting mechanism, increasing the complexity of problem localization and system maintenance. Summary of the Invention

[0004] This application provides a page monitoring method, apparatus, computer equipment, and storage medium that can enhance the ability to identify and handle page malfunctions and performance problems.

[0005] On the one hand, this application provides a page monitoring method, including: Retrieve monitoring rule configuration in response to page loading; In response to page operation, obtain page operation status information, and parse the page operation status information based on the monitoring rule configuration to determine the page operation status; Based on the page's running status, extract the corresponding monitoring rules from the monitoring rule configuration, and determine the execution parameters corresponding to the page's running status based on the matched monitoring rules; Based on the execution parameters, collect the page running data, process the running data, generate the processing results, and report them.

[0006] On the other hand, this application provides a risk assessment device, the device comprising: The loading module is used to retrieve monitoring rule configurations in response to the start of page loading; The parsing module is used to respond to page operation, obtain page operation status information, and parse the page operation status information based on the monitoring rule configuration to determine the page operation status. The parameter calculation module is used to extract the corresponding monitoring rules from the monitoring rule configuration based on the page running status, and determine the execution parameters corresponding to the page running status based on the matched monitoring rules. The execution module is used to collect page running data according to execution parameters, process the running data, generate processing results, and report them.

[0007] In another aspect, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the page monitoring method described in the first aspect.

[0008] In another aspect, this application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the page monitoring method described in the first aspect.

[0009] This application describes a page monitoring method, apparatus, computer device, and storage medium. The method is applied to a front-end page. When the page begins loading, pre-configured monitoring rules are acquired to provide a basic configuration for monitoring during page operation. During page operation, the method continuously acquires the page's running status information and parses this information according to the monitoring rules to determine the current running status. After determining the running status, monitoring rules matching the current running status are selected from the configuration, and corresponding execution parameters are determined based on the matching results to guide the collection and processing of page running data. The page running data collected based on the execution parameters is processed to generate processing results, which are then reported, thereby achieving continuous monitoring of the front-end page's operation. This process enables monitoring rules to dynamically match according to the page running status, ensuring the accuracy and real-time nature of page running data collection and reporting while avoiding unnecessary data collection and processing overhead. It also reduces the coupling between monitoring logic and front-end business code, improving the flexibility, scalability, and efficiency of anomaly identification and handling in front-end page monitoring. Attached Figure Description

[0010] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 This is a flowchart of a page monitoring method in one embodiment.

[0012] Figure 2 This is a structural diagram of a page monitoring method in one embodiment.

[0013] Figure 3 This is a diagram showing the internal structure of a computer device in an embodiment of this application. Detailed Implementation

[0014] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0015] In one embodiment, such as Figure 1 As shown, a page monitoring method is provided, applied to the front end, including: S100: Retrieves monitoring rule configuration in response to page loading; S200: In response to page operation, obtain page operation status information, and parse the page operation status information based on the monitoring rule configuration to determine the page operation status; S300: Based on the page running status, extract the corresponding monitoring rules from the monitoring rule configuration, and determine the execution parameters corresponding to the page running status based on the matched monitoring rules; S400: Based on the execution parameters, collect the page running data, process the running data, generate the processing results, and report them.

[0016] Among them, monitoring rule configuration refers to the set of configurations used to constrain page monitoring behavior, defining the monitoring conditions, triggering logic, and corresponding data collection requirements that need to be monitored under different page running states; page running state information refers to state-related information generated during page loading and running, reflecting the current running status of the page; page running state is the page state result obtained based on the parsing of page running state information, used to distinguish the state type of the page under different running stages or conditions; monitoring rules are specific rule content extracted from the monitoring rule configuration that matches the page running state, used to guide monitoring behavior; execution parameters are parameter information determined according to the monitoring rules, used to clarify the collection method, collection scope, and processing strategy of page running data; page running data is data related to page running collected according to the execution parameters, used to reflect the actual running status of the page.

[0017] Specifically, monitoring rule configuration is introduced when the page begins loading, providing clear monitoring criteria from the initial stage of page operation. During page operation, by continuously acquiring and parsing page operation status information, the current operation status of the page can be dynamically determined, thus avoiding the insufficient adaptability issues caused by relying solely on fixed monitoring logic. After determining the page operation status, the monitoring rule corresponding to that status is extracted from the monitoring rule configuration, and the execution parameters are determined accordingly. This ensures that the collection and processing of page operation data accurately matches the actual page status, avoiding the overhead of repeatedly collecting and processing irrelevant data. Based on the execution parameters, page operation data is collected and processed in a targeted manner, and the processing results are generated and reported, making the reported data more comprehensively reflect the actual operation of the page. Through this implementation process, not only is the targeting and accuracy of page operation data collection and processing improved, but the flexibility and adaptability of page monitoring under different operation states are also enhanced, improving the efficiency of abnormal state identification and problem localization, thereby further improving the overall effect and scalability of front-end page monitoring.

[0018] It should be understood that page monitoring does not indiscriminately collect all page data during page operation. Instead, it first collects page operation status information reflecting the page's operational status, and then parses and determines this information based on the configured monitoring rules. Page operation status information characterizes the page's performance in loading, script execution, and resource requests. By matching this information with preset status determination conditions and rules in the monitoring rule configuration, the page's current operation status is determined. Only when the page operation status meets the corresponding rule conditions is the appropriate monitoring rule extracted from the configuration, and execution parameters are generated to guide subsequent page operation data collection and processing. This approach makes the determination of page operation status a prerequisite for monitoring data collection, enabling differentiated monitoring based on page operation status. This avoids unnecessary data collection when the page is in a normal state, while allowing targeted collection of key monitoring data when the page exhibits abnormal or failed states, thus improving the relevance and overall efficiency of page monitoring.

[0019] In one embodiment, in response to page execution, page execution status information is obtained, and the page execution status information is parsed based on monitoring rule configuration to determine the page execution status. The page execution status information includes: page loading status parameters, script execution status parameters, and resource request status parameters, including: Obtain the status judgment conditions corresponding to the page load status parameters, script execution status parameters, and resource request status parameters respectively from the monitoring rule configuration; The page loading status parameters, script execution status parameters, and resource request status parameters are matched with their corresponding status judgment conditions to obtain the matching results for each status parameter. The page running state is determined based on the preset page state determination rules and the matching results of each state parameter.

[0020] Among them, page loading status parameters are used to reflect the status of the page loading process, representing the completion status and loading performance of the page during the loading phase; script execution status parameters are used to reflect the execution status of scripts on the page, representing the execution status of scripts during page operation; resource request status parameters are used to reflect the resource request status during page operation, representing whether resource requests are normal and their request status; status judgment conditions are pre-configured judgment criteria for different status parameters, used to determine whether the corresponding status parameter meets specific status requirements; preset page status judgment rules are rules used to determine the overall running status of the page by comprehensively considering the matching results of various status parameters; the matching result is the result obtained by comparing the status parameter with the corresponding status judgment condition, representing whether each status parameter meets the corresponding judgment condition.

[0021] Specifically, during page operation, page operation status information is acquired and refined into page loading status parameters, script execution status parameters, and resource request status parameters, providing a multi-dimensional data foundation for determining the page operation status. Based on this, status judgment conditions corresponding to each status parameter are obtained from the monitoring rule configuration, and each status parameter is matched with its corresponding condition to obtain the matching result, thus enabling independent judgment of different operational dimensions. Subsequently, combined with preset page status judgment rules, the matching results of each status parameter are comprehensively analyzed to determine the overall page operation status. Through this process, the determination of page operation status no longer relies on a single indicator but is based on a comprehensive judgment of multiple status parameters, improving the accuracy and stability of page operation status identification. Simultaneously, this approach allows the page operation status to more precisely reflect the actual operation of the page in different stages such as loading, script execution, and resource requests, facilitating earlier detection and differentiation of abnormal states, further enhancing the adaptability and anomaly identification effect of page monitoring in complex operating scenarios.

[0022] In one embodiment, the page running state is determined based on a preset page state determination rule and the matching results of each state parameter, wherein the matching result includes at least one of the following: satisfying the state determination condition and not satisfying the state determination condition, including: The preset page state determination rules are used to pre-establish the correspondence between the matching results of page loading state parameters, script execution state parameters, and resource request state parameters and the page running state; The matching results of page loading status parameters, script execution status parameters, and resource request status parameters are combined, and the combined results are matched with the correspondence established in the preset page status judgment rules. In response to the combination result corresponding to the combination relationship in the preset page state determination rule in which all three state parameters meet the state determination conditions, the page running state is determined to be the normal running state. In response to a combination relationship in which only one state parameter in the preset page state determination rule does not meet the state determination condition, the page running state is determined to be an abnormal running state. If the combination result corresponds to a combination relationship in the preset page state determination rules where at least two state parameters do not meet the state determination conditions, the page running state is determined to be a failed running state.

[0023] Among them, the matching result combination refers to the result formed by combining the matching results corresponding to the page loading status parameters, script execution status parameters, and resource request status parameters, which is used to reflect the overall satisfaction of multiple status parameters; the combination relationship refers to the status relationship corresponding to the matching result combination in the preset page status judgment rules, which is used to represent the page running status type corresponding to the combination; the normal running status refers to the page running status in which all the status parameters corresponding to page loading, script execution, and resource request satisfy the status judgment conditions; the abnormal running status refers to the page running status in which only one of the status parameters corresponding to page loading, script execution, and resource request fails to satisfy the status judgment conditions; the failed running status refers to the page running status in which at least two of the status parameters corresponding to page loading, script execution, and resource request fail to satisfy the status judgment conditions.

[0024] Specifically, in the process of determining the page's running status, a pre-established correspondence between the matching results of page loading status parameters, script execution status parameters, and resource request status parameters and the page's running status provides a clear and configurable rule basis for determining the page's running status. During page operation, the matching results corresponding to each status parameter are combined and matched against the correspondence established in the pre-defined page status determination rules to determine the page's running status. When the combined result corresponds to a combination where all three status parameters meet the status determination conditions, the page is determined to be in a normal running state; when the combined result corresponds to a combination where only one status parameter does not meet the status determination conditions, the page is determined to be in an abnormal running state; when the combined result corresponds to a combination where at least two status parameters do not meet the status determination conditions, the page is determined to be in a failed running state. This determination method based on matching result combinations provides a clear hierarchical division in the process of determining the page's running status, allowing for the differentiation and identification of problems of different degrees, thereby avoiding the problem of mixing minor anomalies with serious failures. Meanwhile, the judgment process is based on rule configuration, which makes it easy to expand and adjust according to actual monitoring needs. This helps to improve the accuracy and interpretability of page operation status identification and further improve the efficiency of anomaly location and handling.

[0025] In one embodiment, based on the page running state, the corresponding monitoring rules are extracted from the monitoring and rule configuration, and the execution parameters corresponding to the page running state are determined based on the matched monitoring rules, including: Based on the page's running status, determine the target monitoring rule corresponding to the page's running status in the monitoring rule configuration; Read the rule values ​​for the collection method, collection range, and collection frequency of page data from the target monitoring rules; The collection method, collection range, and collection frequency rule values ​​are combined to generate execution parameters corresponding to the page's running state.

[0026] Among them, the target monitoring rule refers to the monitoring rule corresponding to the current page running state in the monitoring rule configuration, which is used to indicate the monitoring behavior in the running state of the page; the collection method is the rule content used to indicate how the page running data is collected; the collection scope is the rule content used to limit the type of page running data or data object to be collected; and the collection frequency rule value is the rule content used to limit the time interval or trigger frequency of page running data collection.

[0027] Specifically, after determining the page's running state, the corresponding target monitoring rule is located in the monitoring rule configuration based on the page's running state, enabling the page to match different monitoring strategies under different running states. Subsequently, the collection method, collection range, and collection frequency rule values ​​corresponding to the page data are read from the target monitoring rule, and these rule values ​​are combined to generate execution parameters corresponding to the current page running state. This provides a unified and clear parameter basis for subsequent collection and processing of page running data. Through this process, the collection behavior of page running data can be dynamically adjusted according to changes in the page's running state. This avoids using high-frequency, full-volume data collection methods when the page state is relatively stable, and also avoids missing key information due to insufficient collection strategies when the page is in an abnormal or failed state. This ensures the integrity of critical data while reducing unnecessary performance overhead.

[0028] In one embodiment, based on execution parameters, page execution data is collected, the execution data is processed, processing results are generated, and reported, including: Based on the collection scope and collection frequency, obtain the page operation data; The page execution data is cleaned and statistically processed according to the collection method, and the processing results are generated. The processing result is encapsulated, and the encapsulated processing result is reported to the server.

[0029] Specifically, after collecting page operation data, the required operation data is precisely obtained from the page based on the collection range and frequency defined in the execution parameters. This process ensures that data collection not only meets the actual needs of the page but also allows for dynamic adjustment of the collection frequency, avoiding unnecessary data redundancy. By cleaning and statistically processing the collected data, noise and invalid data are removed, while key indicators reflecting the actual operation status of the page are extracted. Cleaning and statistical processing make the final reported data more concise and accurate, effectively improving the quality of subsequent analysis and decision-making. The processed data is then encapsulated to form standardized processing results, ensuring that the data can be efficiently and accurately transmitted to the server. This encapsulation process not only guarantees the consistency of the data reporting format but also enables the server to quickly parse and process the received data.

[0030] In one embodiment, the method of collecting page execution data based on execution parameters, processing the execution data, generating processing results, and reporting them further includes: During the process of generating the processing results, the runtime environment information of the page is collected, and the business line identifier corresponding to the page is obtained; The processing results, operating environment information, and business line identifiers are assembled into a monitoring message according to a preset message format. Prioritize monitoring messages and write them to the local cache. In response to the detection that the local cache space is insufficient, low-priority messages are eliminated according to the preset overflow protection policy. According to the preset reporting strategy, real-time or delayed reporting is performed on the monitoring messages in the local cache. When a page leave event is detected, batch reporting of unreported messages is triggered. In response to a reporting failure, the system will retry at exponentially increasing time intervals according to a preset retry strategy until the preset maximum number of retries is reached or the reporting is successful.

[0031] Among them, runtime environment information refers to data used to characterize the environment in which the page runs, reflecting the external conditions of the page's operation; business line identifier is information used to identify the business category to which the page belongs, used to distinguish monitoring data under different business scenarios; preset message format refers to a predefined data organization structure used to standardize the assembly method of monitoring data; monitoring message refers to a data unit assembled according to the preset message format, used for monitoring data transmission; page leave event refers to an event used to characterize that the user is about to leave the current page; exponentially increasing time interval refers to the retry interval that gradually increases with the number of retries.

[0032] Specifically, during the generation of processing results, the runtime environment information of the page is collected synchronously, and the business line identifier corresponding to the page is obtained. This ensures that the monitoring data has complete contextual information from the outset, thereby improving the analyzability and traceability of the data. Subsequently, the processing results, runtime environment information, and business line identifier are assembled according to a preset message format to form a uniformly structured monitoring message. This improves parsing efficiency during data transmission and reduces processing costs caused by inconsistent formats. After the monitoring message is generated, its priority is determined and written to the local cache, ensuring that important messages receive higher storage protection. When insufficient local cache space is detected, low-priority messages are evicted according to a preset overflow protection policy. This prioritizes the retention of critical monitoring data under limited storage resources, reducing the risk of losing important data.

[0033] Furthermore, based on a preset reporting strategy, monitoring messages in the local cache are reported in real-time or with a delay. This balances data timeliness and performance overhead, and triggers batch reporting of unreported messages upon detecting a page leave event, helping to reduce data loss due to page closure. In case of reporting failure, retries are performed at exponentially increasing time intervals according to a preset retry strategy until the preset maximum number of retries is reached or the reporting is successful. This avoids the additional network burden caused by frequent retries while improving the success rate of data reporting. Through the above implementation process, monitoring data has higher reliability and integrity at each stage of generation, storage, and transmission, while enhancing the stability of the data reporting mechanism in complex network environments, further improving the data quality and overall monitoring effect of the front-end page.

[0034] In one embodiment, after reporting the encapsulated processing result to the server, the method further includes: After receiving monitoring messages on the server side, the monitoring messages are classified according to the log type identifier carried in the monitoring messages, and stored in the target log databases in multiple cloud log databases respectively. Configure corresponding monitoring query statements for each target log database, and perform periodic queries on the monitoring data in the target log database; When the query result of any target log database meets the preset alarm conditions, the alarm process is triggered and an alarm notification is sent.

[0035] Among them, the log type identifier refers to the information used to identify the log category to which the monitoring message belongs, and is used to classify and manage different types of monitoring messages on the server side; the target log library refers to the database configured in the cloud for storing specific types of monitoring data, and is used to centrally store and manage monitoring data by category.

[0036] Specifically, after receiving the reported monitoring messages on the server side, the messages are classified according to log type identifiers and stored in the corresponding target log databases. This allows different types of monitoring data to be managed and stored independently, avoiding confusion and improving data retrieval efficiency. Subsequently, corresponding monitoring query statements are configured for each target log database to periodically query key indicators and data under specific conditions, enabling continuous monitoring of page operation. When the query result of any target log database meets the preset alarm conditions, the alarm process is immediately triggered and an alarm notification is sent, ensuring that abnormal information can be quickly transmitted to operations or business management personnel. Through this process, monitoring data forms a closed loop from collection to server storage to abnormal alarms, ensuring not only the classification management and retrieval of monitoring data but also timely detection and response to abnormal situations. This significantly improves the agility and operability of front-end page monitoring, as well as the overall system stability and reliability.

[0037] In one embodiment, such as Figure 2 As shown, this application provides a page monitoring device, which includes: a loading module 210, a parsing module 220, a parameter calculation module 230, and an execution module 240, comprising: Load module 210 is used to retrieve monitoring rule configurations in response to the start of page loading; The parsing module 220 is used to respond to page operation, obtain page operation status information, and parse the page operation status information based on the monitoring rule configuration to determine the page operation status; The parameter calculation module 230 is used to extract the corresponding monitoring rules from the monitoring rule configuration according to the page running status, and determine the execution parameters corresponding to the page running status based on the matched monitoring rules. The execution module 240 is used to collect page running data according to the execution parameters, process the running data, generate processing results and report them.

[0038] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described page monitoring method embodiments at runtime.

[0039] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0040] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described page monitoring method embodiments.

[0041] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, such as Figure 3 As shown, to clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of functionality in the above description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0042] The page monitoring method provided in this application has been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and its core ideas. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method of page monitoring, characterized by, include: Retrieve monitoring rule configuration in response to page loading; In response to page operation, obtain page operation status information, and parse the page operation status information based on the monitoring rule configuration to determine the page operation status; Based on the page running status, extract the corresponding monitoring rules from the monitoring rule configuration, and determine the execution parameters corresponding to the page running status based on the matched monitoring rules; Based on the execution parameters, collect page running data, process the page running data, generate processing results, and report them.

2. The method of claim 1, wherein, The process involves responding to page execution, acquiring page execution status information, and parsing this information based on the monitoring rule configuration to determine the page execution status. This page execution status information includes: page loading status parameters, script execution status parameters, and resource request status parameters, including: Obtain the status judgment conditions corresponding to the page loading status parameter, the script execution status parameter, and the resource request status parameter respectively from the monitoring rule configuration; The page loading status parameters, the script execution status parameters, and the resource request status parameters are matched with the corresponding status determination conditions to obtain the matching results of each status parameter. The page running state is determined based on the preset page state determination rules and the matching results of each state parameter.

3. The method of claim 2, wherein, The page running state is determined by judging the page running state according to the preset page state judgment rules and the matching results of each state parameter, wherein the matching result includes at least one of the following: satisfying the state judgment condition and not satisfying the state judgment condition, including: The preset page state determination rule is used to pre-establish the correspondence between the matching result combination of the page loading state parameter, the script execution state parameter and the resource request state parameter and the page running state; The matching results of the page loading status parameters, the script execution status parameters, and the resource request status parameters are combined, and the combined results are matched with the correspondence established in the preset page status determination rules. In response to the combination result corresponding to the combination relationship in the preset page state determination rule in which all three state parameters meet the state determination conditions, the page running state is determined to be a normal running state. In response to a combination result that corresponds to a combination relationship in the preset page state determination rule in which only one state parameter does not meet the state determination condition, the page running state is determined to be an abnormal running state. In response to a combination result that corresponds to a combination relationship in the preset page state determination rule where at least two state parameters do not meet the state determination conditions, the page running state is determined to be a failed running state.

4. The method of claim 1, wherein, The step of extracting the corresponding monitoring rules from the monitoring rule configuration based on the page running state, and determining the execution parameters corresponding to the page running state based on the matched monitoring rules, includes: Based on the page's running status, determine the target monitoring rule corresponding to the page's running status in the monitoring rule configuration; Read the collection method, collection range, and collection frequency rule values ​​of the page data from the target monitoring rules; The collection method, the collection range, and the collection frequency rule value are combined to generate execution parameters corresponding to the page running state.

5. The method of claim 4, wherein, The step of collecting page execution data according to the execution parameters, processing the page execution data, generating processing results, and reporting them includes: The page operation data is obtained from the page according to the collection range and the collection frequency; The page operation data is cleaned and statistically processed according to the collection method described above, and the processing result is generated. The processing result is encapsulated, and the encapsulated processing result is reported to the server.

6. The method of claim 5, wherein, The step of collecting page execution data according to the execution parameters, processing the page execution data, generating processing results, and reporting them further includes: During the generation of the processing result, the runtime environment information of the page is collected, and the business line identifier corresponding to the page is obtained; The processing result, the operating environment information, and the business line identifier are assembled into a monitoring message according to a preset message format. The monitoring messages are assigned a priority and written to the local cache. In response to the detection that the local cache space is insufficient, the monitoring messages with low priority are eliminated according to the preset overflow protection policy. According to the preset reporting strategy, the monitoring messages in the local cache are reported in real time or with a delay. In response to the detection of a page leave event, the monitoring messages that have not been reported are reported in batches. In response to a reporting failure, the system will retry at exponentially increasing time intervals according to a preset retry strategy until the preset maximum number of retries is reached or the reporting is successful.

7. The method of claim 6, wherein, After reporting the encapsulated processing result to the server, the process further includes: After receiving the monitoring message on the server side, the monitoring message is classified according to the log type identifier carried in the monitoring message, and stored in the target log library in multiple cloud log libraries respectively. Configure corresponding monitoring query statements for each of the target log databases, and periodically query the monitoring data in the target log databases; In response to the query result of any of the target log databases meeting the preset alarm conditions, an alarm process is triggered and an alarm notification is sent.

8. A page monitoring apparatus characterized by comprising: The device includes: The loading module is used to retrieve monitoring rule configurations in response to the start of page loading; The parsing module is used to respond to page operation, obtain page operation status information, and parse the page operation status information based on the monitoring rule configuration to determine the page operation status. The parameter calculation module is used to extract the corresponding monitoring rules from the monitoring rule configuration according to the page running status, and determine the execution parameters corresponding to the page running status based on the matched monitoring rules. The execution module is used to collect the page running data according to the execution parameters, process the page running data, generate processing results, and report them.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images