Performance monitoring method and device based on front-end webpage, equipment and storage medium

Abstract

The embodiment of the invention provides a performance monitoring method and device based on a front-end webpage, equipment and a storage medium, and belongs to the technical field of financial science and technology. The method comprises the following steps: acquiring webpage monitoring configuration information of a target webpage; obtaining webpage monitoring data of the target webpage according to the webpage monitoring configuration information; wherein the webpage monitoring data comprises page operation parameters and interface operation parameters, and the page operation parameters comprise webpage loading duration information and page access times; performing page performance evaluation processing on the target webpage according to the webpage loading duration information and the page access times to obtain target page performance evaluation data; performing interface performance evaluation on the target webpage according to the interface operation parameters to obtain interface performance evaluation data; and performing performance level division on the target webpage according to the target page performance evaluation data and the interface performance evaluation data to obtain webpage performance level information. According to the embodiment of the invention, the performance monitoring of the front-end webpage can be simpler and more visual.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and in particular to a performance monitoring method and apparatus, device and storage medium based on a front-end web page. Background Art

[0002] In order to increase the diversity of financial services, the front-end web pages of financial systems are becoming more and more complex, and the interactions with the user end are also increasing. Therefore, the performance issues of the front-end web pages indirectly affect the quality of financial services. In order to improve the user experience when using the financial system for financial services, it is necessary to monitor the performance of the front-end web pages in real time so that developers can adjust the front-end web pages in time according to the monitoring data to ensure the stable operation of the front-end web pages. In the related technology, the performance monitoring of the front-end web pages is to collect web page operation data according to development requirements. The directly collected web page operation data is complex and highly professional. It requires professional developers to analyze the current performance status of the front-end web pages, which makes the front-end web page performance monitoring complicated. Therefore, how to make the performance monitoring of the front-end web pages more intuitive has become a technical problem that needs to be solved urgently. Summary of the invention

[0003] The main purpose of the embodiments of the present application is to propose a performance monitoring method and apparatus, device and storage medium based on a front-end web page, aiming to make the performance monitoring of the front-end web page simpler and more intuitive.

[0004] To achieve the above-mentioned purpose, a first aspect of an embodiment of the present application proposes a performance monitoring method based on a front-end web page, the method comprising:

[0005] Obtaining web page monitoring configuration information of the target web page;

[0006] Acquire webpage monitoring data of the target webpage according to the webpage monitoring configuration information; wherein the webpage monitoring data includes: page operation parameters and interface operation parameters, and the page operation parameters include: webpage loading time information and page access times;

[0007] Performing page performance evaluation processing on the target web page according to the web page loading time information and the page access times to obtain target page performance evaluation data;

[0008] Performing interface performance evaluation on the target webpage according to the interface operation parameters to obtain interface performance evaluation data;

[0009] The target web page is divided into performance levels according to the target page performance evaluation data and the interface performance evaluation data to obtain web page performance level information.

[0010] In some embodiments, performing page performance evaluation processing on the target web page according to the web page loading time information and the page access times to obtain target page performance evaluation data includes:

[0011] Performing page performance evaluation processing on the target web page according to the loading time information of each web page to obtain single page performance evaluation data;

[0012] The single page performance evaluation data are summed up according to a preset weight ratio to obtain total page performance evaluation data;

[0013] The ratio between the total page performance evaluation data and the page access times is obtained to obtain the target page performance evaluation data.

[0014] In some embodiments, the interface operation parameters include: number of interface accesses, average response time information, and watermark response time information; performing interface performance evaluation on the target webpage according to the interface operation parameters to obtain interface performance evaluation data includes:

[0015] Calculating the access frequency of the target webpage according to the number of interface accesses to obtain the interface access frequency;

[0016] Calculate the response frequency of the target webpage according to the average response time information and the watermark response time information to obtain an interface response frequency;

[0017] An interface performance evaluation is performed on the target webpage according to the interface access frequency and the interface response frequency to obtain the interface performance evaluation data.

[0018] In some embodiments, after classifying the target web page performance level according to the target page performance evaluation data and the interface performance evaluation data to obtain web page performance level information, the method further includes:

[0019] Filtering abnormal page data from the web page monitoring data according to the web page performance level information;

[0020] Acquire the abnormal log parameters of the abnormal page data; wherein the abnormal log parameters include: abnormal page information, abnormal number of times and abnormal reporting time information;

[0021] Performing link conversion on the abnormal page data to obtain an abnormal page link;

[0022] The abnormal page link, the abnormal page information, the abnormal number of times and the abnormal reporting time information are spliced ​​to obtain an abnormal page item;

[0023] The abnormal page item is visualized to obtain an abnormal page view.

[0024] In some embodiments, after visualizing the abnormal page item to obtain the abnormal page view, the method further includes:

[0025] In response to a click on the abnormal page link on the page abnormality view, the abnormal page data and the abnormal log parameter are acquired; wherein the abnormal page data includes: page abnormality category, abnormal location information and page user information;

[0026] The page exception category, the exception location information, the page user information, the exception page information, and the exception reporting time information are visualized to obtain a page exception detail view.

[0027] In some embodiments, after visualizing the page exception category, the exception location information, the page user information, the exception page information, and the exception reporting time information to obtain a page exception detail view, the method further includes:

[0028] Performing category identification on the abnormal page data to obtain an abnormal identification category;

[0029] Filtering selected exception reporting method information from preset candidate exception reporting method information according to the exception identification category;

[0030] The page exception detail view is reported as an exception according to the selected exception reporting method information.

[0031] In some embodiments, after performing an exception reporting on the page exception detail view according to the selected exception reporting method information, the method further includes:

[0032] Receiving an exception repair request based on feedback from the page exception detail view;

