Cisco Technology, Inc.

Appdynamics, Inc.

Ryan Ericson

Sanjay Nagaraj

Michael Margulis

David Roth

Suraj Puvvada

Amod Gupta

Alexander Fedotyev

In one embodiment, a monitoring process modifies a class definition of an object of a monitored process to include an injected field. The monitoring process may then execute a first interception point of the monitored process, and sets, at the first interception point, the injected field to a given value. Upon executing a second interception point of the monitored process, the monitoring process can then read, at the second interception point, the given value in the injected field, and can use the given value at the second interception point for a corresponding correlation operation between the first interception point and the second interception point.

In-process correlation through class field injection

Application performance data and machine health are collected by a system. The system correlates the two data types to provide context as to how machine health affects the performance of an application. Performance data for an application, for example an application executing as part of a distributed business transaction, and health data for a machine which hosts the application are collected. The performance data and machine health data may be correlated for a particular period of time. The correlation may then be reported to a user. By viewing the correlation, a user may see when machine health was good and bad, and may identify the effects of the machine health on the performance of an application.

Analyzing physical machine impact on business transaction performance

The present technology may monitor an asynchronous transaction based on a custom exit point. Once an asynchronous method to be monitored has been identified, the transition framework may be tracked while executing the asynchronous method call. Within a .NET framework, monitoring may include tracking a task object, continuation method calls at the completion of a method, and tracking the continuation method as it executes other code. The asynchronous method may then be correlated within a business transaction using the returned task object data.

Asynchronous custom exit points

Asynchronous operations associated with a request such as synchronous threads, runnable elements, callable elements, and other invokable objects are tracked to determine the metrics about the request and operations. The present technology tracks the start and end of each asynchronous operation and maintains a counter which tracks the currently executing asynchronous operations. By monitoring the request, the start and end of each asynchronous operation associated with the request, and the number of asynchronous operations currently executing, the present technology may identify the end of a request by identifying when the last asynchronous operation associated with the request ends. In some instances, the present technology identifies the end of a request when a counter which tracks the number of asynchronous operations executing reaches a value of zero after the first asynchronous operation has already begun.

Tracking asynchronous entry points for an application

A system for naming a process being monitored that handles a requesting a framework such as a .NET framework. The process may be implemented by a .NET application framework within an IIS web server. The naming system allows for user readable names which are more than just numbers or indexes. The naming system is configured from a single location rather than from multiple locations, making it much easier to configure, change and update.

Naming of nodes in NET framework

A system monitors asynchronous transactions over a different number of threads by capturing data and tracking transitions in the particular framework. Once an asynchronous method is called, the transition framework may be tracked while executing a asynchronous method call. Within a .NET framework, monitoring may include tracking a task object return, continuation method calls at the completion of a method, and tracking the continuation method as it executes other code. The asynchronous method may then be correlated within a business transaction using the returned task object data.

Growing community of inventors

San Francisco, CA, United States of America

Ryan Ericson