Instrumenting an application with flexible tracers to provide correlation data and metrics

• US 8,423,973 B2
• Filed: 05/08/2009
• Issued: 04/16/2013
• Est. Priority Date: 05/08/2009
• Status: Expired due to Fees

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Saunders, Roger Clive, Goulet, Michael, Singh, Vashistha
• Primary Examiner(s): Alrobaye, Idriss N
• Assistant Examiner(s): MODO, RONALD T
• Application Number:
  US12/437,834
• Publication Number:
  US 20100287541A1
• Time in Patent Office: 1,439 Days
• Field of Search: None
• US Class Current: 717/130
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• 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
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 8/40 Transformation of program code
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

A technique for flexibly adding instrumentation to an application. A file is created which includes a dynamic parameter syntax. The file identifies a trace point in the application, such as a method, and the syntax includes one or more parameters which are evaluated when the method is invoked. The parameters can be used to provide cross-process correlation and/or performance metrics. A client process which calls a server process can include the parameter in a message header according to any desired transport protocol, such as HTTP or JMS. Different application protocols and implementation can be accommodated to track a transaction which executes on different platforms. The dynamic parameter syntax is interpreted as uncompiled code and is designed to be added by the user in the field to augment a package of pre-built instrumentation software after the package has been deployed.

Claims

1. A computer-implemented method for instrumenting an application, comprising:

editing a probe builder file in a software instrumentation product by adding uncompiled instructions to the probe builder file, the probe builder file comprising tracers for an application, and the uncompiled instructions specify one trace point in the application, a parameter to evaluate at the one trace point, and an operator for at least one of number comparison, object comparison, string comparison or Boolean comparison;

using the probe builder file, creating an instrumented application comprising;

compiled code of the application, the compiled code is modified to add the tracers, and the uncompiled instructions, the uncompiled instructions provide a tracer which augments the tracers in the software instrumentation product;

executing the instrumented application;

when the one trace point is invoked in the instrumented application, in a client process of a transaction, interpreting the uncompiled instructions and, in response, providing a value for the parameter by applying the operator to a first value and a second value, the first value is based on an invoked method at the one trace point and the second value is based on an invoked method at another trace point;

providing the parameter in a call from the client process to a server process; and

communicating the parameter to a manager, the manager uses the parameter to correlate the client and server processes as being part of the transaction.

2. The computer-implemented method of claim 1, wherein:

a first agent associated with the client process performs the communicating, and a second agent associated with the server process retrieves the parameter from the call and communicates the parameter to the manager.

3. The computer-implemented method of claim 1, wherein:

the executing the instrumented application comprises interpreting the uncompiled instructions as script instructions.

4. The computer-implemented method of claim 1, wherein:

the parameter comprises an input argument of the invoked method at the one trace point.

5. The computer-implemented method of claim 1, wherein:

the uncompiled instructions comprise a name of a method to be invoked at the one trace point.

6. The computer-implemented method of claim 1, wherein:

the value comprises a return value of the invoked method at the one trace point.

7. The computer-implemented method of claim 1, wherein:

the parameter comprises a name of a class of an object which is invoked at the one trace point.

8. The computer-implemented method of claim 1, wherein:

the parameter comprises a name of a class of an object which is invoked at the one trace point, and a name of a method to be invoked on the class.

9. The computer-implemented method of claim 1, wherein:

the uncompiled instructions comprise a keyword in a Dynamic Parameter Syntax, the keyword signals that an entry for the parameter follows and is to be evaluated when the one trace point is invoked to provide the value for the parameter.

10. The computer-implemented method of claim 1, wherein:

the parameter comprises a reserved string which is substituted with at least one of a name or a namespace associated with the one trace point when the one trace point is invoked.

11. The computer-implemented method of claim 1, wherein:

the parameter is evaluated with an operation name of the invoked method at the one trace point when the one trace point is invoked.

12. The computer-implemented method of claim 1, wherein:

the parameter provides at least one of a class name and a method name of a performance metric.

13. A processor readable storage device comprising processor readable code embodied thereon for programming a processor to perform a method for instrumenting an application, the method comprising:

editing a probe builder file in a software instrumentation product by adding uncompiled instructions to the probe builder file, the probe builder file comprising tracers for an application, and the uncompiled instructions specify one trace point in the application, a parameter to evaluate at the one trace point and an operator for at least one of number comparison, object comparison, string comparison or Boolean comparison;

using the probe builder file, creating an instrumented application comprising;

compiled code of the application, the compiled code is modified to add the tracers, and the uncompiled instructions, the uncompiled instructions provide a tracer which augments the tracers in the software instrumentation product, and the tracers in the software instrumentation product provide a baseline set of instrumentation;

executing the instrumented application;

when the one trace point is invoked in the instrumented application, in a client process of a transaction, interpreting the uncompiled instructions and, in response, providing a value for the parameter by applying the operator to a first value and a second value, the first value is based on an invoked method at the one trace point and the second value is based on an invoked method at another trace point; and

communicating the parameter to a manager, the manager uses the parameter to correlate the client process and an associated server process as being part of the transaction.

14. The processor readable storage device of claim 13, wherein:

the parameter is evaluated with a return value of the invoked method at the one trace point.

15. The processor readable storage device of claim 13, wherein:

the parameter provides at least one of a class name or a method name for a metric of the transaction; and

the manager uses the parameter to report the metric of the transaction.

16. The processor readable storage device of claim 13, wherein:

the parameter is evaluated with an operation name of the invoked method at the one trace point when the one trace point is invoked.