[0033] Performing content recognition on the page exception detail view according to the exception repair request to obtain page exception detail information;

[0034] Generate a repair solution using a preset exception repair solution generation model and the page exception details information to obtain a page exception repair solution;

[0035] The target web page is repaired according to the page abnormality repair solution.

[0036] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application proposes a performance monitoring device based on a front-end web page, the device comprising:

[0037] The device comprises:

[0038] An information acquisition module, used to acquire webpage monitoring configuration information of a target webpage;

[0039] A data acquisition module, used to acquire webpage monitoring data of the target webpage according to the webpage monitoring configuration information; wherein the webpage monitoring data includes: page operation parameters and interface operation parameters, and the page operation parameters include: webpage loading time information and page access times;

[0040] A page performance evaluation module is used to perform page performance evaluation processing on the target web page according to the web page loading time information and the page access times to obtain target page performance evaluation data;

[0041] An interface performance evaluation module, used to perform interface performance evaluation on the target webpage according to the interface operation parameters to obtain interface performance evaluation data;

[0042] The performance level classification module is used to classify the performance level of the target web page according to the target page performance evaluation data and the interface performance evaluation data to obtain web page performance level information.

[0043] To achieve the above objectives, a third aspect of an embodiment of the present application proposes an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the method described in the first aspect is implemented.

[0044] To achieve the above-mentioned purpose, the fourth aspect of an embodiment of the present application proposes a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in the first aspect is implemented.

[0045] The performance monitoring method, device, equipment and storage medium based on the front-end web page proposed in the present application obtain the page operation parameters and interface operation parameters of the target web page according to the web page monitoring configuration information, and the page operation data includes the web page loading time information and the page access times. The page performance of the target web page is evaluated in combination with the web page loading time information and the page access times evaluation, and then the interface performance of the target web page is evaluated according to the interface operation parameters. Finally, the performance level of the target web page is divided in combination with the data of the page performance evaluation and the interface performance evaluation, so that the performance evaluation of the target web page is simpler, and the professional requirements and complexity of the web page performance evaluation are reduced. The performance of the target web page can also be more intuitively represented through the web page performance level information, making the web page performance monitoring more intuitive. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1is a flow chart of a performance monitoring method based on a front-end web page provided in an embodiment of the present application;

[0047] Figure 2 It is a schematic diagram of web page monitoring data in the performance monitoring method based on the front-end web page provided in an embodiment of the present application;

[0048] Figure 3 yes Figure 1 Flow chart of step S102 in FIG.

[0049] Figure 4 It is a schematic diagram of target page performance evaluation data in the performance monitoring method based on the front-end web page provided in an embodiment of the present application;

[0050] Figure 5 yes Figure 1 Flow chart of step S104 in FIG.

[0051] Figure 6 is a flow chart of a performance monitoring method based on a front-end web page provided by another embodiment of the present application;

[0052] Figure 7 It is a schematic diagram of an abnormal page view in a performance monitoring method based on a front-end web page provided in an embodiment of the present application;

[0053] Figure 8 is a flow chart of a performance monitoring method based on a front-end web page provided by another embodiment of the present application;

[0054] Fig. 9 It is a schematic diagram of a page exception detail view in a performance monitoring method based on a front-end web page provided in an embodiment of the present application;

[0055] Fig.10 is a flow chart of a performance monitoring method based on a front-end web page provided by another embodiment of the present application;

[0056] Fig.11 is a flow chart of a performance monitoring method based on a front-end web page provided by another embodiment of the present application;

[0057] Fig.12 It is a structural diagram of a performance monitoring device based on a front-end web page provided in an embodiment of the present application;

[0058] Fig.13 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0060] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0061] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0062] First, some nouns involved in this application are analyzed:

[0063] Artificial intelligence (AI) is a new technical science that studies and develops theories, methods, technologies and application systems for simulating, extending and expanding human intelligence. AI is a branch of computer science that attempts to understand the essence of intelligence and produce a new type of intelligent machine that can respond in a similar way to human intelligence. Research in this field includes robotics, speech recognition, image recognition, natural language processing and expert systems. AI can simulate the information process of human consciousness and thinking. AI is also a theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0064] Front-end web page: refers to the web page interface that users see in the browser, which is usually composed of three main technologies: HTML, CSS and JavaScript.

[0065] Node.js: is an open source, cross-platform JavaScript runtime environment that allows developers to run JavaScript code on the server side. Node.js uses the Chrome V8 JavaScript engine and provides an efficient and lightweight way to build scalable network applications.

[0066] Script: A computer program that usually consists of a series of instructions that can be executed automatically. Scripts can be used to automate a variety of tasks, from simple file operations to complex system management tasks.

[0067] Watermark: A special event marker used in Flink stream processing to indicate that all events with timestamps less than or equal to this marker have been processed.

[0068] First useful painting time (FMP): is an important indicator for measuring web page loading speed and user experience. The first useful painting time indicates the time when the main content of the page appears on the screen, which is the main indicator of the user's perceived loading experience.

[0069] Time to Interactive (TTI): is an important indicator for measuring web page performance, indicating the time from when the page starts loading to when the page is fully interactive. TTI takes into account the time when the page becomes responsive enough to user input after visually presenting the main content.

[0070] As financial services become more and more diverse, the complexity of front-end web pages that provide financial services is also increasing, with more and more interactions, and the performance problems and errors of front-end web pages are gradually becoming prominent. In order to adapt to the richness of financial services and service effects, it is necessary to monitor the performance of front-end web pages, optimize the front-end web pages according to the performance monitoring results, and make the front-end web pages run more stably.

[0071] In the related art, the performance monitoring of front-end web pages only focuses on development requirements, and directly collects web page monitoring data according to development requirements. The directly collected web page monitoring data is complex and difficult to understand. Professional developers are required to analyze the performance of the front-end web pages through the collected web page monitoring data, which leads to the complexity of the performance of the front-end web pages. Therefore, how to make the performance monitoring of the front-end web pages easier has become an urgent problem to be solved.

