BUSINESS TRANSACTION CORRELATION WITH CLIENT REQUEST MONITORING DATA

• US 20150067031A1
• Filed: 09/04/2013
• Published: 03/05/2015
• Est. Priority Date: 09/04/2013
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: AppDynamics, Inc. (Cisco Systems, Inc.)
• Inventors: Acharya, Manoj, Srinivasaiah, Vinay, Cath, Adam, Thomas, Binil, Rowe, Ed
• Granted Patent: US 9,961,129 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• 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
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

A system monitors a client request and a backend business transaction performed in response to the request and correlates the data generated from monitoring the request and business transaction. A request may be monitored in detail to determine several metrics. The metrics may include sever connection time, response receipt completion time, document download time, document processing time, and page rendering time. The metrics may be determined for an entire content page as well as individual page elements, such as Iframes and elements constructed from AJAX techniques.

Claims

1. A method for reporting data, comprising:

receiving from a client a client request identifier and data associated with processing the client request at the client device;

receiving from one or more servers the client request identifier and data associated with processing a business transaction associated with the client request; and

reporting the data associated with processing the client request at the client device and the data associated with processing a business transaction at the one or more servers.

2. The method of claim 1, wherein the data associated with processing the client request includes the name of the element or page sending the request and the name of the parent page sending the request.

3. The method of claim 1, wherein in the data associated with processing the client request includes a first time associated with one or more of redirected connections, domain look-up communications, transmission control protocol connection communications, and establishing a secure socket layer communications.

4. The method of claim 1, wherein in the data associated with processing the client request includes a second time at which the beginning of a response to the request sent to the server is received.

5. The method of claim 1, wherein in the data associated with processing the client request includes a third time at which the receipt of the response is complete.

6. The method of claim 1, wherein in the data associated with processing the client request includes a fourth time at which a document associated with the response is loaded by the network browser application.

7. The method of claim 1, wherein in the data associated with processing the client request includes a fifth time at which the content page is completely rendered with the document by the network browser application.

8. The method of claim 1, further comprising detecting that the client request is associated with an error, the reported data identifying the request and the performance of the business transaction associated with the client request associated with the error.

9. The method of claim 1, further comprising generating a hierarchy of elements which send a request to the one or more servers and are included in a base content page, the hierarchy generated from the client request identifier and an identifier associated with the base content page.

10. The method of claim 8, wherein the hierarchy is generated from the base content page identifier and a parent content page identifier for each element which sends a request to the one or more servers.

11. The method of claim 8, wherein the data associated with processing the client request at the client device is reported for each level in the hierarchy.

55. The computer readable storage medium claim 8, wherein the unique request identifier is received in a header of an XHR response.

12. A method for processing a client request, comprising

sending a request to a remote server;

receiving from the server a unique request identifier associated with the request, the unique request identifier created by the server in response to receiving the request;

capturing performance data associated with processing the request by the network browser; and

reporting the performance data and the unique request identifier associated with the request.

13. The method of claim 12, wherein the request identifier is associated with a request sent from an Iframe element within the content page.

14. The method of claim 12, wherein the request identifier is associated with a request due to the use of AJAX techniques within the content page.

15. The method of claim 12, wherein the reporting includes transmitting an identifier for a parent page for an element of the content page that sent the request.

16. The method of claim 12, wherein the unique request identifier is received from the server in a cookie.

17. The method of claim 16, wherein the cookie is received before receipt of the response is complete.

18. The method of claim 12, wherein the unique request identifier is received in a portion of the response.

19. The method of claim 12, wherein the unique request identifier is received in a header of an HTTP response.

20. The method of claim 12, wherein reporting includes sending metrics and the unique request identifier to a server for reporting by the server, the server reporting the received metrics and the unique request identifier with metrics provided by the server for processing the response at the server.

21. The method of claim 12, wherein the request is associated with two or more business transactions.

22. The method of claim 12, wherein reporting the performance data includes:

providing performance data for a business transaction associated with the request; and

providing performance data for the network browser processing the request.

23. The method of claim 22, further comprising receiving input associated with a content page through a network browser on a client device;

24. The method of claim 12, further comprising:

