METHOD TO CONFIGURE MONITORING THRESHOLDS USING OUTPUT OF LOAD OR RESOURCE LOADINGS
First Claim
1. A method of identifying and load testing resources invoked by a web app (inclusive of a web application or a web page), the method including:
- initiating a load test of a subject web app that requests resources from a system under test, including,for each testable resource in a set of multiple testable resources, causing a test load to vary for the testable resource in a test segment, andcollecting from the test segments at least one measure of load-dependent results related to expected user experience as the test load varies;
wherein the set of testable resources is a selected subset of resources, including nested resources, requested by a user device upon invoking the subject web app;
correlating the load-dependent results and identifying co-variant load-dependent results;
responsive to receiving user input selecting a first alert threshold for a first testable resource or for a first load-dependent result, using the identified co-variant load-dependent results to suggest or set a second alert threshold for a second load-dependent result; and
persisting the first alert threshold and the second alert threshold to be applied by a monitoring device.
1 Assignment
0 Petitions
Accused Products
Abstract
The technology disclosed enables the automatic definition of monitoring alerts for a web page across a plurality of variables such as server response time, server CPU load, network bandwidth utilization, response time from a measured client, network latency, server memory utilization, and the number of simultaneous sessions, amongst others. This is accomplished through the combination of load or resource loading and performance snapshots, where performance correlations allow for the alignment of operating variables. Performance data such as response time for the objects retrieved, number of hits per second, number of timeouts per sec, and errors per second can be recorded and reported. This allows for the automated ranking of tens of thousands of web pages, with an analysis of the web page assets that affect performance, and the automatic alignment of performance alerts by resource participation.
-
Citations
23 Claims
-
1. A method of identifying and load testing resources invoked by a web app (inclusive of a web application or a web page), the method including:
-
initiating a load test of a subject web app that requests resources from a system under test, including, for each testable resource in a set of multiple testable resources, causing a test load to vary for the testable resource in a test segment, and collecting from the test segments at least one measure of load-dependent results related to expected user experience as the test load varies; wherein the set of testable resources is a selected subset of resources, including nested resources, requested by a user device upon invoking the subject web app; correlating the load-dependent results and identifying co-variant load-dependent results; responsive to receiving user input selecting a first alert threshold for a first testable resource or for a first load-dependent result, using the identified co-variant load-dependent results to suggest or set a second alert threshold for a second load-dependent result; and persisting the first alert threshold and the second alert threshold to be applied by a monitoring device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 20, 21)
-
-
13. A method of identifying and load testing resources critical to invoking a web app, the method including:
-
parsing a subject web app to identify resources, including nested resources, loaded upon invoking the subject web app; conducting a hybrid load test of a selected plurality of the identified resources, including; load testing response to requests for particular resources among the identified resources, wherein the load testing simulates a multiplicity of user sessions requesting the particular resources and a number of the user sessions varies during the load testing; and experience testing load time of at least components of the subject web app during the load testing, wherein the experience testing emulates a browser, requests the subject web app, requests the identified resources and nested resources, and records at least response times for loading the identified resources and nested resources; and identifying from the load testing and experience testing some of the particular resources as more sensitive than others to how many user sessions request the particular resource; generating data for display that includes the identified more sensitive particular resources. - View Dependent Claims (14, 15, 16, 17, 18, 19)
-
-
22. At least one device, including a processor, a network interface, and memory storing computer instructions that, when executed on the processor, cause the device to a hybrid load test of a selected plurality of identified resources, including:
-
load testing response to requests for particular resources among the identified resources, wherein the load testing simulates a multiplicity of user sessions requesting the particular resources and a number of the user sessions varies during the load testing; and experience testing load time of at least components of the subject web app during the load testing, wherein the experience testing emulates a browser, requests the subject web app, requests the identified resources and nested resources, and records at least response times for loading the identified resources and nested resources; and identifying from the load testing and experience testing some of the particular resources as more sensitive than others to how many user sessions request the particular resource; generating data for display that includes the identified more sensitive particular resources.
-
-
23. A non-transitory computer readable medium storing instructions that, when executed on the a processor device, cause the device to a hybrid load test of a selected plurality of identified resources, including:
-
load testing response to requests for particular resources among the identified resources, wherein the load testing simulates a multiplicity of user sessions requesting the particular resources and a number of the user sessions varies during the load testing; and experience testing load time of at least components of the subject web app during the load testing, wherein the experience testing emulates a browser, requests the subject web app, requests the identified resources and nested resources, and records at least response times for loading the identified resources and nested resources; and identifying from the load testing and experience testing some of the particular resources as more sensitive than others to how many user sessions request the particular resource; generating data for display that includes the identified more sensitive particular resources.
-
Specification