[0072] Based on this, the embodiment of the present application provides a performance monitoring method and device, equipment and storage medium based on a front-end web page, which is intended to automatically collect web page monitoring data of a target web page according to web page monitoring configuration information, and the web page monitoring data includes page operation parameters and interface operation parameters, and the page operation parameters include web page loading time information and page access times, so as to evaluate the page performance of the target web page according to the web page loading time information and the page access times to obtain target page performance evaluation data, and then evaluate the interface performance of the target web page according to the interface operation parameters to obtain interface performance evaluation data, and finally determine the web page performance level information of the target web page based on the target page performance evaluation data and the interface performance evaluation data. Therefore, through automated data collection and performance evaluation, and the performance evaluation of the target web page is a joint evaluation from two aspects of the page and the interface, not only is the performance monitoring of the target web page easier, but also accurate performance monitoring is achieved.

[0073] The performance monitoring method, device, equipment and storage medium based on the front-end web page provided in the embodiments of the present application are specifically illustrated through the following embodiments. First, the performance monitoring method based on the front-end web page in the embodiments of the present application is described.

[0074] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0075] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0076] The performance monitoring method based on the front-end web page provided in the embodiment of the present application relates to the field of artificial intelligence technology. The performance monitoring method based on the front-end web page provided in the embodiment of the present application can be applied to the terminal, can also be applied to the server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the server side can be configured as an independent physical server, or it can be configured as a server cluster or a distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements a performance monitoring method based on the front-end web page, etc., but is not limited to the above forms.

[0077] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0078] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0079] Figure 1 is an optional flow chart of a performance monitoring method based on a front-end web page provided in an embodiment of the present application. Figure 1 The method may include but is not limited to steps S101 to S105.

[0080] Step S101, obtaining webpage monitoring configuration information of a target webpage;

[0081] Step S102, obtaining webpage monitoring data of the target webpage according to the webpage monitoring configuration information; wherein the webpage monitoring data includes: page operation parameters and interface operation parameters, and the page operation parameters include: webpage loading time information and page access times;

[0082] Step S103, performing page performance evaluation processing on the target web page according to the web page loading time information and the page access times, to obtain target page performance evaluation data;

[0083] Step S104, performing interface performance evaluation on the target webpage according to the interface operation parameters to obtain interface performance evaluation data;

[0084] Step S105 , classifying the target web page into performance levels according to the target page performance evaluation data and the interface performance evaluation data, and obtaining web page performance level information.

[0085] Steps S101 to S105 shown in the embodiment of the present application are to obtain web page monitoring data by monitoring the target web page according to the web page monitoring configuration information; wherein the web page monitoring data includes: page operation parameters and interface operation parameters, the page operation parameters include web page loading time information and page access times, the page performance of the target web page is evaluated according to the web page loading time information and the page access times, and the interface performance of the target web page is evaluated according to the interface operation parameters, and the performance level of the target web page is determined in combination with the evaluation data of the page performance and the interface performance. Therefore, by automatically collecting the page operation parameters and the interface operation parameters of the target web page, the performance of the page and the interface of the target web page is automatically evaluated, and the performance level of the target web page is divided in combination with the evaluation data of the two aspects of the page and the interface, which not only simplifies the web page performance monitoring and reduces the professional requirements of web page monitoring, but also allows the performance of the target web page to be more intuitively grasped, so that the operation and maintenance personnel can more quickly optimize the performance of the target web page and improve the performance of the target web page.

[0086] In step S101 of some embodiments, the target webpage is a front-end webpage that needs to be performance monitored, and the webpage monitoring configuration information is pre-configured, which is configuration information that indicates which aspect of the target webpage needs to be monitored. The monitoring items, monitoring methods, and monitoring data reporting methods of the target webpage can be determined through the webpage monitoring configuration information. It should be noted that the performance monitoring method of the target webpage is applied to a visualization platform to display the operation status of the target webpage through the visualization platform, and the monitoring configuration is performed on the visualization platform to generate the webpage monitoring configuration information.

[0087] For example, if the embodiment of the present application is applied to the insurance field, the target webpage is an insurance product page, the visualization platform connects to the insurance product page, and monitors the operation of the insurance product page. In order to realize the performance monitoring of the insurance product page, the page link of the insurance product page is input in advance on the visualization platform, and the insurance product page is monitored and configured to obtain the webpage monitoring configuration information, and the webpage monitoring configuration information is used to monitor the operation performance of the insurance product page, mainly realizing the monitoring of operation data, page errors, page operation logs, etc.

[0088] In step S102 of some embodiments, the target web page is monitored in a targeted manner according to the web page monitoring configuration information. Specifically, the preset monitoring script is configured according to the web page monitoring configuration information to obtain the target monitoring script, and the target monitoring script is placed in the entry file of the target web page to monitor the target web page through the target monitoring script. It should be noted that when the target web page is accessed, the target monitoring script starts to run, and the target monitoring script is written with methods for obtaining performance data, error information, etc., so after the target monitoring script runs, it will monitor the target web page according to the pre-configured monitoring method to obtain web page monitoring data.

