CN117076232A - Page abnormality detection method, computing device and storage medium - Google Patents

Abstract

The application discloses a page abnormality detection method, a computing device and a storage medium, wherein the page abnormality detection method is executed in the computing device and comprises the following steps: responding to a page access request, and acquiring a network address type of an access page; determining the performance data acquisition frequency of the access page based on the network address type; judging whether to collect the performance data of the access page according to the performance data collection frequency; if yes, acquiring performance data during the loading of the access page by calling the page performance interface, and detecting whether the access page is abnormally loaded or not by utilizing the performance data. According to the method, different sampling frequencies are set for access pages with different network address types, so that the detected performance consumption can be reduced, and the unnecessary pressure of performance reporting on a server can be relieved.

Description

Page abnormality detection method, computing device and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method for detecting page abnormalities, a computing device, and a storage medium.

Background

With the development of mobile APP (Application) and front-end technology, H5 (HTML 5) pages are mixed in native APP, so that cross-platform (Android and iOS) development is realized, and the development is more and more popular in practical applications. In some APP, H5 replaces the native page completely, and becomes the most dominant business rendering mode, and WebView is used as a browser control of the mobile terminal, and is a carrier for rendering the H5 page.

The loading speed of H5 in APP is very important to user experience, and in order to improve user experience, performance data of each H5 page needs to be detected and counted. However, if performance is collected and reported on all WebView loaded pages, a large number of repeated reports are caused, resulting in serious equipment performance consumption and other problems.

Disclosure of Invention

The present application has been made in view of the above problems, and provides a page fault detection method, a computing device, and a storage medium that overcome or at least partially solve the above problems.

According to one aspect of the present application, there is provided a page fault detection method, executed in a computing device, the method comprising: responding to a page access request, and acquiring a network address type of an access page; determining the performance data acquisition frequency of the access page based on the network address type; judging whether to collect the performance data of the access page according to the performance data collection frequency; if yes, acquiring performance data during the loading of the access page by calling the page performance interface, and detecting whether the access page is abnormally loaded or not by utilizing the performance data.

Optionally, in the page abnormality detection method according to the present application, wherein the step of acquiring performance data during loading of the access page by retrieving the page performance interface and detecting whether the access page is abnormally loaded by using the performance data includes: during loading the access page in the page control, acquiring page element data of the access page, and detecting whether each page element data is loaded successfully or not; if yes, acquiring preset resource data of the access page, and detecting whether each preset resource data is loaded successfully; if yes, acquiring the display interface image data of the access page, and detecting whether the display interface image data is normal or not; if yes, determining that the access page is normally loaded.

Optionally, in the page abnormality detection method according to the present application, the method further includes: if the preset resource data loading failure, the preset resource data loading failure or the display interface image data abnormality is detected, determining that the access page has a first abnormality.

Optionally, in the page abnormality detection method according to the present application, wherein the step of acquiring performance data during loading of the access page by retrieving the page performance interface and detecting whether the access page is abnormally loaded by using the performance data includes: during loading an access page in a page control, acquiring first time data of the access page indicating first drawing page content and second time data of the access page indicating maximum drawing page content; detecting whether the first time data is not greater than a first time threshold; if yes, detecting whether the second time data is not greater than a second time threshold; if yes, determining that the access page is normally loaded.

Optionally, in the page abnormality detection method according to the present application, the method further includes: and if the first time data is detected to be larger than the first time threshold value or the second time data is detected to be larger than the second time threshold value, determining that the second abnormality exists in the access page.

Optionally, in the page exception detection method according to the present application, detecting whether each page element data is loaded successfully includes: counting the number of the acquired page element data; and when the number of the page element data is larger than the number threshold value, determining that the page element data is successfully loaded.

Optionally, in the page abnormality detection method according to the present application, detecting whether the display interface image data is normal includes: acquiring the pixel duty ratio of each color in the image data of the display interface; and when the duty ratio of each pixel is smaller than the duty ratio threshold value, determining that the image data of the display interface is normal.