sending a second request to a second server in response to the user input; and

receiving a second unique request identifier associated with the second request, wherein the metrics are reported for the first request and the second request corresponding to the first input.

25. The method of claim 12, further comprising generating a unique request identifier for the base content page and one or more second unique request identifiers for elements within the content page that send a request to a remote server.

26. A method for reporting data, comprising:

receiving a request from a client, the request associated with one of a plurality of content page elements requesting data from one or more remote servers;

generating a unique request identifier for the received request; and

transmitting the unique request identifier to the requesting client.

27. The method of claim 26, wherein the request is a content page request, the unique request identifier transmitted to the client in both a body of the response and a cookie file.

28. The method of claim 27, wherein the cookie is written when the unique identifier is created and before the response is transmitted to the client.

29. The method of claim 26, wherein the request is an XML HTTP request, the unique request identifier transmitted to the client in an HTTP header.

30. The method of claim 26, receiving a second request from the client, the second request and the first request associated with a single content page rendered by a web browser.

31. A method for processing a client request, comprising:

receiving input associated with a content page through a network browser on a client device;

detecting a first time at which the client device connects with a server that creates a response having content for a content page, the response created in response to a request sent based on the received input; and

detecting a second time at which the response completed at the client device.

32. The method of claim 31, wherein the first time includes time associated with one or more of redirected connections, domain look-up communications, transmission control protocol connection communications, and establishing a secure socket layer communications.

33. The method of claim 31, detecting a second time at which the beginning of a response to the request sent to the server is received.

34. The method of claim 31, detecting a third time at which the receipt of the response is complete.

35. The method of claim 31, detecting a fourth time at which a document associated with the response is loaded by the network browser application.

36. The method of claim 31, detecting a fifth time at which the content page is completely rendered with the document by the network browser application.

37. A computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for processing a client request, the method comprising:

receiving from a client a client request identifier and data associated with processing the client request at the client device;

receiving from one or more servers the client request identifier and data associated with processing a business transaction associated with the client request; and

reporting the data associated with processing the client request at the client device and the data associated with processing a business transaction at the one or more servers.

38. The computer readable storage medium of claim 37, wherein the data associated with processing the client request includes the name of the element sending the request and the name of the parent node of the element sending the request.

39. The computer readable storage medium of claim 37, wherein in the data associated with processing the client request includes a first time associated with one or more of redirected connections, domain look-up communications, transmission control protocol connection communications, and establishing a secure socket layer communications.

40. The computer readable storage medium of claim 37, wherein in the data associated with processing the client request includes a second time at which the beginning of a response to the request sent to the server is received.

41. The computer readable storage medium claim 37, wherein in the data associated with processing the client request includes a third time at which the receipt of the response is complete.

42. The computer readable storage medium claim 37, wherein in the data associated with processing the client request includes a fourth time at which a document associated with the response is loaded by the network browser application.

43. The computer readable storage medium claim 37, wherein in the data associated with processing the client request includes a fifth time at which the content page is completely rendered with the document by the network browser application.

44. The computer readable storage medium of claim 37, the method further comprising detecting that the client request is associated with an error, the reported data identifying the request and the performance of the business transaction associated with the client request associated with the error.

45. The computer readable storage medium of claim 37, the method further comprising generating a hierarchy of elements which send a request to the one or more servers and are included in a base content page, the hierarchy generated from the client request identifier and an identifier associated with the base content page.

46. The computer readable storage medium of claim 45, wherein the hierarchy is generated from the base content page identifier and a parent content page identifier for each element which sends a request to the one or more servers.

47. The computer readable storage medium of claim 45, wherein the data associated with processing the client request at the client device is reported for each level in the hierarchy.

48. A computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for processing a client request, the method comprising:

sending a request to a remote server;

receiving from the server a unique request identifier associated with the request, the unique request identifier created by the server in response to receiving the request;

capturing performance data associated with processing the request by the network browser; and

reporting the performance data and the unique request identifier associated with the request.

49. The computer readable storage medium claim 48, wherein the request identifier is associated with a request sent from an Iframe element within the content page.

