In New Relic's APM, the Node VMs page provides useful runtime data for troubleshooting performance issues and monitoring the health of your application.
one.newrelic.com > APM & services > (select an app) > Node VMs: When multiple servers are reporting to the same application, the page breaks charts down by server. You can view data for an individual server and obtain additional details by selecting a server from the Servers filter at the top of the page.
To correlate spikes or upward trends in any of these measurements with specific transactions:
- Go to one.newrelic.com > APM & services > (select an app) > Node VMs.
- Select the time period by clicking and dragging within any of the charts.
- Navigate to the Transactions page or any other page.
As you go to other pages, the time picker selection will remain the same.
Here is a summary of the data available on individual Node VMs charts. By using all of the charts together, you can troubleshoot performance issues. For example:
- When the application starts using more objects, memory usage will increase, and garbage collection (GC) will run more frequently. CPU utilization will increase due to time spent in GC.
- Abnormally long synchronous code execution can increase CPU utilization. This will show spikes in the Event loop max CPU time per tick chart.
When multiple Node.js processes on the same server report to the same New Relic application, these charts will show aggregated data. This is because each worker process in a cluster has its own separate Node.js runtime and collects separate data.
Sum across all workers
The following charts show a sum across all workers:
Average from all workers
The following charts show an average from all workers:
Max across all workers
The following charts show max across all workers: