Application monitoring of related activities across multiple threads
View Patent ↗Embodiments provide systems, methods, and computer program products for monitoring application performance in multithreaded environments. Monitoring data may be inserted into data structures that propagate and persist between threads involved in a processing event. Data related to specific methods executing on each thread may be output to a trace file. The trace file may be analyzed for application performance by associating the threads that contain the same tracking data from the propagated data structure.
1. A method for monitoring performance of a thread processing a transaction, comprising:
determining, at a processing server, whether the thread is a parent thread or a child thread based on monitoring data in a call context of the thread;
inserting, by the processing server, an identifier into the call context when the thread is the parent thread that lacks an existing identifier, and allowing the thread to inherit the identifier from an active parent thread when the thread is the child thread; and
recording, to a trace file, tracked data comprising the identifier and relating to a method called by the thread while processing the transaction.
2. The method of claim 1 , further comprising:
receiving, at the processing server, a request from a user client to process the transaction;
initiating, at the processing server, the thread to process the transaction; and
outputting the trace file to a data warehouse for performance analysis.
3. The method of claim 1 , wherein the determining comprises:
interrogating the call context of the thread;
identifying the thread as the parent thread when the call context lacks the monitoring data;
identifying the thread as the parent thread when the call context includes the monitoring data comprising the existing identifier that equals a stored identifier for the thread; and
identifying the thread as the child thread when the call context includes the monitoring data comprising the existing identifier that does not equal the stored identifier for the thread.
4. The method of claim 1 , further comprising:
allocating a data structure in the processing server when the thread has not been detected previously by the processing server.
5. The method of claim 1 , wherein the recording comprises:
instrumenting application code utilized in processing the transaction; and
recording transaction data from the method within the instrumented application code as the tracked data.
6. The method of claim 5 , wherein the instrumenting comprises:
selecting the method for monitoring based on activities pre-designated as important for performance monitoring.
7. The method of claim 1 , wherein the identifier comprises a thread identifier and a transaction identifier.
8. A system for application performance monitoring in a processing server, comprising:
a processor configured to initiate a thread to process a transaction;
a monitoring module configured to:
determine whether the thread is a parent thread or a child thread based on monitoring data in a call context of the thread; and
insert an identifier into the call context when the thread is the parent thread that lacks an existing identifier, and allow the thread to inherit the identifier from an active parent thread when the thread is the child thread;
wherein the monitoring module is further configured to record, to a trace file, tracked data comprising the identifier and relating to a method called by the thread while processing the transaction.
9. The system of claim 8 , further comprising a transceiver configured to:
receive a request from a user client to process the transaction; and
output the trace file to a data warehouse for performance analysis.
10. The system of claim 8 , wherein the monitoring module is further configured to:
interrogate the call context of the thread;
identify the thread as the parent thread when the call context lacks the monitoring data;
identify the thread as the parent thread when the call context includes the monitoring data comprising the existing identifier that equals a stored identifier for the thread; and
identify the thread as the child thread when the call context includes the monitoring data comprising the existing identifier that does not equal the stored identifier for the thread.
11. The system of claim 8 , further comprising:
a memory, wherein the monitoring module is further configured to allocate a data structure in the memory when the thread has not been detected previously by the monitoring module.
12. The system of claim 8 , further comprising:
an instrumenting module configured to instrument application code utilized in processing the transaction;
wherein the monitoring module is further configured to record transaction data from the method within the instrumented application code to the trace file as the tracked data.
13. The system of claim 12 , wherein the instrumenting module is further configured to select the method for monitoring based on activities pre-designated as important for performance monitoring.
14. The system of claim 8 , wherein the identifier comprises a thread identifier and a transaction identifier.
15. A non-transitory computer-readable storage medium having control logic recorded thereon that, when executed by a processor, causes the processor to perform a method for monitoring performance of a thread processing a transaction in a processing server, the method comprising:
determining whether the thread is a parent thread or a child thread based on monitoring data in a call context of the thread;
inserting an identifier into the call context when the thread is the parent thread that lacks an existing identifier, and allowing the thread to inherit the identifier from an active parent thread when the thread is the child thread; and
recording, to a trace file, tracked data comprising the identifier and relating to a method called by the thread while processing the transaction.
16. The non-transitory computer-readable medium of claim 15 , further comprising:
receiving a request from a user client to process the transaction;
initiating the thread to process the transaction; and
outputting the trace file to a data warehouse for performance analysis.
17. The non-transitory computer-readable medium of claim 15 , wherein the determining comprises:
interrogating the call context of the thread;
identifying the thread as the parent thread when the call context lacks monitoring data;
identifying the thread as the parent thread when the call context includes the monitoring data comprising the existing identifier that equals a stored identifier for the thread; and
identifying the thread as the child thread when the call context includes the monitoring data comprising the existing identifier that does not equal the stored identifier for the thread.
18. The non-transitory computer-readable medium of claim 15 , further comprising:
allocating a data structure in the processing server when the processing server has not previously detected the thread.
19. The non-transitory computer-readable medium of claim 15 , wherein the recording comprises:
instrumenting application code utilized in processing the transaction; and
recording transaction data from the method within the instrumented application code as the tracked data.
20. The non-transitory computer-readable medium of claim 15 , wherein the instrumenting comprises:
selecting the method for monitoring based on activities pre-designated as important for performance monitoring.