Asynchronous custom exit points
AssigneeAppDynamics, Inc.
InventorsSanjay Nagaraj, Ryan Ericson, Alexander Fedotyev
Life of this patent
Estimating the term…
Abstract
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.
Claims22
1-21. (canceled)
A method for monitoring an asynchronous transaction, comprising:
- receiving, by an agent executing on a serve, a selection of a back-end calling method to monitor;
- determining whether the received selection of the method to monitor is an asynchronous method;
- responsive to the determining, instrumenting the asynchronous method call to monitor;
- responsive to the instrumenting, monitoring, by the agent, asynchronous framework initiated by the instrumented asynchronous method call;
- obtaining asynchronous framework data based on the monitoring;
- and
- correlating the back-end calling method with a distributed business transaction performed at least in part on the server.
A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for monitoring an asynchronous transaction, the method comprising:
- receiving, by an agent executing on a serve, a selection of a back-end calling method to monitor;
- determining whether the received selection of the method to monitor is an asynchronous method;
- responsive to the determining, instrumenting the asynchronous method call to monitor;
- responsive to the instrumenting, monitoring, by the agent, asynchronous framework initiated by the instrumented asynchronous method call;
- obtaining asynchronous framework data based on the monitoring;
- and
- correlating the back-end calling method with a distributed business transaction performed at least in part on the server.
The non-transitory computer readable storage medium of claim 31, wherein the instrumenting includes performing byte code instrumenting.
The non-transitory computer readable storage medium of claim 31, wherein instrumenting includes injecting intermediate language and a map into a .NET framework.
A system for monitoring a business transaction, comprising:
- a processor;
- a memory;
- and
- one or more modules stored in memory and executable by a processor to perform operations including:
- receive, by an agent executing on a serve, a selection of a back-end calling method to monitor;
- determine whether the received selection of the method to monitor is an asynchronous method;
- responsive to the determination, instrument the asynchronous method call to monitor;
- responsive to the instrumenting, monitor, by the agent, asynchronous framework initiated by the instrumented asynchronous method call;
- obtain asynchronous framework data based on the monitoring;
- and
- correlate the back-end calling method with a distributed business transaction performed at least in part on the server.
Dependencies are inferred from the claim text.