Business transaction resource usage tracking
A system associates resource usage with a particular business transaction. A business transaction may include a PHP request and occur over a distributed system. The distributed application may be monitored. The resource usage by the requests that form the business transaction may be compiled together to determine the resource usage of the business transaction. The resources may include resources used by PHP requests, such as for example memory pool usage, files used, CPU usage, and other resources.
1. A method for monitoring a business transaction and associated resource usage, the method comprising:
receiving, by a server, a plurality of PHP: hypertext preprocessor (PHP) requests;
analyzing, by an agent installed on the server, each PHP request to detect an identifier representing a business transaction associated with each received PHP request;
initiating monitoring of the received PHP requests by the agent, each associated with a corresponding business transaction;
determining resource usage, by the agent, by each PHP request associated with the corresponding business transaction as each PHP request is executed;
stitching together the determined resource usage by all PHP requests, from the received PHP requests, associated with the same business transaction based on the determined identifier for each PHP request; and
reporting the stitched together resource usage by the PHP requests associated with the same business transaction to indicate a total resource usage for the same business transaction.
2. The method of claim 1 , including determining a business transaction associated with each PHP request based on the identifier.
3. The method of claim 1 , wherein determining the resource usage includes determining a memory metric associated with each PHP request.
4. The method of claim 3 , wherein determining the memory metric includes retrieving a ZEND engine memory pool size.
5. The method of claim 1 , wherein determining the resource usage includes determining a processing time associated with the PHP request.
6. The method of claim 1 , including:
reporting the resource usage to an external server; and
determining the total resource usage for the business transaction by the external server.
7. The method of claim 1 , wherein each PHP request is associated with a business transaction by an agent that resides on a server that receives the PHP request.
8. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform operations for monitoring a business transaction, the operations including:
receiving, by a server, a plurality of PHP: hypertext preprocessor (PHP) requests;
analyzing, by an agent installed on the server, each PHP request to detect an identifier representing a business transaction associated with each received PHP request;
initiating monitoring of the received PHP requests by the agent, each associated with a corresponding business transaction;
determining resource usage, by the agent, by each PHP request associated with the corresponding business transaction as each PHP request is executed;
stitching together the determined resource usage by all PHP requests, from the received PHP requests, associated with the same business transaction based on the determined identifier for each PHP request; and
reporting the stitched together resource usage by the PHP requests associated with the same business transaction to indicate a total resource usage for the same business transaction.
9. The non-transitory computer readable storage medium of claim 8 , wherein the operations include determining a business transaction associated with each PHP request based on the identifier.
10. The non-transitory computer readable storage medium of claim 8 , wherein determining the resource usage includes determining a memory metric associated with each PHP request.
11. The non-transitory computer readable storage medium of claim 10 , wherein determining the memory metric includes retrieving a ZEND engine memory pool size.
12. The non-transitory computer readable storage medium of claim 8 , wherein determining the resource usage includes determining a processing time associated with each PHP request.
13. The non-transitory computer readable storage medium of claim 8 , wherein the operations include reporting the resource usage to an external server to be associated with a business transaction by the external server.
14. The non-transitory computer readable storage medium of claim 8 , wherein each PHP request is associated with a business transaction by an agent that resides on a server that receives each PHP request.
15. A system for monitoring a business transaction, the system comprising:
a processor;
a memory; and
one or more modules stored in the memory and executed by the processor to perform operations including:
receive a plurality of PHP: hypertext preprocessor (PHP) requests;
analyze, by an agent installed on the server, each PHP request to detect an identifier representing a business transaction associated with each received PHP request;
initiate monitoring of the received PHP requests by the agent, each associated with a corresponding business transaction;
determine resource usage, by the agent, by each PHP request associated with the corresponding business transaction as each PHP request is executed;
stitch together the determined resource usage by all PHP requests, from the received PHP requests, associated with the same business transaction based on the determined identifier for each PHP request; and
report the stitched together resource usage by the PHP requests associated with the same business transaction to indicate a total resource usage for the same business transaction.
16. The system of claim 15 , wherein the one or more modules are executable to determine a business transaction associated with the request based on the identifier.
17. The system of claim 15 , wherein the one or more modules are executable to determine the resource usage by determining a memory metric associated with each PHP request.
18. The system of claim 17 , wherein the one or more modules are executable to determine the memory metric including retrieve a ZEND engine memory pool size.
19. The system of claim 15 , wherein the one or more modules are executable to determine the resource usage by determining a processing time associated with each PHP request.
20. The system of claim 15 , wherein the one or more modules are executable to report the resource usage to an external server to be associated with a business transaction by the external server.
21. The system of claim 15 , wherein each PHP request is associated with a business transaction by an agent that resides on a server that receives the PHP request.