Optionally, in the page anomaly detection method according to the present application, the determining the performance data acquisition frequency of the access page based on the network address type includes: generating a configuration file related to the page performance data acquisition frequency at least based on the network address type of each page; the performance data acquisition frequency of the access page is matched from the configuration file based on the network address type of the access page.

Optionally, in the page abnormality detection method according to the present application, the method further includes: and correlating and displaying the network address, the network address type, the subdomain name prefix, the primary directory, the equipment information of the computing equipment and the loading result of the access page.

Optionally, in the page anomaly detection method according to the present application, the page control is a WebView control, and the page performance interface is a performance API; and, the method further comprises: and in the WebView control configuration stage, a JS script is injected, and the JS script is associated with a performance API.

According to yet another aspect of the present application, there is provided a computing device comprising: at least one processor; and a memory storing program instructions, wherein the program instructions are configured to be adapted to be executed by the at least one processor, the program instructions comprising instructions for performing the above-described method.

According to yet another aspect of the present application, there is provided a readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform the above-described method.

According to the scheme of the application, different sampling frequencies are set for the access pages with different network address types, so that the detected performance consumption can be reduced, and the unnecessary pressure of performance reporting on a server can be relieved.

The foregoing description is only an overview of the present application, and is intended to be implemented in accordance with the teachings of the present application in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present application more readily apparent.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:

FIG. 1 shows a schematic diagram of a computing device 100 according to one embodiment of the application;

FIG. 2 illustrates a flow diagram of a page fault detection method 200 according to one embodiment of the application.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Before the H5 page is presented, network loading is needed through a WebView control, and once loading failure is caused by network abnormality and the like in the loading process, the WebView cannot normally present the content and becomes a white screen page, so that the user experience is seriously affected.

To solve the above problem, in the development of pages, a third party code is generally injected into a single page to collect performance indexes, and the collected performance indexes are analyzed to detect the loading condition of the page. However, this detection scheme suffers from the following drawbacks:

1. in separate H5 page development, the developer may use different development languages, such as, for example, react/Vue/Zepto/JavaScript, etc. The code for realizing the collection and reporting functions will be different for different technical languages, so that a developer is required to perform personalized configuration for different language or frames of the project.

Some of the indicators of webvisual present compatibility problems on iOS and do not fully reflect whether pages are white-screen or not and the reality of slow loading.

3. The accuracy of the white screen judgment is slightly thin by singly adopting the screen capturing detection, DOM detection or static resource detection, for example, the screen capturing detection is realized, in some cases, the loading image occupation is commonly agreed by H5 and Native, then only the screen capturing detection is used for judging the single pixel occupation ratio at the moment, and the white screen problem under the scene cannot be reported.

4. The detection means have certain performance cost, and can cause a large number of repeated reports.

The proposal of the application is provided for solving the problems in the prior art. One embodiment of the present application provides a page fault detection method that may be performed in a computing device. FIG. 1 illustrates a block diagram of a computing device 100 according to one embodiment of the application. As shown in FIG. 1, in a basic configuration 102, a computing device 100 typically includes a system memory 106 and one or more processors 104. The memory bus 108 may be used for communication between the processor 104 and the system memory 106.

Depending on the desired configuration, the processor 104 may be any type of processing including, but not limited to: a microprocessor (μp), a microcontroller (μc), a digital information processor (DSP), or any combination thereof. The processor 104 may include one or more levels of caches, such as a first level cache 110 and a second level cache 112, a processor core 114, and registers 116. The example processor core 114 may include an Arithmetic Logic Unit (ALU), a Floating Point Unit (FPU), a digital signal processing core (DSP core), or any combination thereof. The example memory controller 118 may be used with the processor 104, or in some implementations, the memory controller 118 may be an internal part of the processor 104.