[0089] It should be noted that after the web page monitoring data is collected, it is uploaded to the visualization platform and can be directly displayed on the visualization platform. Specifically, the web page monitoring data is displayed on the visualization platform, and the web page monitoring data includes page operation parameters, interface operation parameters, routing modes, etc. Among them, the interface operation parameters include: the number of interface accesses, the average response time information, and the watermark response time information (referred to as the interface watermark); the page operation parameters include: the web page loading time information (referred to as the TTI watermark) and the number of page accesses; in addition, the interface operation parameters also include the first effective rendering time information (referred to as the FMP watermark). It should be further noted that the specific composition of the web page monitoring data can be set according to the configuration, and this embodiment does not impose specific restrictions on the web page monitoring data. For example, if Figure 2 As shown, Figure 2 Displays web monitoring data of multiple front-end web pages for the visualization platform, through Figure 2 The identification number, webpage name, development team and webpage monitoring data of the monitored front-end webpage can be known, and the webpage monitoring data includes the interface waterline, TTI waterline, etc., so the performance monitoring status of each front-end webpage can be clearly known.

[0090] In some embodiments, in order to improve the security of webpage monitoring data, identity authentication is set on the visualization platform, by obtaining the access identity information of the access terminal, and determining whether the access terminal is an authorized terminal according to the access identity information. If it is an authorized terminal, the webpage monitoring data within the authorized scope can be searched.

[0091] See also Figure 3 In some embodiments, step S102 may include but is not limited to steps S301 to S303:

[0092] Step S301, performing page performance evaluation processing on the target web page according to the loading time information of each web page to obtain single page performance evaluation data;

[0093] Step S302, summing up the single page performance evaluation data according to a preset weight ratio to obtain total page performance evaluation data;

[0094] Step S303, obtaining the ratio between the total page performance evaluation data and the number of page accesses, and obtaining the target page performance evaluation data.

[0095] In step S301 of some embodiments, the webpage loading time information is also called the first interactive time, which represents the time from the target webpage loading to the normal access time of the access terminal, and the page access times are the times the access terminal accesses the target page, and the webpage loading time information of each access to the target page is different. Therefore, in order to more accurately evaluate the page performance of the target webpage, the single page performance evaluation of the target webpage is performed according to the webpage loading time information generated by each access, and the single page performance evaluation data is obtained. It should be noted that the single page performance evaluation data table shows the performance of the target page each time it is accessed.

[0096] Specifically, in this embodiment, the single-page performance evaluation rules are set in advance, and the single-page performance evaluation rules record the basic loading time for starting to deduct points, and each loading time corresponds to a deduction score, so the loading deduction score is determined according to the web page loading time information, and then the target deduction score is determined according to the ratio between the current page visit number of the target page and the visit number of the target page with the most visits on the day and the loading deduction score. If the percentage system is used as the standard, 100 minus the target deduction score will get the single-page performance evaluation data. For example, the basic loading time for starting to deduct points is 1000ms, and the corresponding loading deduction score score is 1000ms. z = 0, and increase the loading time by 2000ms, the corresponding deduction score is increased by 40 points, and the highest loading deduction score is 100. The target deduction score is score m =score z (Tt / Tm), Tt is the number of page visits to the target web page during the period, and Tm is the number of page visits to the front-end web page with the most visits on that day. Finally, the single page performance evaluation data is determined as score d =100-score m .

[0097] In step S302 of some embodiments, the performance of the target web page accessed by each access terminal can be determined by the single page performance evaluation data. However, in order to more intuitively characterize the overall performance of the target web page, it is necessary to sum the single page performance evaluation data to obtain the total page performance evaluation data. It should be noted that when calculating the total page performance evaluation data, it is necessary to sum according to the weight ratio, because the weight ratio corresponding to each access is different, and the importance of the single page performance evaluation data obtained by each access is different. Specifically, the weight ratio is determined by the access period information of the single page performance evaluation data. If the access period information belongs to the busy period, the higher the weight ratio is. On the contrary, if the access period information belongs to the idle period, the lower the weight ratio is, the importance of the single page performance evaluation data characterizing the idle period for the overall performance evaluation of the target web page is lower. Therefore, by weighted summing the single page performance evaluation data to obtain the total page performance evaluation data, the total page performance evaluation data can more accurately characterize the performance of the target web page.

[0098] In step S303 of some embodiments, in order to more intuitively and accurately characterize the performance of the target web page, the total page performance evaluation data is divided by the total number of page visits to obtain the target page performance evaluation data. Figure 4 As shown, the visualization platform displays the target page performance evaluation data of web page A, and the target page performance evaluation data is represented by scores. When displaying the target page performance evaluation data, the interface watermark, TTI watermark and FMP watermark of the target web page are displayed at the same time. Through the content displayed by the visualization platform, the current performance status of the target web page can be intuitively grasped, providing reference information for the performance optimization of the target web page.

[0099] In step S301 to step S303 shown in this embodiment, the performance of the target web page when it is accessed once is evaluated according to the web page loading time information to obtain single page performance evaluation data, and then the single page performance evaluation data of the entire access cycle of the target web page is weighted and summed to obtain total page performance evaluation data that can characterize the overall performance of the target web page. Finally, the total page performance evaluation data is divided by the number of page accesses to obtain target page performance evaluation data that more accurately characterizes the performance of the target web page, thereby improving the accuracy of the target web page performance evaluation.

[0100] As disclosed above, the interface operation parameters include: the number of interface accesses, average response time information and watermark response time information. The number of interface accesses is the number of times the interface of the target webpage is accessed, the average response time information represents the average time from the beginning of the interface access to the feedback of the access result, and the watermark response time information represents the time from the beginning of the interface access to the feedback of the access result. It should be noted that in order to more intuitively display the changes in the interface operation parameters, a line chart will be used on the visualization platform to display the changes in the interface operation parameters, so as to realize real-time monitoring of the interface performance of the target webpage.

[0101] See also Figure 5 In some embodiments, step S104 may include but is not limited to steps S501 to S503:

[0102] Step S501, calculating the access frequency of the target web page according to the number of interface accesses to obtain the interface access frequency;

[0103] Step S502, calculating the response frequency of the target web page according to the average response time information and the watermark response time information to obtain the interface response frequency;