50. The computer readable storage medium claim 48, wherein the request identifier is associated with a request sent from an element generated using AJAX techniques within the content page.

51. The computer readable storage medium claim 48, wherein the reporting includes transmitting an identifier for a parent node for an element of the content page that sent the request.

52. The computer readable storage medium claim 51, wherein the unique request identifier is received from the server in a cookie.

53. The computer readable storage medium claim 51, wherein the cookie is received before receipt of the response is complete.

54. The computer readable storage medium claim 48, wherein the unique request identifier is received in a portion of the response.

56. The computer readable storage medium claim 48, wherein reporting includes sending metrics and the unique request identifier to a server for reporting by the server, the server reporting the received metrics and the unique request identifier with metrics provided by the server for processing the response at the server.

57. The computer readable storage medium claim 48, wherein the request is associated with two or more business transactions.

58. The computer readable storage medium claim 48, wherein reporting the performance data includes:

providing performance data for a business transaction associated with the request; and

providing performance data for the network browser processing the request.

59. The computer readable storage medium claim 58, further comprising receiving input associated with a content page through a network browser on a client device;

60. The computer readable storage medium claim 48, further comprising:

sending a second request to a second server in response to the user input; and

receiving a second unique request identifier associated with the second request, wherein the metrics are reported for the first request and the second request corresponding to the first input.

61. The computer readable storage medium claim 48, further comprising generating a unique request identifier for the base content page and one or more second unique request identifiers for elements within the content page that send a request to a remote server.

62. A computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for processing a client request, the method comprising:

receiving a request from a client, the request associated with one of a plurality of content page elements requesting data from one or more remote servers;

generating a unique request identifier for the received request; and

transmitting the unique request identifier to the requesting client.

63. The computer readable storage medium claim 62, wherein the request is a content page request, the unique request identifier transmitted to the client in both a body of the response and a cookie file.

64. The computer readable storage medium claim 63, wherein the cookie is written when the unique identifier is created and before the response is transmitted to the client.

65. The computer readable storage medium claim 62, wherein the request is an XML HTTP request, the unique request identifier transmitted to the client in an HTTP header.

66. The computer readable storage medium claim 62, receiving a second request from the client, the second request and the first request associated with a single content page rendered by a web browser.

76. The system of claim 65, wherein in the data associated with processing the client request includes a second time at which the beginning of a response to the request sent to the server is received.

67. A computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for processing a client request, the method comprising:

receiving input associated with a content page through a network browser on a client device;

detecting a first time at which the client device connects with a server that creates a response having content for a content page, the response created in response to a request sent based on the received input; and

detecting a second time at which the response completed at the client device.

68. The computer readable storage medium claim 67, wherein the first time includes time associated with one or more of redirected connections, domain look-up communications, transmission control protocol connection communications, and establishing a secure socket layer communications.

69. The computer readable storage medium claim 67, detecting a second time at which the beginning of a response to the request sent to the server is received.

70. The computer readable storage medium claim 67, detecting a third time at which the receipt of the response is complete.

71. The computer readable storage medium claim 67, detecting a fourth time at which a document associated with the response is loaded by the network browser application.

72. The computer readable storage medium claim 67, detecting a fifth time at which the content page is completely rendered with the document by the network browser application.

73. A system for processing a client request, comprising:

a processor;

memory; and

one or more software modules stored in the memory and executed by the processor to receive from a client a client request identifier and data associated with processing the client request at the client device, receive from one or more servers the client request identifier and data associated with processing a business transaction associated with the client request, and report the data associated with processing the client request at the client device and the data associated with processing a business transaction at the one or more servers.

74. The system of claim 73, wherein the data associated with processing the client request includes the name of the element sending the request and the name of the parent node of the element sending the request.

75. The system of claim 73, wherein in the data associated with processing the client request includes a first time associated with one or more of redirected connections, domain look-up communications, transmission control protocol connection communications, and establishing a secure socket layer communications.

77. The system of claim 73, wherein in the data associated with processing the client request includes a third time at which the receipt of the response is complete.

78. The system of claim 73, wherein in the data associated with processing the client request includes a fourth time at which a document associated with the response is loaded by the network browser application.