Depending on the desired configuration, system memory 106 may be any type of memory including, but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. Physical memory in a computing device is often referred to as volatile memory, RAM, and data in disk needs to be loaded into physical memory in order to be read by processor 104. The system memory 106 may include an operating system 120, one or more applications 122, and program data 124. The application 122 is actually a plurality of program instructions for instructing the processor 104 to perform a corresponding operation. In some implementations, the application 122 may be arranged to execute instructions on an operating system by the one or more processors 104 using the program data 124 in some implementations. The operating system 120 may be, for example, linux, windows or the like, which includes program instructions for handling basic system services and performing hardware-dependent tasks. The application 122 includes program instructions for implementing various functions desired by the user, and the application 122 may be, for example, a browser, instant messaging software, a software development tool (e.g., integrated development environment IDE, compiler, etc.), or the like, but is not limited thereto. When an application 122 is installed into computing device 100, a driver module may be added to operating system 120.

When the computing device 100 starts up running, the processor 104 reads the program instructions of the operating system 120 from the memory 106 and executes them. Applications 122 run on top of operating system 120, utilizing interfaces provided by operating system 120 and underlying hardware to implement various user-desired functions. When a user launches the application 122, the application 122 is loaded into the memory 106, and the processor 104 reads and executes the program instructions of the application 122 from the memory 106.

Computing device 100 also includes storage device 132, storage device 132 including removable storage 136 and non-removable storage 138, both removable storage 136 and non-removable storage 138 being connected to storage interface bus 134.

Computing device 100 may also include an interface bus 140 that facilitates communication from various interface devices (e.g., output devices 142, peripheral interfaces 144, and communication devices 146) to basic configuration 102 via bus/interface controller 130. The example output device 142 includes a graphics processing unit 148 and an audio processing unit 150. They may be configured to facilitate communication with various external devices such as a display or speakers via one or more a/V ports 152. Example peripheral interfaces 144 may include a serial interface controller 154 and a parallel interface controller 156, which may be configured to facilitate communication with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/O ports 158. An example communication device 146 may include a network controller 160, which may be arranged to facilitate communication with one or more other computing devices 162 via one or more communication ports 164 over a network communication link.

The network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media in a modulated data signal, such as a carrier wave or other transport mechanism. A "modulated data signal" may be a signal that has one or more of its data set or changed in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or special purpose network, and wireless media such as acoustic, radio Frequency (RF), microwave, infrared (IR) or other wireless media. The term computer readable media as used herein may include both storage media and communication media.

Computing device 100 also includes a storage interface bus 134 that is coupled to bus/interface controller 130. The storage interface bus 134 is coupled to the storage device 132, and the storage device 132 is adapted to store data. An example storage device 132 may include removable storage 136 (e.g., CD, DVD, U disk, removable hard disk, etc.) and non-removable storage 138 (e.g., hard disk drive HDD, etc.).

In computing device 100 according to the present application, application 122 includes a plurality of program instructions to perform method 200.

FIG. 2 illustrates a flow diagram of a page fault detection method 200 according to one embodiment of the application. The method 200 is suitable for execution in a computing device, such as the computing device 100 described previously.

As shown in fig. 2, one of the purposes of the method 200 is to implement a method for setting different sampling frequencies for access pages of different network address types, which can reduce the performance consumption of detection and alleviate unnecessary performance reporting stress on the server.

The method 200 begins at step 202 where, in response to a page access request, a network address type of an access page is obtained at step 202. The web address of a page refers to the URL address of the page. In this embodiment, the network address type of the page refers to that the regular matching rule types selected by the URL address of the page are different.

Specifically, the computing device may obtain a URL address corresponding to the page selected by the user, and parse the URL address to determine a network address type corresponding to the access page.

Subsequently, in step 204, a performance data acquisition frequency of the access page is determined based on the network address type.

In some embodiments, first, the computing device generates a configuration file related to the frequency of page performance data collection based on the network address type of each page. The configuration file will indicate the acquisition frequency of each page. In some embodiments, the same sampling frequency is set for URL addresses of the same regular matching rule, for example, five thousandths of the sampling frequency is uniformly set for URLs with network addresses host/detail/1 and host/detail/2 (i.e., one thousand accesses and five samples), one hundredth of the sampling frequency is set for pages corresponding to URLs with network address types host/list/1_3_3 and host/list/1_5_3 (i.e., one hundred accesses and one sample), and the like. Thus, the method can reduce unnecessary performance report and simultaneously has specific acquisition frequency configuration for different types of pages, so that the final sample size is not excessive or insufficient.