[0104] Step S503: performing interface performance evaluation on the target webpage according to the interface access frequency and the interface response frequency to obtain interface performance evaluation data.

[0105] In step S501 of some embodiments, the interface access frequency reflects the access situation of the target web page, and the higher the interface access frequency, the more frequent the access to the target web page. Conversely, the lower the interface access frequency, the more scarce the access to the target web page. It can also reflect the performance of the target web page. It should be noted that the number of times of calculating the number of interface accesses is obtained, and the number of interface accesses is divided by the number of times calculating the time to obtain the number of accesses per unit time to obtain the interface access frequency.

[0106] In step S502 of some embodiments, the average response frequency is determined according to the average response time information, and the waterline response frequency is determined according to the waterline response time information. Then, the interface response frequency is obtained by averaging the average response frequency and the waterline response frequency.

[0107] In step S503 of some embodiments, an interface evaluation mapping table between the interface access frequency, the interface response frequency and the performance evaluation data is set in advance, and the corresponding performance evaluation data is found in the interface evaluation mapping table according to the interface access frequency and the interface response frequency as the interface performance evaluation data.

[0108] In steps S501 to S503 shown in this embodiment, the interface access frequency is determined according to the number of interface accesses, the interface response frequency is determined according to the average response time information and the watermark response time information, and the interface performance evaluation data is determined according to the interface access frequency and the interface response frequency. This makes the interface performance evaluation of the target web page easy to operate and can be implemented without professional developers, thereby reducing the difficulty of interface performance evaluation.

[0109] In step S105 of some embodiments, the target web page is divided into performance levels according to the target page performance evaluation data and the interface performance evaluation data. The target page performance evaluation data and the interface performance evaluation data can be spliced ​​to obtain the target performance evaluation data, and the target web page is divided into performance levels according to the target performance evaluation data to obtain web page performance level information. Among them, the splicing method of the target page performance evaluation data and the interface performance evaluation data can be a weighted sum method, and a sum value, an average value, etc. can also be calculated. This embodiment does not make specific restrictions on the splicing method. In addition, the division of web page performance level information can also be based on the target page performance evaluation data. Find out the page performance level information in the preset level division table, and then find out the interface performance level information in the preset level division table according to the interface performance evaluation data, and determine the web page performance level information according to the page performance level information and the interface performance level information. Therefore, there can be multiple ways to determine the web page performance level information, and this embodiment does not make specific restrictions.

[0110] See also Figure 6 In some embodiments, after step S105, the performance monitoring method based on the front-end web page may include but is not limited to steps S601 to S605:

[0111] Step S601, filtering out abnormal page data from the web page monitoring data according to the web page performance level information;

[0112] Step S602, obtaining abnormal log parameters of abnormal page data; wherein the abnormal log parameters include: abnormal page information, abnormal number of times and abnormal reporting time information;

[0113] Step S603, link conversion is performed on the abnormal page data to obtain an abnormal page link;

[0114] Step S604, the abnormal page link, abnormal page information, abnormal number of times and abnormal reporting time information are spliced ​​to obtain an abnormal page item;

[0115] Step S605: Visualize the abnormal page item to obtain an abnormal page view.

[0116] In step S601 of some embodiments, an abnormality assessment is first performed on the target web page based on the web page performance level information to obtain abnormality assessment information. If the abnormality assessment information indicates that there is an abnormality in the target web page, abnormal page data is extracted from the web page monitoring data. The abnormal page data is page operation data automatically collected by the target monitoring script when an abnormality occurs when the target web page is accessed. The abnormal page data can be used to analyze the abnormal cause and abnormal situation of the target web page so as to repair the target web page in a timely manner.

[0117] In step S602 of some embodiments, as disclosed above, the abnormal page data is the page operation data when the target web page is accessed abnormally, so the abnormal log parameters of the abnormal page data are obtained, and the abnormal log parameters are the log parameters corresponding to the abnormal situation when the target web page is accessed. Among them, the abnormal log parameters include: abnormal page information, abnormal number of times and abnormal reporting time information, the abnormal page information is the abnormal description when the target web page is abnormal, the abnormal number of times represents the number of times the target web page is abnormal, and the abnormal reporting time information is the time information when the target web page is abnormal and reported. Therefore, by obtaining the abnormal page information, the abnormal number of times and the abnormal reporting time information, the abnormal cause of the target web page can be analyzed in more detail, and the repair of the target web page can be completed more accurately.

[0118] In step S603 of some embodiments, the abnormal page data is converted into an abnormal page link, and clicking the abnormal page link can jump to the page corresponding to the abnormal page data, so as to provide professional developers with the opportunity to further analyze the cause of the abnormality.

[0119] In some embodiments, in order to more intuitively represent the abnormal situation of the target web page and reduce the difficulty of abnormal analysis, the abnormal page link, abnormal page information, abnormal number and abnormal reporting time information are spliced ​​into abnormal page items, and each abnormal page item represents the abnormal situation of a target web page. Then, each abnormal page item is visualized to obtain an abnormal page view. Specifically, Figure 7 As shown, Figure 7 The exception page view is displayed, through which the exception page information, number of exceptions and exception reporting time information of each target web page can be clearly known. The exception page view also provides exception operation options for users to choose from to determine whether to handle the exceptions that occur on the target web page.

[0120] In steps S601 to S605 shown in the present embodiment, the abnormal page data of the target web page is automatically obtained, and the abnormal page information, the number of abnormalities and the abnormal reporting time information are obtained according to the abnormal page data, and then the abnormal page data is converted into an abnormal page link, and the abnormal page link, the abnormal page information, the number of abnormalities and the abnormal reporting time information are visualized, so that the user can understand the abnormal situation of the target web page more intuitively, and can repair the abnormality of the target web page in time, thereby improving the stability of the target web page.

