Intelligent performance monitoring based on user transactions

• US 7,552,212 B2
• Filed: 10/22/2004
• Issued: 06/23/2009
• Est. Priority Date: 10/22/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Chen, Xiaoping, Lavery, Andrew Jason, Chagoly, Bryan Christopher, McKinney, Howard Milton, Sexton, Kirk Malcolm
• Primary Examiner(s): Patel; Haresh N
• Application Number:
  US10/971,472
• Publication Number:
  US 20060107255A1
• Time in Patent Office: 1,705 Days
• Field of Search: 709/203, 709217-228
• 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: G06F 2201/87 Monitoring of transactions

Abstract

A system and method to allow an individual transaction in an instrumented software application to be monitored according to its own configuration. In one preferred embodiment, each transaction is associated with a token. The token includes the monitoring configuration that should be used for the associated transaction. When the application entry point is reached for the transaction, the token is looked up and retrieved, and the monitoring policy configuration of the token determines what data is gathered about the transaction.

Claims

1. A method for monitoring an application operating on a computer system, the method comprising:

monitoring an entry point of the application for a transaction to selectively monitor the transaction within a plurality of transactions in the application in order to minimize computational overhead and data recording associated with monitoring all of the plurality of transactions in the application, wherein the entry point is a location in the application where the transaction is recorded by a monitoring application, and wherein each transaction in the plurality of transactions is associated with a corresponding token that includes data that uniquely identifies an associated transaction and contains configuration information required by a probe that monitors an entry point in the application where the associated transaction occurs to determine an appropriate level of data recording for the associated transaction;

responsive to the entry point being reached by the application for the transaction, acquiring a token associated with the transaction, wherein the token is acquired by looking up the transaction in a policy mapper, and wherein the policy mapper maps a monitoring policy to the transaction from a list of monitoring policies;

monitoring the transaction according to the monitoring policy of the token associated with the transaction, wherein the monitoring policy contains a host name, a user name, an application name, a transaction name, scheduling information that defines when the transaction is recorded, a threshold that defines an execution time limit for the transaction, and the configuration information that determines the appropriate level of data recording for the transaction, and wherein the monitoring policy of the token determines what specific information is gathered about the transaction, and wherein the transaction includes a plurality of sub-transactions, and wherein each sub-transaction within the plurality of sub-transactions is associated with the monitoring policy of the token;

collecting the appropriate level of data recording for the transaction defined by the configuration information; and

sending the collected appropriate level of data recording for the transaction to the monitoring application, wherein the monitoring application records the collected appropriate level of data recording for the transaction for use by a user of the monitoring application.

2. A data processing system for monitoring transactions in an application, comprising:

a storage device connected to the bus system, wherein the storage device includes a set of instructions; and

a processing unit connected to the bus system,

the processing unit executes the set of instructions to monitor an entry point of the application for a transaction to selectively monitor the transaction within a plurality of transactions in the application in order to minimize computational overhead and data recording associated with monitoring all of the plurality of transactions in the application, wherein the entry point is a location in the application where the transaction is recorded by a monitoring application, and wherein each transaction in the plurality of transactions is associated with a corresponding token that includes data that uniquely identifies an associated transaction and contains configuration information required by a probe that monitors an entry point in the application where the associated transaction occurs to determine an appropriate level of data recording for the associated transaction;

acquire a token associated with the transaction in response to the entry point being reached by the application for the transaction, wherein the token is acquired by looking up the transaction in a policy mapper, and wherein the policy mapper maps a monitoring policy to the transaction from a list of monitoring policies;

monitor the transaction according to the monitoring policy of the token associated with the transaction, wherein the monitoring policy contains a host name, a user name, an application name, a transaction name, scheduling information that defines when the transaction is recorded, a threshold that defines an execution time limit for the transaction, and the configuration information that determines the appropriate level of data recording for the transaction, and wherein the monitoring policy of the token determines what specific information is gathered about the transaction, and wherein the transaction includes a plurality of sub-transactions, and wherein each sub-transaction within the plurality of sub-transactions is associated with the monitoring policy of the token;

collect the appropriate level of data recording for the transaction defined by the configuration information; and

send the collected appropriate level of data recording for the transaction to the monitoring application, wherein the monitoring application records the collected appropriate level of data recording for the transaction for use by a user of the monitoring application.

3. A computer program product stored in a computer readable storage medium for monitoring an application operating on a computer system, the computer program product comprising:

first instructions for monitoring an entry point of the application for a transaction to selectively monitor the transaction within a plurality of transactions in the application in order to minimize computational overhead and data recording associated with monitoring all of the plurality of transactions in the application, wherein the entry point is a location in the application where the transaction is recorded by a monitoring application, and wherein each transaction in the plurality of transactions is associated with a corresponding token that includes data that uniquely identifies an associated transaction and contains configuration information required by a probe that monitors an entry point in the application where the associated transaction occurs to determine an appropriate level of data recording for the associated transaction;

second instructions for, responsive to the entry point being reached by the application for the transaction, acquiring a token associated with the transaction, wherein the token is acquired by looking up the transaction in a policy mapper, and wherein the policy mapper maps a monitoring policy to the transaction from a list of monitoring policies;

third instructions for monitoring the transaction according to the monitoring policy of the token associated with the transaction, wherein the monitoring policy contains a host name, a user name, an application name, a transaction name, scheduling information that defines when the transaction is recorded, a threshold that defines an execution time limit for the transaction, and the configuration information that determines the appropriate level of data recording for the transaction, and wherein the monitoring policy of the token determines what specific information is gathered about the transaction, and wherein the transaction includes a plurality of sub-transactions, and wherein each sub-transaction within the plurality of sub-transactions is associated with the monitoring policy of the token;

fourth instructions for collecting the appropriate level of data recording for the transaction defined by the configuration information; and

fifth instructions for sending the collected appropriate level of data recording for the transaction to the monitoring application, wherein the monitoring application records the collected appropriate level of data recording for the transaction for use by a user of the monitoring application.