Method and system for monitoring the performance of a distributed application

• US 8,032,626 B1
• Filed: 09/27/2007
• Issued: 10/04/2011
• Est. Priority Date: 11/16/2000
• Status: Expired due to Fees

• Current Assignee: Clouding Corporation (Marathon Patent Group, Inc.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Chen, John Bradley, Russell, Ethan George, Cote, Stephen William, Marsh, Brian David, Aikas, Erkki Ville Juhani
• Primary Examiner(s): STRANGE, AARON N
• Application Number:
  US11/863,027
• Time in Patent Office: 1,468 Days
• Field of Search: 709/223, 709/224, 715/736
• US Class Current: 709/224
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A service monitor and a browser monitor determine performance metrics on both a server and a client in connection with a distributed application running on a network. While applicable to other types of distributed application data, an example is described in which a Web page is requested by a user running a browser program on the client computer. In response, the server transmits the requested Web page, along with JavaScript code that defines a browser monitor, to the client. A browser monitoring function controlled by this code determines a plurality of different performance metrics related to the access of Web pages by the client. In addition, the server monitor determines performance metrics specific to its function in providing the Web page to the client. A correlated performance metric is determined by combining a server performance metric with a browser performance metric.

Claims

1. A method for determining one or more performance metrics for a distributed application in which distributed application data is transferred from a first site to a second site over a network, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

receiving a request for the distributed application data, the request being transmitted from the second site to the first site over the network, the time of the request being recorded at the second site using machine instructions;

in response to the request, transmitting the distributed application data from the first site to the second site over the network;

including machine instructions with the distributed application data that define a performance monitoring function;

including a monitor cookie with the distributed application data that indicates that the distributed application data is a monitored object, wherein the monitor cookie enables the second site to;

detect that the distributed application data is a monitored object;

execute, in response to detecting that the distributed application data is a monitored object, the machine instructions to implement the performance monitoring function to determine the one or more performance metrics for the distributed application without requesting any additional distributed application data from any other site, at least one of the one or more performance metrics being determined using the recorded time of the request.

2. The method of claim 1, wherein the machine instructions included with the distributed application data implement the performance monitoring function at the second site after the distributed application data is accessed at the second site.

3. The method of claim 1, further comprising collecting the one or more performance metrics for the distributed application over the network.

4. The method of claim 3, wherein collecting the performance metrics includes applying a probabilistic sampling parameter to determine whether performance metrics are collected from each of a plurality of sites.

5. The method of claim 3, further comprising determining whether to collect a performance metric from the second site as a function of a specific performance metric that was determined at the second site.

6. The method of claim 1, wherein the performance monitoring function is configured to cause the second site to determine one or more of:

(a) a fetch latency, corresponding to a time period required to fetch the distributed application data from the first site over the network;

(b) a render latency, corresponding to a time period required to fetch and display the distributed application data at the second site;

(c) a dwell latency, corresponding to a time period exhibited by a user requesting the distributed application data, before requesting other distributed application data;

(d) a per-image fetch latency, corresponding to a time period for fetching a specific image referenced in the distributed application data;

(e) an image arrival time, corresponding to a time at which a specific image, loaded as a part of accessing the distribution application data, arrives at the second site;

(f) a navigation status, corresponding to an event that brought a user to the distributed application data;

(g) a cache status, corresponding to a determination of whether the distributed application data was cached at the second site;

(h) a window resize event, corresponding to a determination of whether the user resized a window in which the distributed application data is accessed;

(i) a page stop event, corresponding to a determination of whether the user aborted loading the distributed application data;

(j) an image error event, corresponding to a determination of whether an error occurred while loading an image referenced in the distributed application data; and

(k) a JavaScript error event, corresponding to a determination of whether an error occurred during interpretation of JavaScript included in the distributed application data.

7. The method of claim 1, further comprising:

determining a performance metric at the first site; and

combining a performance metric determined at the second site with the performance metric determined at the first site to determine a correlated performance metric.

8. The method of claim 1, wherein the one or more performance metrics are determined without any apparent effect on the access of the distributed application data at the second site.

9. A non-transitory memory medium on which are stored machine readable instructions that, when executed by a client computing device, cause the client computing device to:

record the time of a request by the client computing device for distributed application data from another computing device;

receive the distributed application data from another computing device;

detect a monitor cookie included with the distributed application data received from the other computing device, the monitor cookie indicating that the distributed application data is a monitored object;

determine, in response to detecting the monitor cookie, at least one performance metric for the distributed application data on the client computing device, the performance metric being related to access of the distributed application data by a browser program executed on the client computing device and enabling at least one of a compound performance metric and a correlated performance metric to be determined without requesting any additional distributed application data from any other site.

10. The memory medium of claim 9, wherein the machine readable instructions cause the performance metric to be transmitted to a remote site over a network for determination of the correlated performance metric.

11. The memory medium of claim 9, wherein the performance metric is determined without the client device providing any indication to a user of the client device that the performance metric is being determined.

12. The memory medium of claim 9, wherein the machine readable instructions determine one or more of the following performance metrics:

(a) a fetch latency, corresponding to a time period required to fetch a base Web page document from a server over the network;

(b) a render latency, corresponding to a time period required to fetch and display all contents referenced within an HTML document on the client device;

(c) a dwell latency, corresponding to a time period exhibited by the user viewing the Web page, before navigating to a different Web page with the browser program;

(d) a per-image fetch latency, corresponding to a time period for fetching a specific image referenced in the Web page;

(e) an image arrival time, corresponding to a time at which a specific image, loaded as a part of rendering the Web page, arrives on the browser;

(f) a navigation status, corresponding to an event that brought the user to the Web page;

(g) a cache status, corresponding to a determination of whether the Web page was cached by the browser program or by a proxy;

(h) a window resize event, corresponding to a determination of whether the user resized a window in which the Web page is rendered;

(i) a page stop event, corresponding to a determination of whether the user aborted loading of the Web page;

(j) an image error event, corresponding to a determination of whether an error occurred while loading an image included in the Web page; and

(k) a JavaScript error event, corresponding to a determination of whether an error occurred during interpretation of JavaScript included in the Web page.

13. The memory medium of claim 9, wherein the machine readable instructions cause the client computing device to determine whether the distributed application data was previously cached by the client computing device.

14. The memory medium of claim 9, wherein the performance metric includes a performance metric for each image in a Web page.

15. A system for determining and collecting at least one performance metric related to access of a Web page by a browser program, comprising:

(a) a memory;

(b) a network interface; and

(c) a processing device that is coupled to the memory and the network interface, the network interface being coupled to a remote storage at a server to retrieve the Web page, the Web page including machine instructions that cause the processing device to;

detect a monitor cookie included with the Web page, the monitor cookie indicating that the Web page is a monitored document;

perform, in response to detecting the monitor cookie, a browser monitoring function when the Web page is loaded by the processing device, the browser monitoring function determining the at least one performance metric and being implemented without requiring any affirmative action by a user of the processing device and without using the browser monitoring function to request any further download from any site, the at least one performance metric being combined with another performance metric determined at the server to determine a correlated performance metric.

16. The system of claim 15, wherein the machine instructions further cause the processing device to transmit the performance metric from the processing device to a remote site over a network through the network interface.

17. The system of claim 15, wherein a determination of whether the performance metric will be accepted for processing by a data center is based upon a probabilistic sampling parameter, ensuring that performance metrics transmitted to the data center are randomly sampled.

18. The system of claim 15, wherein the machine instructions further cause the processing device to determine if the Web page was previously cached in the memory by the processing device before determining the performance metric.

19. The system of claim 15, wherein:

(a) the server executes a server monitoring function in regard to transferring the Web page to the processing device over the network;

(b) the server determines a server performance metric related to the transfer of the Web page to the processing device from the server computing device; and

(c) the server transmits the server performance metric to a data center for processing.

20. The system of claim 19, wherein the data center combines a performance metric determined by the browser monitoring function executed by the processing device with the server performance metric determined by the server computing function to determine the correlated performance metric.