[0121] See also Figure 8 In some embodiments, after step S605, the performance monitoring method based on the front-end web page may also include but is not limited to steps S801 to S802:

[0122] Step S801, in response to a click on an abnormal page link on a page abnormality view, acquiring abnormal page data and abnormal log parameters; wherein the abnormal page data includes: page abnormality category, abnormal location information and page user information;

[0123] Step S802 , visualize the page exception category, exception location information, page user information, exception page information, and exception reporting time information to obtain a page exception detail view.

[0124] In step S801 of some embodiments, when the user clicks on the abnormal page link on the page abnormality view, in response to the click on the abnormal page link, the abnormal page data and abnormal log parameters are directly extracted. The abnormal page data includes: page abnormality category, abnormal location information and page user information, the page abnormality category represents the abnormality category of the target web page, the abnormal location information represents the location where the abnormality occurs in the target web page, and the abnormal user information is the identity information of the access terminal when the abnormality occurs when accessing the target web page.

[0125] In step S802 of some embodiments, the page anomaly category, anomaly location information, page user information, anomaly page information, and anomaly reporting time information are combined, and then the combined information is visualized to obtain a page anomaly detail view. Fig. 9 As shown, Fig. 9 The page exception details view is displayed. Through the page exception details view, you can clearly see the page exception category, exception location information, page user information, exception page information and exception reporting time information. The exception location information includes exception rows and exception columns. The exception location of the target web page is determined through the exception rows and exception columns.

[0126] In steps S801 to S802 shown in the embodiment of the present application, when the user clicks on the abnormal page link, the page abnormality details view is automatically displayed, and the page abnormality category, abnormal location information, abnormal user information, abnormal page information and abnormal reporting time information are displayed through the page abnormality details view, so that the user can understand the abnormal problems existing in the target web page more intuitively and in detail, and can accurately repair the target web page.

[0127] See also Fig.10 In some embodiments, after step S802, the performance monitoring method based on the front-end web page further includes but is not limited to steps S1001 to S1003:

[0128] Step S1001, classify the abnormal page data to obtain the abnormal classification;

[0129] Step S1002, selecting the selected abnormality reporting method information from the preset candidate abnormality reporting method information according to the abnormality identification category;

[0130] Step S1003, reporting the exception of the page exception details view according to the selected exception reporting method information.

[0131] In steps S1001 to S1002 of some embodiments, different exception identification categories correspond to different exception reporting methods, so the category of the abnormal page data is first identified to obtain the abnormal identification category, and then the candidate abnormal reporting method information corresponding to the abnormal identification category is used as the selected abnormal reporting method information. It should be noted that the candidate abnormal reporting method information can be scheduled reporting method information, manual reporting method information, trigger reporting method information, etc. This embodiment does not specifically limit the candidate abnormal reporting method information. Specifically, a reporting method mapping table that characterizes the mapping relationship between the abnormal identification category and the candidate abnormal reporting method information is set in advance, and the selected abnormal reporting method information corresponding to the abnormal identification category can be determined through the reporting method mapping table.

[0132] In step S1003 of some embodiments, the page exception detail view is reported according to the selected exception reporting method information, so that the reporting of the page exception detail view is more personalized. For example, if the selected exception reporting method information is the scheduled reporting method information, the page exception detail view is pushed regularly according to the set time information in the scheduled reporting method information, so that the operation and maintenance personnel of the target webpage can perform abnormal maintenance on the target webpage in time, so that the operation of the target webpage is more stable, and the user's experience of using the target webpage is improved.

[0133] In steps S1001 to S1003 shown in this embodiment, the selected exception reporting method information of the page exception details view is determined according to the exception identification category of the abnormal page data to achieve personalized reporting of the page exception details view, that is, the page exception details view can be reported according to the user's reporting requirements.

[0134] See also Fig.11 In some embodiments, after step S1003, the performance monitoring method based on the front-end web page may also include but is not limited to steps S1101 to S1104:

[0135] Step S1101, receiving an exception repair request fed back from a page exception detail view;

[0136] Step S1102, performing content recognition on the page exception detail view according to the exception repair request to obtain page exception detail information;

[0137] Step S1103, generating a repair solution through a preset abnormality repair solution generation model and page abnormality details information to obtain a page abnormality repair solution;

[0138] Step S1104: repair the target web page according to the page abnormality repair solution.

[0139] In step S1101 of some embodiments, the exception repair request is a repair request based on the page exception detail view feedback, and is used to repair the exception of the target web page. Specifically, the exception repair request is generated by selecting the exception handling button in the exception operation option on the page exception detail view, so as to indicate the exception repair of the target web page through the exception repair request.

[0140] In step S1102 of some embodiments, content identification is performed on the page exception detail view according to the exception repair request to obtain page exception detail information, and the exception page detail information includes: page exception category, exception location information, exception user information, exception page information and exception reporting time information. The exception situation and exception location of the target web page can be determined through the exception page detail information, so that the abnormal page of the target web page can be quickly located.

[0141] In step S1103 of some embodiments, in order to achieve efficiency and accuracy in repairing the target web page exception, this embodiment uses an exception repair solution generation model and page exception details information to generate a page exception repair solution. It should be noted that the exception repair solution generation model is obtained based on a large amount of training page exception information and training repair solutions, and the exception repair solution generation model can automatically and accurately generate a repair solution corresponding to each page exception information, and provide repair steps for the front-end web page.

[0142] In step S1104 of some embodiments, the page exception repair scheme is composed of multiple page exception repair operations and repair logic, and the page exception repair operations are executed one by one on the target web page according to the repair logic to achieve automatic repair of the target web page.

