Monitoring of Node.JS Applications
First Claim
1. A method for monitoring a business transaction, comprising:
- detecting a workflow function on an application server;
setting a context associated with the workflow function;
monitoring the workflow on the application server associated with the workflow function; and
storing performance data associated with the context.
3 Assignments
0 Petitions
Accused Products
Abstract
A system creates and monitors virtual threads within a node.js application. Callbacks executing within an event loop for a node.js system are identified and may be traced. The callbacks are associated with a context, and resources associated with execution flow during each context may be identified. Callback registrations, callback calls, and callback completion messages may each be detected and recorded. Each registration, call, and completion message is associated with a virtual thread or other transaction identifier. The timing information for each virtual thread and other resource usage for each context may then be identified, stitched together for distributed transactions and reported to a user to provide more detail for node.js application processing.
-
Citations
27 Claims
-
1. A method for monitoring a business transaction, comprising:
-
detecting a workflow function on an application server; setting a context associated with the workflow function; monitoring the workflow on the application server associated with the workflow function; and storing performance data associated with the context.
-
-
2. The method of 1, wherein the workflow function includes a callback registration.
-
3. The method of 2, wherein the workflow function is detected by intercepting the callback registration.
-
4. The method of 1, wherein the workflow function is performed by a node.js application.
-
5. The method of 1, further comprising creating a transaction identifier for the workflow function
-
6. The method of 1, further comprising reporting event information to a tracer module.
-
7. The method of 6, wherein the event information is reported upon detecting a callback call.
-
8. The method of 6, wherein the event information is reported upon detecting a callback completion.
-
9. The method of 1, further comprising:
-
accessing performance data associated with a plurality of contexts; and processing the performance data to determine performance of a node.js application handling one or more workflow functions.
-
-
10. 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 a business transaction, the method comprising:
-
detecting a workflow function on an application server; setting a context associated with the workflow function; monitoring the workflow on the application server associated with the workflow function; and storing performance data associated with the context.
-
-
11. The non-transitory computer readable storage medium of 10, wherein the workflow function includes a callback registration.
-
12. The non-transitory computer readable storage medium of 11, wherein the workflow function is detected by intercepting the callback registration.
-
13. The non-transitory computer readable storage medium of 10, wherein the workflow function is performed by a node.js application.
-
14. The non-transitory computer readable storage medium of 10, further comprising creating a transaction identifier for the workflow function
-
15. The non-transitory computer readable storage medium of 10, further comprising reporting event information to a tracer module.
-
16. The non-transitory computer readable storage medium of 15, wherein the event information is reported upon detecting a callback call.
-
17. The non-transitory computer readable storage medium of 15, wherein the event information is reported upon detecting a callback completion.
-
18. The non-transitory computer readable storage medium of 1, further comprising:
-
accessing performance data associated with a plurality of contexts; and processing the performance data to determine performance of a node.js application handling one or more workflow functions.
-
-
19. A system for monitoring a business transaction, comprising:
-
an application server including one or more processors and memory; and one or more modules stored in memory and executable by at least one of the one or more processors to detect a workflow function on an application server, set a context associated with the workflow function, monitor the workflow on the application server associated with the workflow function, and store performance data associated with the context.
-
-
20. The system of 19, wherein the workflow function includes a callback registration.
-
21. The system of 20, wherein the workflow function is detected by intercepting the callback registration.
-
22. The system of 19, wherein the workflow function is performed by a node.js application.
-
23. The system of 19, the one or more modules further executable to create a transaction identifier for the workflow function
-
24. The system of 19, the one or more modules further executable to report event information to a tracer module.
-
25. The system of 24, wherein the event information is reported upon detecting a callback call.
-
26. The system of 24, wherein the event information is reported upon detecting a callback completion.
-
27. The system of 19, the one or more modules further executable to:
-
access performance data associated with a plurality of contexts; and process the performance data to determine performance of a node.js application handling one or more workflow functions.
-
Specification