PERFORMANCE MONITORING OF NETWORK APPLICATIONS

• US 20110252087A1
• Filed: 06/23/2011
• Published: 10/13/2011
• Est. Priority Date: 10/12/2005
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Bley, John B., Zuzga, Brian, Ng, Krates, Addleman, Mark Jacob
• Granted Patent: US 8,239,528 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet

Abstract

Network performance is monitored using timing information retrieved from a client device, server in communication with the client, or both. Client side timing information is retrieved using performance monitoring code provided by the server. The code may be provided to the client as part of a content response. Once content in the provided content response is loaded, the code sends the timing information to the server. The server may then process the timing information to calculate response time and other time information metrics.

Claims

1. A method for monitoring a client, comprising:

receiving first content source information from a client device by a server, the first content source information associated with a user selection;

receiving second content source information from the client device by the server, the second content source information associated with the most recent source of content accessed by the client device in response to the user selection; and

determining whether the first content source information matches the second content source information.

2. The method of claim 1, wherein the first content source information is a selected URL and the second content source information is a current URL.

3. The method of claim 1, wherein the first content source information and the second content source information are provided as timing information by the client device to the server.

4. The method of claim 1, further comprising:

determining if client time response data received from a client and associated with a content request and server time response data received from a server and associated with the content request differ by more than a time difference threshold.

5. The method of claim 1, further comprising;

determining that the client accessed an intervening server in response to detecting that the first content source information does not match the second content source information.

6. A method of accessing timing information, comprising:

storing first time data associated with receiving a user selection through an interface, the interface having content in two or more frames;

storing two or more second time data in separate files, each of the second time data associated with the time at which content is unloaded from one of the two or more frames;

accessing third time data associated with loading content in a frame for which content has been unloaded; and

reporting the first time data, the third time data, and one of the second time data, the third time data and the reported second time data associated with the same interface frame.

7. The method of claim 6, wherein said reporting includes:

deleting the file containing the reported second time data, wherein said deleting is performed after the first time data, the third time data, and the one of the second time data is reported.

8. The method of claim 6, wherein said accessing includes:

detecting a number of third time data, the number of third time data being the same as the first number of second time data.

9. The method of claim 8, wherein said reporting includes:

clearing the first time data after the last of the number of third time data is reported.

10. The method of claim 6, wherein the interface is provided by a network browser application.

11. The method of claim 6, wherein the first time data is time information associated with an On Click event, each of the two or more second time data is time information associated with a different On Unload event, and the third time data is a time associated with an On Load event, the On Unload event and On Load event associated with the same interface frame.

12. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method comprising:

receiving a user selection through an interface having two or more frames, the user input associated with one of the two or more frames;

loading content for two or more of the two or more frames in response to receiving the user selection;

storing time information associated with the user input and the loaded content for the two or more frames; and

sending the time information to a server.

13. The one or more processor readable storage devices of claim 12, wherein the time information includes a time associated with receiving the user input.

14. The one or more processor readable storage devices of claim 12, wherein the time information includes a time associated with loading content in each of the two or more frames in which content is loaded.

15. The one or more processor readable storage devices of claim 12, wherein said storing the time information includes:

storing time information to a browser cookie file.

16. The one or more processor readable storage devices of claim 12, wherein said sending the time information includes:

determining that content has been loaded in a frame; and

sending time information associated with user input and the frame associated with the loaded content.

17. The one or more processor readable storage devices of claim 12, wherein said sending the time information includes:

sending information identifying each frame in which content has been loaded.