[0143] In steps S1101 to S1104 shown in this embodiment, a page exception repair plan for the target web page is automatically generated by adopting an exception repair plan generation model, and the target web page is automatically repaired according to the page exception repair plan, thereby realizing automated repair of the target web page, reducing the manpower for manual repair, and improving the efficiency of abnormality repair of the target web page.

[0144] The target webpage of the embodiment of the present application is a front-end webpage based on any one of Node.js, Nest, and React, and the target webpage is subjected to webpage performance analysis, abnormal monitoring, and abnormal repair by setting a visualization platform. When it is necessary to perform performance monitoring on the target webpage, the webpage monitoring configuration information configured on the visualization platform for the target webpage is first obtained, so as to determine the target webpage to be monitored and the monitoring items and monitoring methods of the target webpage according to the webpage monitoring configuration information. Then, the preset monitoring script is configured according to the webpage monitoring configuration information to obtain the target monitoring script, and the target monitoring script is placed in the entry file of the target webpage, so as to obtain webpage monitoring data by monitoring the target webpage when the target webpage is accessed through the target monitoring script. Among them, the webpage monitoring data includes: page operation parameters, interface operation parameters, and routing mode, the interface operation parameters include: interface access times, average response time information, and waterline response time information (referred to as interface waterline), and the page operation parameters include: webpage loading time information (referred to as TTI waterline) and page access times. First, a single page performance evaluation is performed on the target web page according to the web page loading time information to obtain the single page performance evaluation data, and then the single page performance evaluation data is weighted and summed according to the weight ratio to obtain the total page performance evaluation data, and finally the ratio between the total page performance evaluation data and the page access times is used as the target page performance evaluation data. At the same time, the number of times of interface access is obtained, and the interface access frequency is determined according to the ratio between the number of interface accesses and the number of times of calculation time, and then the average response frequency is determined according to the average response time information, and the waterline response frequency is determined according to the waterline response time information, and then the interface performance evaluation data of the target web page is found in the interface evaluation mapping table according to the average response frequency and the waterline response frequency. Then, the target page performance evaluation data and the interface performance evaluation data are spliced ​​into the target performance evaluation data, and the target web page is divided into performance levels according to the target performance evaluation data to obtain the web page performance level information. Therefore, the performance evaluation of the target web page is realized by combining the evaluation data of the page and the interface, reducing the professionalism and complexity of the performance monitoring of the target web page, making the performance monitoring of the target web page easier.

[0145] After completing the performance evaluation of the target web page, it is necessary to perform abnormal monitoring on the target web page. By performing abnormal evaluation on the target web page according to the web page performance monitoring level information to obtain abnormal evaluation information, and when the web page performance monitoring level information is lower than the preset performance level information, it is determined that the abnormal evaluation information indicates that there is an abnormality in the target web page, and it is necessary to extract abnormal page data from the web page monitoring data, that is, abnormal page operation data. By obtaining the abnormal page information, abnormal number of times and abnormal reporting time information of the page operation data, the abnormal page data is converted into an abnormal page link, and then the abnormal page link, abnormal page information, abnormal number of times and abnormal reporting time information are combined and visualized to generate an abnormal page view, through which the abnormal situation of the target web page can be clearly known.

[0146] When you need to view the exception information of the target web page in more detail, you can click the exception page link on the exception page view to automatically visualize the page exception category, exception location information, page user information, exception page information, and exception reporting time information into a page exception details view, and display the detailed exception situation of the target web page through the page exception details view.

[0147] After the exception details of the front-end web page are displayed, if the target web page needs to be automatically repaired, an exception repair request can be sent to the visualization platform. The visualization platform identifies the page exception details in the page exception details view according to the exception repair request, and generates a page exception repair plan through the exception repair plan generation model and the page exception details. Among them, the page exception repair plan consists of multiple page exception repair operations and repair logic. The page exception repair operations are executed one by one on the target web page according to the repair logic to achieve automatic repair of the target web page.

[0148] In summary, by setting up a visualization platform to automatically perform performance analysis, anomaly monitoring and anomaly repair on the target web page, not only the professional requirements for target web page performance monitoring are reduced, but also the stability of the target web page can be improved, and the user experience when using the front-end web page can be enhanced.

[0149] See also Fig.12 The embodiment of the present application also provides a performance monitoring device based on a front-end web page, which can implement the above-mentioned performance monitoring method based on a front-end web page, and the device includes:

[0150] The information acquisition module 1201 is used to acquire the webpage monitoring configuration information of the target webpage;

[0151] The data acquisition module 1202 is used to acquire the webpage monitoring data of the target webpage according to the webpage monitoring configuration information; wherein the webpage monitoring data includes: page operation parameters and interface operation parameters, and the page operation parameters include: webpage loading time information and page access times;

[0152] The page performance evaluation module 1203 is used to perform page performance evaluation processing on the target web page according to the web page loading time information and the page access times to obtain target page performance evaluation data;

[0153] The interface performance evaluation module 1204 is used to perform interface performance evaluation on the target web page according to the interface operation parameters to obtain interface performance evaluation data;

[0154] The performance level classification module 1205 is used to classify the performance level of the target web page according to the target page performance evaluation data and the interface performance evaluation data to obtain web page performance level information.

[0155] The specific implementation of the performance monitoring device based on the front-end web page is basically the same as the specific implementation of the performance monitoring method based on the front-end web page mentioned above, and will not be repeated here.

[0156] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned performance monitoring method based on the front-end web page when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a car computer, etc.

[0157] See also Fig.13 , Fig.13 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0158] The processor 1301 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0159] The memory 1302 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1302 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 1302, and the processor 1301 calls and executes the performance monitoring method based on the front-end web page of the embodiment of this application;

[0160] Input / output interface 1303, used to implement information input and output;

