System and methods for monitoring application server performance

• US 6,792,460 B2
• Filed: 01/20/2003
• Issued: 09/14/2004
• Est. Priority Date: 10/02/2002
• Status: Expired due to Term

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: Mercury Interactive Corp. (HP Inc.)
• Inventors: Sarig, Ido, Oulu, Yossi, Mogilevsky, Pinhas
• Primary Examiner(s): Coulter, Kenneth R.
• Application Number:
  US10/348,203
• Publication Number:
  US 20040068560A1
• Time in Patent Office: 603 Days
• Field of Search: 714/47, 714/25, 714/35, 709/105, 709/224, 717/124, 717/130
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A monitoring system monitors the amount of time spent by specific application components, such as Java components, during execution of specific web site transactions. A probe that runs on an application server initially instruments these components (preferably at component load time) to add code for tracking execution start and stop times. When a monitored transaction is executed by the application server, the probe measures the execution times of the invoked components—preferably at the component method level. The resulting measurement data is reported to a reports server, and is used to provide transaction-specific breakdowns of the amount of time spent by each instrumented component, and optionally each instrumented method within such components. In one embodiment, the probe only monitors transactions initiated by agent-generated transaction request messages that are marked or “colored” for monitoring, and thus ignores transactions initiated by actual users.

Claims

1. A method of monitoring execution of a transaction that invokes a plurality of application components of an application that runs on an application server, the method comprising:

instrumenting code of each of the plurality of application components to permit execution of each application component to be monitored on the application server;

in response to execution of the instrumented code within a thread, determining whether the thread is part of the transaction; and

when the thread is part of the transaction, tracing execution of the thread through each of the plurality of application components to measure an amount of time spent by each such application component on the transaction.

2. The method of claim 1, wherein tracing execution of the thread through each of the plurality of application components comprises recording execution start and stop times of specific methods of the application components.

3. The method of claim 1, wherein determining whether the thread is part of the transaction comprises determining whether an associated transaction request message is colored.

4. The method of claim 1, wherein the transaction is an actual user transaction.

5. The method of claim 1, further comprising monitoring execution of the transaction from a location external to the application server to measure an end-user response time, whereby the method generates data sufficient to assess an impact each of the application components has on transaction performance as seen by end users.

6. The method of claim 1, wherein the application components are J2EE components.

7. The method of claim 1, wherein instrumenting the code of the plurality of application components comprises instrumenting each component as it is loaded into a memory of the application server for execution.

8. The method of claim 7, wherein instrumenting the code of the plurality of application components further comprises using a patched version of a Java Virtual Machine class loader to access said code when application components are loaded.

9. A probe software component that embodies the method of claim 1.

10. The method of claim 1, further comprising, when the thread is not part of the transaction, refraining from tracing execution of the thread through each of the plurality of application components.

11. The method of claim 1, wherein the plurality of components is a subset of a complete set of application components invoked by the transaction, said subset being dependent upon configuration data that specifies which components are to be instrumented for monitoring.

12. A system for selectively monitoring application components on an application server, the system comprising:

an instrumentation component that instruments code of application components to permit execution thereof by the application server to be monitored;

a virtual machine that executes the application components on the application server;

wherein the virtual machine is configured to pass the application components to the instrumentation component for instrumentation prior to execution thereof by the virtual machine, and wherein the instrumentation component selectively instruments the application components received from the virtual machine based on configuration data that specifies which application components are to be instrumented for monitoring.

13. The system of claim 12, wherein the configuration data comprises heuristics for determining which application components are to be instrumented for monitoring.

14. The system of claim 12, further comprising a monitoring component that records execution start and stop times of instrumented application components executed by the virtual machine.

15. The system of claim 14, wherein the monitoring component records said start and stop times in association with specific user transactions to which they correspond, to thereby collect transaction-specific application server performance data.

16. The system of claim 12, wherein the virtual machine comprises a patched class loader class that is configured to pass code of an application component to the instrumentation component when said application component is loaded.

17. The method of claim 12, wherein the configuration data indirectly specifies which application components are to be instrumented for monitoring.