Ca, Inc.

Computer Associates Think, Inc.

Michael Goulet

Stuart Todd Rader

Abhijit Sawant

Venkata Naresh Chippada

Roger Clive Saunders

Vashistha Singh

Todd Rader

William Stewart Robson Thain

Raghuram Doddapaneni

Anand Krishnamurthy

Stewart Thain

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.

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

Technology for monitoring transactions in a computing environment is disclosed. Execution of a transaction by a first application is monitored by a first software entity executing on a first computing device. Performance data that relates to execution of the transaction by a first application is generated. Execution of the transaction by a second application is monitored by a second software entity. The transaction is executed by the second application based on a request from the first application. A determination is made, based on the monitoring, that the first software entity should report the performance data to a third software entity that executes on a second computing device. Based on determining that the first software entity should report the performance data, data is propagated that indicates that the first software entity should report the performance data. The first software entity reports the performance data to the third software entity.

Selective reporting of upstream transaction trace data

Relationships between components in an application and the services they provide are identified, including redundant caller-callee sequences. Specific components of interest are instrumented to obtain data when they execute. Data structures are created which identify the components and their dependencies on one other. To avoid excessive overhead costs, redundant dependencies are identified. A dependency data structure can be provided for each unique dependency. When repeated instances of a dependency are detected, the associated dependency data structure can be augmented with correlation data of the repeated instances, such as transaction identifiers and sequence identifiers. Sequence identifiers identify an order in which a component is called. A flag can be used to force the creation of a new dependency data structure, and a calling component's name can be used instead of a sequence identifier. Agents report the dependency data structures to a manager to provide graph data in a user interface.

Detecting, logging and tracking component dependencies in web service transactions

A monitoring system is used to monitor extended business transactions comprised of asynchronous messages. Each message may be a request or a response of an application transaction request-response pair and may be identified with a unique identifier. The unique identifier may be used to identify two or more asynchronous messages, where each extended business transaction may be associated with one or more unique identifiers to identify messages that comprise the business transaction. The extended business transactions are completed over an extended period of time and implemented over several different machines which may or may not be in communication with each other are monitored. Alerts are generated when messages of the extended business transaction do not satisfy a threshold or other criteria, such as a time period for occurring. A user interface or other mechanism may be used to configure the transactions and provide information regarding the status of the transactions and alerts generated for uncompleted portions of the transaction.

Monitoring asynchronous transactions within service oriented architecture

Growing community of inventors

Newton, MA, United States of America

Michael Goulet