[0161] The communication interface 1304 is used to realize the communication interaction between the device and other devices. The communication can be realized through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0162] A bus 1305 that transmits information between the various components of the device (e.g., the processor 1301, the memory 1302, the input / output interface 1303, and the communication interface 1304);

[0163] The processor 1301 , the memory 1302 , the input / output interface 1303 and the communication interface 1304 are connected to each other in communication within the device via a bus 1305 .

[0164] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned performance monitoring method based on the front-end web page is implemented.

[0165] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0166] The front-end web page performance monitoring method, apparatus, device and storage medium provided in the embodiments of the present application collect page operation parameters and interface operation parameters of the target web page according to web page monitoring configuration information, and the page operation parameters include web page loading time information and page access times, evaluate the page performance of the target web page in combination with the web page loading time information and the page access times, and then evaluate the interface performance of the target web page according to the interface operation parameters, and finally complete the performance level division of the target web page in combination with the performance evaluation data of the page and the interface, so that the performance evaluation of the target web page is more intuitive and accurate, the professional requirements and complexity of the web page performance evaluation are reduced, and the web page performance monitoring is more intuitive.

[0167] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0168] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0169] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0170] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0171] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0172] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0173] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0174] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0175] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0176] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0177] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A performance monitoring method based on a front-end web page, characterized in that: The method comprises: Obtaining web page monitoring configuration information of the target web page; Acquire webpage monitoring data of the target webpage according to the webpage monitoring configuration information; wherein the webpage monitoring data includes: page operation parameters and interface operation parameters, and the page operation parameters include: webpage loading time information and page access times; Performing page performance evaluation processing on the target web page according to the web page loading time information and the page access times to obtain target page performance evaluation data; Performing interface performance evaluation on the target webpage according to the interface operation parameters to obtain interface performance evaluation data; The target web page is divided into performance levels according to the target page performance evaluation data and the interface performance evaluation data to obtain web page performance level information.

2. The method according to claim 1, characterized in that The performing page performance evaluation processing on the target webpage according to the webpage loading time information and the page access times to obtain target page performance evaluation data includes: Performing page performance evaluation processing on the target web page according to the loading time information of each web page to obtain single page performance evaluation data; The single page performance evaluation data are summed up according to a preset weight ratio to obtain total page performance evaluation data; The ratio between the total page performance evaluation data and the page access times is obtained to obtain the target page performance evaluation data.

3. The method according to claim 1, characterized in that The interface operation parameters include: the number of interface accesses, average response time information and watermark response time information; the interface performance evaluation of the target webpage is performed according to the interface operation parameters to obtain interface performance evaluation data, including: Calculating the access frequency of the target webpage according to the number of interface accesses to obtain the interface access frequency; Calculate the response frequency of the target webpage according to the average response time information and the watermark response time information to obtain an interface response frequency; An interface performance evaluation is performed on the target webpage according to the interface access frequency and the interface response frequency to obtain the interface performance evaluation data.

4. The method according to any one of claims 1 to 3, characterized in that: After the target web page is divided into performance levels according to the target page performance evaluation data and the interface performance evaluation data to obtain web page performance level information, the method further includes: Filtering abnormal page data from the web page monitoring data according to the web page performance level information; Acquire the abnormal log parameters of the abnormal page data; wherein the abnormal log parameters include: abnormal page information, abnormal number of times and abnormal reporting time information; Performing link conversion on the abnormal page data to obtain an abnormal page link; The abnormal page link, the abnormal page information, the abnormal number of times and the abnormal reporting time information are spliced ​​to obtain an abnormal page item; The abnormal page item is visualized to obtain an abnormal page view.

5. The method according to claim 4, characterized in that After visualizing the abnormal page item to obtain the abnormal page view, the method further includes: In response to a click on the abnormal page link on the page abnormality view, the abnormal page data and the abnormal log parameter are acquired; wherein the abnormal page data includes: page abnormality category, abnormal location information and page user information; The page exception category, the exception location information, the page user information, the exception page information, and the exception reporting time information are visualized to obtain a page exception detail view.

6. The method according to claim 5, characterized in that After visualizing the page exception category, the exception location information, the page user information, the exception page information, and the exception reporting time information to obtain a page exception detail view, the method further includes: Performing category identification on the abnormal page data to obtain an abnormal identification category; Filtering selected exception reporting method information from preset candidate exception reporting method information according to the exception identification category; The page exception detail view is reported as an exception according to the selected exception reporting method information.

7. The method according to claim 5, characterized in that After the page exception detail view is reported according to the selected exception reporting method information, the method further includes: Receiving an exception repair request based on feedback from the page exception detail view; Performing content recognition on the page exception detail view according to the exception repair request to obtain page exception detail information; Generate a repair solution using a preset exception repair solution generation model and the page exception details information to obtain a page exception repair solution; The target web page is repaired according to the page abnormality repair solution.

8. A performance monitoring device based on a front-end web page, characterized in that: The device comprises: An information acquisition module, used to acquire webpage monitoring configuration information of a target webpage; A data acquisition module, used to acquire webpage monitoring data of the target webpage according to the webpage monitoring configuration information; wherein the webpage monitoring data includes: page operation parameters and interface operation parameters, and the page operation parameters include: webpage loading time information and page access times; A page performance evaluation module is used to perform page performance evaluation processing on the target web page according to the web page loading time information and the page access times to obtain target page performance evaluation data; An interface performance evaluation module, used to perform interface performance evaluation on the target webpage according to the interface operation parameters to obtain interface performance evaluation data; The performance level classification module is used to classify the performance level of the target web page according to the target page performance evaluation data and the interface performance evaluation data to obtain web page performance level information.

9. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the front-end web page-based performance monitoring method described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the front-end web page-based performance monitoring method described in any one of claims 1 to 7 is implemented.

Images