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, comprising:
modifying an object with a callback wrapper by agent stored in memory;
receiving, by the agent, sampled call stack data associated with the callback wrapper by the agent, the sampled call stack data including a unique identification for each request in a business transaction; and
reporting the sampled call stack data to a remote server, the remote server reporting data associated with each request instance of the business transaction based on the sampled call stack data.
2. The method of claim 1 , wherein modifying the object includes placing the callback wrapper around the object that includes a callback object associated with a request.
3. The method of claim 2 , wherein the callback wrapper includes a globally unique name, the unique identification including the unique name.
4. The method of claim 2 , wherein the callback wrapper is retrieved from a pool of callback wrappers having unique names.
5. The method of claim 1 , further comprising associating the unique identification with a business transaction request instance by the agent, the reported sampled call stack data including the associated business transaction request instance.
6. The method of claim 1 , wherein the remote server reports a hierarchical call graph of the business transaction and requests called as part of the business transaction.
7. The method of claim 1 , wherein modifying the object includes modifying a listen method within a create server created via an application program interface of a programming framework.
8. The method of claim 1 , wherein the object is part of a platform built on Java script.
9. The method of claim 1 , wherein the object is executed on a NodeJS platform.
10. The method of claim 1 , further comprising: processing a request by modified object; and
providing a call stack with the unique identification.
11. 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 application, the method comprising:
modifying an object with a callback wrapper by agent stored in memory;
receiving, by the agent, sampled call stack data associated with the callback wrapper by the agent, the sampled call stack data including a unique identification for each request in a business transaction; and
reporting the sampled call stack data to a remote server, the remote server reporting data associated with each request instance of the business transaction based on the sampled call stack data.
12. The non-transitory computer readable storage medium of claim 11 , wherein modifying the object includes placing the callback wrapper around the object including:
a callback object associated with a request.
13. The non-transitory computer readable storage medium of claim 12 , wherein the callback wrapper includes a globally unique name, the unique identification including the unique name.
14. The non-transitory computer readable storage medium of claim 12 , wherein the callback wrapper is retrieved from a pool of callback wrappers having unique names.
15. The non-transitory computer readable storage medium of claim 11 , further comprising associating the unique identification with a business transaction request instance by the agent, the reported sampled call stack data including the associated business transaction request instance.
16. The non-transitory computer readable storage medium of claim 11 , wherein the remote server reports a hierarchical call graph of the business transaction and requests called as part of the business transaction.
17. The non-transitory computer readable storage medium of claim 11 , wherein modifying the object includes modifying a listen method within a create server created via an application program interface of a programming framework.
18. The non-transitory computer readable storage medium of claim 11 , wherein the object is part of a platform built on Java script.
19. The non-transitory computer readable storage medium of claim 11 , wherein the object is executed on a NodeJS platform.
20. The non-transitory computer readable storage medium of claim 11 , further comprising:
processing a request by modified object; and
providing a call stack with the unique identification.
21. A system for monitoring an application, comprising: a processor;
a memory; and
one or more modules stored in memory and executable by a processor to modify an object with a callback wrapper by an agent stored in memory, receive, by the agent, sampled call stack data associated with the callback wrapper by the agent, the sampled call stack data including a unique identification for each request in a business transaction, and report the sampled call stack data to a remote server, the remote server reporting data associated with each request instance of PA the business transaction based on the sampled call stack data.
22. The system of claim 21 , wherein the one or more modules are further executable to place the callback wrapper around the object that includes a callback object associated with a request.
23. The system of claim 22 , wherein the callback wrapper includes a globally unique name, the unique identification including the unique name.
24. The system of claim 22 , wherein the callback wrapper is retrieved from a pool of callback wrappers having unique names.
25. The system of claim 21 , wherein the one or more modules are further executable to associate the unique identification with a business transaction request instance by the agent, the reported sampled call stack data including the associated business transaction request instance.
26. The system of claim 21 , wherein the remote server reports a hierarchical call graph of the business transaction and requests called as part of the business transaction.
27. The system of claim 21 , wherein the one or more modules are further executable to modify a listen method within a create server created via an application program interface of a programming framework.
28. The system of claim 21 , wherein the object is part of a platform built on Java script.
29. The system of claim 21 , wherein the object is executed on a NodeJS platform.
30. The system of claim 21 , wherein the one or more modules are further executable to process a request by modified object and provide a call stack with the unique identification.