Measuring actual end user performance and availability of web applications

• US 9,973,568 B2
• Filed: 01/07/2015
• Issued: 05/15/2018
• Est. Priority Date: 07/21/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Letca, Ilarie, Coelho, Alexandre, Kurapati, Venkata Seshu Kumar, Sudhakar, Rajeev, Savage, Daniel, Sanghvi, Ashvinkumar, Lim, Jin Soon
• Primary Examiner(s): DAO, THUY CHAN
• Application Number:
  US14/591,659
• Publication Number:
  US 20150304398A1
• Time in Patent Office: 1,224 Days
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Techniques for monitoring web application performance are provided. A request for a web application is received at an application server. A response pipeline at the application server generates client application code corresponding to the requested web application. The client application code is intercepted in the response pipeline. Instrumentation code is inserted into the intercepted client application code to generate an instrumented client application code. The instrumentation code is configured to be executed when the instrumented client application code is rendered at the client to capture performance information at the client, and is configured to transmit the captured performance information from the client.

Claims

1. A method in a client, comprising:

transmitting a request to a server for a web application containing a web page;

receiving an instrumented client application code from the server in response to the request, the instrumented client application code configured to implement the web application, the instrumented client application code including instrumentation code having portions inserted into a header and a body of the instrumented client application code at the server, the instrumentation code configured to be executed to capture performance information regarding the web application at the client when the instrumented client application code is rendered at the client, and being configured to transmit the captured performance information from the client; and

said executing comprising;

capturing a start load time for the web page with a first portion of the instrumentation code inserted in the header;

capturing an end load time for the web page with a second portion of the instrumentation code inserted in the body; and

calculating a load duration based on the end load time and the start load time.

2. The method of claim 1, further comprising:

rendering the instrumented client application code using a browser at the client;

executing the instrumentation code during said rendering to capture performance information.

3. The method of claim 2, further comprising:

transmitting the captured performance information to a management server.

4. The method of claim 2, further comprising:

aggregating captured performance information over multiple executions of the instrumentation code; and

transmitting the aggregated captured performance information to a management server.

5. The method of claim 2, wherein the web application includes a web page, and the instrumented client application code comprises HTML (hypertext markup language) code.

6. The method of claim 1, wherein said executing further comprises:

determining a load duration by subtracting the captured start load time from the captured end load time.

7. The method of claim 1, wherein said receiving comprises:

receiving the instrumented client application code with the inserted instrumentation code programmed in JavaScript.

8. The method of claim 1, wherein the instrumented client application code is modified at n locations to cause the portion inserted into the header to be invoked at each of the n locations, where n is an integer and greater than zero;

and

the captured performance information includes performance data of pre-defined versions of particular web browsers.

9. A client computing device, comprising:

at least one processor; and

at least one memory that stores program code configured to be executed by the at least one processor circuit, the program code comprising;

a browser configured to receive an instrumented client application code from a server in response to a request for a web application containing a web page, the instrumented client application code configured to implement the web application, the instrumented client application code including instrumentation code having portions inserted into a header and a body of the instrumented client application code at the server, the instrumentation code including;

a performance information capturing module configured to be executed to capture performance information regarding the web application when the instrumented client application code is rendered at the client computing device, the performance information capturing module configured to;

capture a start load time for the web page with a first portion of the instrumentation code inserted in the header;

capture an end load time for the web page with a second portion of the instrumentation code inserted in the body; and

calculate a load duration based on the end load time and the start load time, and

a server interface module configured to transmit the captured performance information from the client.

10. The client computing device of claim 9, wherein the instrumentation code further comprises:

a data aggregation module configured to aggregate captured performance information over multiple executions of the instrumentation code; and

the server interface module is configured to transmit the aggregated captured performance information.

11. The client computing device of claim 9, wherein the web application includes a web page, and the instrumented client application code comprises HTML (hypertext markup language) code.

12. The client computing device of claim 9, wherein the instrumentation code is further configured to:

determine a load duration by subtracting the captured start load time from the captured end load time.

13. The client computing device of claim 9, wherein the instrumentation code is configured to:

capture data regarding at least one of a type of browser at the client, a locale of the client, or a client language.

14. The client computing device of claim 9, wherein the inserted instrumentation code is programmed in JavaScript.

15. A method in one or more servers, comprising;

receiving a client application code corresponding to a web application requested by a client, the requested web application containing a web page;

inserting instrumentation code into the client application code to generate an instrumented client application code, portions of the instrumentation code inserted into a header and a body of the instrumented client application code, the instrumentation code configured to be executed when the instrumented client application code is rendered at the client to capture performance information regarding the web application at the client, and being configured to transmit the captured performance information from the client, the instrumentation code configured to capture a start load time in a browser for the web page with a first portion of the instrumentation code inserted in the header, capture an end load time in the browser for the web page with a second portion of the instrumentation code inserted in the body, and calculate a load duration based on the end load time and the start load time; and

providing the instrumented client application code to be transmitted to the client.

16. The method of claim 15, further comprising:

receiving the captured performance information from the client.

17. The method of claim 15, wherein the instrumented client application code is configured to be rendered by the browser at the client, and the instrumentation code is configured to be executed during the rendering by the browser at the client to capture the performance information.

18. The method of claim 17, wherein the web application includes a web page, and the instrumented client application code comprises HTML (hypertext markup language) code.

19. The method of claim 15, further comprising:

configuring the instrumentation code to determine a load duration by subtracting the captured start load time from the captured end load time.

20. The method of claim 15, further comprising:

configuring the instrumentation code to capture data regarding at least one of a type of browser at the client, a locale of the client, or a client language.