Business transaction context for call graph
An application which utilizes a single thread is monitored and context for the individual requests and business transactions operating on that platform are provided. A wrapper is placed is around an object that calls a request. The wrapper renames a request object. Request objects are renamed with a unique name when they are called. When a call stack is sampled, the sampler will retrieve the unique name. Performance data associated with the unique name may be correlated to a business transaction and particular request as metrics are subsequently analyzed. For subsequent reporting, such as call graph reporting, the report or call graph will have requests in the context of a particular business transaction and a particular request instance. This provides more context in reporting of an business application request for frameworks that utilize as single request for multiple threads.
1. A method for monitoring an application that utilizes single threaded execution, the method comprising:
renaming, by an agent on a device in a computer network, a function object with a unique name associated with a wrapper function object, the function object is configured to be called when a request for the function object is received;
receiving, by the agent, the request that includes a business transaction identifier that identifies a business transaction associated with the request;
receiving, by the agent, data including call stack data and performance data associated with the function object renamed with the unique name;
correlating, by the agent, the received data with the business transaction and the request using the unique name and the business transaction identifier; and
reporting, by the agent, the correlated data using a call graph that includes the request in context of the business transaction.
2. The method of claim 1 , wherein renaming the function object includes:
replacing a reference to the function object with the wrapper function object that references the function object using the unique name.
3. The method of claim 1 , including:
detecting the function object; and
replacing information within the detected function object.
4. The method of claim 3 , including:
placing hooks in a listen method of the detected function object to replace a callback;
retrieving the wrapper object from a pool of wrapper objects, wherein each wrapper object includes an associated unique name; and
placing the wrapper object with the associated unique name around the detected function object.
5. The method of claim 1 , including:
responsive to execution of the function object, placing the unique identifier of the wrapper object on a call stack to include the unique identifier in the call stack data.
6. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform operations for monitoring an application that utilizes single threaded execution, the operations including:
renaming a function object with a unique name associated with a wrapper function object, the function object is configured to be called when a request for the function object is received;
receiving the request that includes a business transaction identifier that identifies a business transaction associated with the request;
receiving data including call stack data and performance data associated with the function object renamed with the unique name;
correlating the received data with the business transaction and the request using the unique name and the business transaction identifier; and
reporting the correlated data using a call graph that includes the request in context of the business transaction.
7. The non-transitory computer readable storage medium of claim 6 , wherein the program is executable to rename the function object including:
replacing a reference to the function object with the wrapper function object that references the function object using the unique name.
8. The non-transitory computer readable storage medium of claim 6 , wherein the operations include:
detecting the function object; and
replacing information within the detected function object.
9. The non-transitory computer readable storage medium of claim 8 , wherein the operations include:
placing hooks in a listen method of the detected function object to replace a callback indication;
retrieving the wrapper object from a pool of wrapper objects, wherein each wrapper object includes an associated unique name; and
placing the wrapper object with the associated unique name around the detected function object.
10. The non-transitory computer readable storage medium of claim 6 , wherein the operations include:
responsive to execution of the function object, placing the unique name of the wrapper object on a call stack to include the unique name in the call stack data.
11. A system for monitoring an application, the system comprising:
a memory;
a processor; and
one or more modules stored in memory and executable by the processor to perform operations for monitoring the application that utilizes single threaded execution including:
rename a function object with a unique name associated with a wrapper function object, the function object is configured to be called when a request for the function object is received;
receive the request that includes a business transaction identifier that identifies a business transaction associated with the request;
receive data including call stack data and performance data associated with the function object renamed with the unique name;
correlating the received data with the business transaction and the request using the unique name and the business transaction identifier; and
report the correlated data using a call graph that includes the request in context of the business transaction.
12. The system of claim 11 , wherein the one or more modules is executable to rename the function object including:
replace a reference to the function object with the wrapper function object that references the function object using the unique name.
13. The system of claim 11 , wherein the call graph includes business transaction information and request information in a hierarchical format.
14. The system of claim 11 , wherein the one or more modules are executable to process the request including:
obtain the business transaction identifier from the request; and
associate the business transaction identifier with the unique name from the function object.
15. The system of claim 11 , wherein the one or more modules are executable to include the unique name on a call stack.
16. The system of claim 11 , wherein the one or more modules are executable to replace information in a listen method within the function object called in response to the request.
17. The system of claim 11 , wherein the one or more modules are executable to perform operations including:
detect the function object;
place hooks in a listen method of the detected function object to replace a callback indication;
retrieve a wrapper object from a pool of wrapper objects, wherein each wrapper object includes an associated unique name; and
place the wrapper object with the associated unique name around the detected function object.