The performance data acquisition frequency of the access page is then matched from the configuration file based on the network address type of the access page.

Thereafter, in step 206, it is determined whether to collect performance data of the access page according to the performance data collection frequency. If the performance data collection frequency of the access page is one percent, the access is just the first hundred times, and the access page is not collected before, it is determined that performance data collection is performed on the access page, and the specific collection process refers to step 208. If the visit is fifty times in one hundred times and the previous fifty times visit is not collected, the performance data collection or not collection of the visit page can be judged. And in particular whether to collect or not, may be determined by the computing device at the discretion of the probability, as the application is not limited in this regard.

Thereafter, in step 208, performance data during the loading of the access page is obtained by retrieving the page performance interface and using the performance data, it is detected whether the access page is abnormally loaded. Note that in this embodiment, each page is loaded through WebView page controls.

Specifically, in the WebView control configuration stage, a JS script is injected, and the JS script associates the performance API. In this way, all the H5 pages accessed through the App WebView can be collected and reported through unified scripts no matter what language is developed, and the service side is not required to access.

It should be noted that, the page Performance interface is a Performance API, where Performance is an API provided by a browser and capable of giving multiple Performance indexes for loading a web page, and based on this interface, the following Performance data (including but not limited to) in loading a page may be extracted:

FirstContentful Paint (FCP), measures the time between the beginning of the loading of a page into the page and the first element being stained. The elements include text, pictures, canvas, etc. Speed Index, representing the time spent dyeing the page content, the lower the value the better.

Largest ContentfulPaint (LCP) the dye time of the largest content element visible in the viewport is measured. The elements include img, video, div and other block-level elements.

Time To Lnteractive (TTL) measures the time when all resources of a page are loaded successfully and can reliably respond quickly to user input, i.e., interaction time.

Total Blocking Time (TBT) this is the sum of all time periods between FCP and TTL.

Cumulative Layout Shift (CLS) the visual stability is measured and in order to provide a good user experience, the CLS of the page should be kept below 0.1.

In this embodiment, the type and number of the acquired performance data may be set according to the type of the abnormality in the page detection, and if it is required to detect whether the page is white, the page element data (DOM element) of the page, the preset resource data (key resource data, such as a buried point script or a video playing plug-in, etc.), and the display interface image data (for performing the screen capturing detection) are acquired through the JS script. If the page needs to be detected whether to be slowly loaded, collecting first time data (FCP data) indicating first drawing of page content and second time data (LCP data) indicating maximum drawing of page content of the page through JS script. If the page needs to be detected whether to be white or not, and if the page needs to be slowly loaded, all the data are acquired. The application is not limited in this regard.

Specifically, detecting whether a page is white screen includes the following steps.

First, page element (DOM element) data detection: and during loading the access page in the page control, acquiring page element data of the access page, and detecting whether each page element data is loaded successfully. Preferably, the number of the acquired page element data is counted, and when the number of the page element data is larger than a number threshold, loading of the page element data is determined, and the following second step is successfully performed. The DOM elements of the page are detected, the number of DOM elements is marked by 1 after the page is traversed to one visible DOM element, and when the number of DOM elements is greater than a preset number threshold, the DOM element data loading is successful. Otherwise, when the number of all the detected DOM elements is smaller than the preset number threshold after the detection is completed, the DOM element data loading failure is indicated, and the first (white screen) abnormality of the page is directly reported. The number threshold may be determined based on the total number of DOM elements contained in the page, e.g., 100 DOM elements are contained in the page in total, the number threshold may be set to 70 or 80, etc.

Second, detecting preset resource data: and acquiring preset resource data of the access page, and detecting whether each preset resource data is loaded successfully. Specifically, whether each preset resource data is loaded successfully or run successfully is detected, if the preset resource data is loaded successfully, the loading of the preset resource data is indicated to be successful, and the following third step is performed. If any one of the preset resources fails to load or fails to operate, the reported page is a white screen abnormality.