79. The system of claim 73, wherein in the data associated with processing the client request includes a fifth time at which the content page is completely rendered with the document by the network browser application.

80. The system of claim 73, the modules further executable to detect that the client request is associated with an error, the reported data identifying the request and the performance of the business transaction associated with the client request associated with the error.

81. The system of claim 73, the modules further executable to generate a hierarchy of elements which send a request to the one or more servers and are included in a base content page, the hierarchy generated from the client request identifier and an identifier associated with the base content page.

82. The system of claim 81, wherein the hierarchy is generated from the base content page identifier and a parent content page identifier for each element which sends a request to the one or more servers.

83. The system of claim 81, wherein the data associated with processing the client request at the client device is reported for each level in the hierarchy.

84. A system for processing a client request, comprising:

a processor;

memory; and

one or more software modules stored in the memory and executed by the processor to send a request to a remote server, receive from the server a unique request identifier associated with the request, the unique request identifier created by the server in response to receiving the request, capture performance data associated with processing the request by the network browser, and report the performance data and the unique request identifier associated with the request.

85. The system of claim 84, wherein the request identifier is associated with a request sent from an Iframe element within the content page.

86. The system of claim 84, wherein the request identifier is associated with a request sent from an element generated using AJAX techniques within the content page.

87. The system of claim 84, wherein the reporting includes transmitting an identifier for a parent node for an element of the content page that sent the request.

88. The system of claim 84, wherein the unique request identifier is received from the server in a cookie.

89. The system of claim 88, wherein the cookie is received before receipt of the response is complete.

90. The system of claim 84, wherein the unique request identifier is received in a portion of the response.

91. The system of claim 84, wherein the unique request identifier is received in a header of an XHR response.

92. The system of claim 84, wherein reporting includes sending metrics and the unique request identifier to a server for reporting by the server, the server reporting the received metrics and the unique request identifier with metrics provided by the server for processing the response at the server.

93. The system of claim 84, wherein the request is associated with two or more business transactions.

94. The system of claim 84, the modules executable to provide performance data for a business transaction associated with the request and provide performance data for the network browser processing the request.

95. The system of claim 94, further comprising receiving input associated with a content page through a network browser on a client device;

96. The system of claim 84, the modules further executable to send a second request to a second server in response to the user input and receive a second unique request identifier associated with the second request, wherein the metrics are reported for the first request and the second request corresponding to the first input.

97. The system of claim 84, the modules further executable to generate a unique request identifier for the base content page and one or more second unique request identifiers for elements within the content page that send a request to a remote server.

98. A system for processing a client request, comprising:

a processor;

memory; and

one or more software modules stored in the memory and executed by the processor to receive a request from a client, the request associated with one of a plurality of content page elements requesting data from one or more remote servers, generate a unique request identifier for the received request, and transmit the unique request identifier to the requesting client.

99. The system of claim 98, wherein the request is a content page request, the unique request identifier transmitted to the client in both a body of the response and a cookie file.

100. The system of claim 98, wherein the cookie is written when the unique identifier is created and before the response is transmitted to the client.

101. The system of claim 98, wherein the request is an XML HTTP request, the unique request identifier transmitted to the client in an HTTP header.

102. The system of claim 98, receiving a second request from the client, the second request and the first request associated with a single content page rendered by a web browser.

103. A system for processing a client request, comprising:

a processor;

memory; and

one or more software modules stored in the memory and executed by the processor to receive input associated with a content page through a network browser on a client device, detect a first time at which the client device connects with a server that creates a response having content for a content page, the response created in response to a request sent based on the received input, and detect a second time at which the response completed at the client device.

104. The system of claim 103, wherein the first time includes time associated with one or more of redirected connections, domain look-up communications, transmission control protocol connection communications, and establishing a secure socket layer communications.

105. The system of claim 103, detecting a second time at which the beginning of a response to the request sent to the server is received.

106. The system of claim 103, detecting a third time at which the receipt of the response is complete.

107. The system of claim 103, detecting a fourth time at which a document associated with the response is loaded by the network browser application.

108. The system of claim 103, detecting a fifth time at which the content page is completely rendered with the document by the network browser application.