Aysnchronous Custom Exit Points

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.

What is claimed is: 
     
         1 . A method for monitoring an asynchronous transaction, comprising:
 detecting an asynchronous method call within an application by an agent executing on a server;   monitoring a task object associated with the method call, the task object creation initiated by the asynchronous method call; and   correlating asynchronous method call data with a distributed business transaction performed at least in part on the server.   
     
     
         2 . The method of  claim 1 , wherein tracking includes performing byte code instrumentation on a called asynchronous method. 
     
     
         3 . The method of  claim 1 , wherein instrumenting includes injecting intermediate language and a map into a .NET framework. 
     
     
         4 . The method of  claim 1 , wherein tracking includes performing byte code instrumentation on a task object associated with the asynchronous method. 
     
     
         5 . The method of  claim 1 , further comprising:
 receiving a selection of a back-end calling method to monitor; and   automatically identifying the selected method as asynchronous.   
     
     
         6 . The method of  claim 1 , further comprising reporting performance of a distributed business transaction that includes a call to the asynchronous method. 
     
     
         7 . The method of  claim 1 , wherein the framework is a .NET framework. 
     
     
         8 . 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:
 detecting an asynchronous method call within an application by an agent executing on a server;   monitoring a task object associated with the method call, the task object creation initiated by the asynchronous method call; and   correlating asynchronous method call data with a distributed business transaction performed at least in part on the server.   
     
     
         9 . The non-transitory computer readable storage medium of  claim 7 , wherein tracking includes performing byte code instrumentation on a called asynchronous method. 
     
     
         10 . The non-transitory computer readable storage medium of  claim 7 , wherein instrumenting includes injecting intermediate language and a map into a .NET framework. 
     
     
         11 . The non-transitory computer readable storage medium of  claim 7 , wherein tracking includes performing byte code instrumentation on a task object associated with the asynchronous method. 
     
     
         12 . The non-transitory computer readable storage medium of  claim 7 , the method further comprising:
 receiving a selection of a back-end calling method to monitor; and   automatically identifying the selected method as asynchronous.   
     
     
         13 . The non-transitory computer readable storage medium of  claim 7 , the method further comprising reporting performance of a distributed business transaction that includes a call to the asynchronous method. 
     
     
         14 . The non-transitory computer readable storage medium of  claim 7 , wherein the framework is a .NET framework. 
     
     
         15 . 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 detect an asynchronous method call within an application by an agent executing on a server, monitor a task object associated with the method call, the task object creation initiated by the asynchronous method call, and correlate asynchronous method call data with a distributed business transaction performed at least in part on the server.   
     
     
         16 . The system of  claim 15 , wherein tracking includes performing byte code instrumentation on a called asynchronous method. 
     
     
         17 . The system of  claim 15 , wherein instrumenting includes injecting intermediate language and a map into a .NET framework. 
     
     
         18 . The system of  claim 15 , wherein tracking includes performing byte code instrumentation on a task object associated with the asynchronous method. 
     
     
         19 . The system of  claim 15 , the one or more modules further executable to receive a selection of a back-end calling method to monitor and automatically identify the selected method as asynchronous. 
     
     
         20 . The system of  claim 15 , the one or more modules further executable to report performance of a distributed business transaction that includes a call to the asynchronous method. 
     
     
         21 . The system of  claim 15 , wherein the framework is a .NET framework.