Third step, screen capturing detection: and acquiring the display interface image data of the access page, and detecting whether the display interface image data is normal or not. Specifically, the pixel duty ratio of each color in the display interface image data is acquired. And when the duty ratio of each pixel is smaller than the duty ratio threshold value, determining that the image data of the display interface is normal. Otherwise, the reported page is a white screen abnormality.

It should be noted that, in the first step or the second step, if a DOM element data loading failure or a preset resource loading failure has occurred, screen capturing detection is not performed, and the page is directly reported as a white screen abnormality. Only when screen capturing detection is needed, screen capturing detection is carried out, the generated performance cost is ensured to be as small as possible, the white screen reporting is ensured to be reported as completely as possible, and no omission exists.

Detecting whether a page is slow-loaded, comprising the steps of:

first, during loading of the access page in a page control, first time data (FCP) of the access page indicating first drawing of page content and second time data (LCP) indicating maximum content of the drawing page are obtained.

Then, it is detected whether the first time data is not greater than a first time threshold. If not, it is detected whether the second time data is not greater than a second time threshold. If the access page is not larger than the access page, the access page is determined to be normally loaded.

If the detection of the first time data is greater than the first time threshold or the second time data is greater than the second time threshold is detected, determining that a second exception (slow load) exists in the accessed page.

After the performance analysis results are obtained, in some embodiments, the network address, network address type, subdomain name prefix, primary directory, device information of the computing device, and loading results of the access page are associated and displayed.

Specifically, the network address type, the subdomain name prefix and the primary directory of the access page are classified and aggregated. And associating the data structure formed after aggregation with the device information of the computing device and the loading result of the access page. The device information of the computing device includes at least: browser information of the user device, a unique identification of the user device, and a current network state of the user. The device information is collected along with the performance data at step 208.

Illustratively, the default rule of aggregation categorization categorizes a large number of collected logs by adopting host (domain name of access page), matchPath (regular matching rule met by path of access page), biz (default to be sub domain name prefix), tags (default to use primary directory as one of labels) and type (page rendering mode is server side rendering or client side rendering), and the like.

The method provided by the application compensates the problem of single index compatibility by reporting the statistics of multiple indexes, and simultaneously increases the statistics of the number of key resources, the loading time consumption and the loading state, so that a business party can know the page performance more comprehensively and accurately.

The application uses the configuration of the acquisition frequency to configure different sampling rates aiming at URLs of different regular matching rules, and can configure specific acquisition frequencies for pages with different access amounts while reducing unnecessary performance reporting, so that the final sample amount is not excessive or too small.

The method integrates DOM element detection, key resource data detection and screen capturing pixel occupation ratio detection, and comprehensively judges the white screen and slow loading. Only when screen capturing detection is needed, screen capturing detection is carried out, the generated performance cost is ensured to be as small as possible, the white screen reporting is ensured to be reported as completely as possible, and no omission exists.

The various techniques described herein may be implemented in connection with hardware or software or, alternatively, with a combination of both. Thus, the methods and apparatus of the present application, or certain aspects or portions of the methods and apparatus of the present application, may take the form of program code (i.e., instructions) embodied in tangible media, such as removable hard drives, U-drives, floppy diskettes, CD-ROMs, or any other machine-readable storage medium, wherein, when the program is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the application.

In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Wherein the memory is configured to store program code; the processor is configured to perform the method of the application in accordance with instructions in said program code stored in the memory.

A9, the method of A1, further comprising: and correlating and displaying the network address, the network address type, the subdomain name prefix, the primary catalog, the equipment information of the computing equipment and the loading result of the access page. A10, the method as set forth in A2 or A4, wherein the page control is a WebView control, and the page performance interface is a performance API; and, the method further comprises: and injecting a JS script in the WebView control configuration stage, wherein the JS script is associated with the performance API.

By way of example, and not limitation, readable media comprise readable storage media and communication media. The readable storage medium stores information such as computer readable instructions, data structures, program modules, or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of readable media.

In the description provided herein, algorithms and displays are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with examples of the application. The required structure for a construction of such a system is apparent from the description above. In addition, the present application is not directed to any particular programming language. It should be appreciated that the teachings of the present application as described herein may be implemented in a variety of programming languages and that the foregoing description of specific languages is provided for disclosure of preferred embodiments of the present application.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the application may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the application, various features of the application are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed application requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this application.

Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment, or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into a plurality of sub-modules.

Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the application and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.

Furthermore, some of the embodiments are described herein as methods or combinations of method elements that may be implemented by a processor of a computer system or by other means of performing the functions. Thus, a processor with the necessary instructions for implementing the described method or method element forms a means for implementing the method or method element. Furthermore, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is for carrying out the functions performed by the elements for carrying out the objects of the application.

As used herein, unless otherwise specified the use of the ordinal terms "first," "second," "third," etc., to describe a general object merely denote different instances of like objects, and are not intended to imply that the objects so described must have a given order, either temporally, spatially, in ranking, or in any other manner.

While the application has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of the above description, will appreciate that other embodiments are contemplated within the scope of the application as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The disclosure of the present application is intended to be illustrative, but not limiting, of the scope of the application, which is defined by the appended claims.

Claims (10)

1. A method of page anomaly detection, performed in a computing device, the method comprising:

responding to a page access request, and acquiring a network address type of an access page;

determining the performance data acquisition frequency of the access page based on the network address type;

judging whether to collect the performance data of the access page according to the performance data collection frequency;

if yes, acquiring performance data during the loading of the access page by calling a page performance interface, and detecting whether the access page is abnormally loaded or not by utilizing the performance data.

2. The method of claim 1, wherein obtaining performance data during loading of the access page by invoking a page performance interface and using the performance data to detect whether the access page is abnormally loaded, comprises:

acquiring page element data of the access page during loading the access page in a page control, and detecting whether each page element data is loaded successfully or not;

if yes, acquiring preset resource data of the access page, and detecting whether each preset resource data is loaded successfully or not;

if yes, acquiring the display interface image data of the access page, and detecting whether the display interface image data is normal or not;

if yes, determining that the access page is normally loaded.

3. The method of claim 2, further comprising:

if the preset resource data loading failure, the preset resource data loading failure or the display interface image data abnormality is detected, determining that the access page has a first abnormality.

4. The method of claim 1, wherein obtaining performance data during loading of the access page by invoking a page performance interface and using the performance data to detect whether the access page is abnormally loaded, comprises:

during loading the access page in a page control, acquiring first time data of the access page indicating first drawing page content and second time data of the access page indicating maximum drawing page content;

detecting whether the first time data is not greater than a first time threshold;

if yes, detecting whether the second time data is not greater than a second time threshold;

if yes, determining that the access page is normally loaded.

5. The method of claim 4, further comprising:

and if the first time data is detected to be larger than a first time threshold value or the second time data is detected to be larger than a second time threshold value, determining that a second abnormality exists in the access page.

6. The method of claim 2, wherein detecting whether each of the page element data is loaded successfully comprises:

counting the number of the acquired page element data;

and when the number of the page element data is larger than a number threshold value, determining that the page element data is successfully loaded.

7. The method of claim 2, wherein detecting whether the display interface image data is normal comprises:

acquiring the pixel duty ratio of each color in the display interface image data;

and when the duty ratio of each pixel is smaller than the duty ratio threshold value, determining that the image data of the display interface is normal.

8. The method of claim 1, wherein determining the performance data collection frequency of the access page based on the network address type comprises:

generating a configuration file related to the page performance data acquisition frequency at least based on the network address type of each page;

and matching the performance data acquisition frequency of the access page from the configuration file based on the network address type of the access page.

9. A computing device, comprising:

at least one processor; and

a memory storing program instructions, wherein the program instructions are configured to be adapted to be executed by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 1-8.

10. A readable storage medium storing program instructions which, when read and executed by a computing device, cause the computing device to perform the method of any of claims 1-8.