Pinpoint and solve issues down to the line of code with Node.js monitoring from New Relic. With features like service maps and error analytics, New Relic for Node.js allows you to get the full picture of your app environment.
Many Node application requests are based on raw URLs. New Relic for Node.js is different. New Relic for Node.js assumes it can group requests to your application into transactions instead of HTTP requests. Transactions are defined by giving one or more request paths a name. These names are used to:
- Visualize where your app is spending its time (in transaction breakdowns).
- Identify slow requests.
- Group metrics.
- Show you which portions of your application are suffering from slow database performance.
Before you install New Relic's Node.js agent, review the system requirements.
For installation procedures, see Install the Node.js agent.
Extend your instrumentation
After installing the Node.js agent, extend your instrumentation:
- VM measurements: Install an additional native module to view detailed VM statistics.
- Enable distributed tracing.
- Custom instrumentation: Implement Node.js custom instrumentation.
- Collect custom metrics: Collect custom metrics via an API call.
- Node.js agent API: Use the API to control, customize, or extend the functionality of the Node.js agent.
- Browser timing process: Integrate the Node.js agent with New Relic Browser to gain visibility into end-user activity.
Troubleshoot your installation
If you encounter issues with your Node.js agent, see our troubleshooting information:
- Large memory usage: If you've installed the New Relic Node.js agent and your memory usage has increased, check out these possible solutions.
- Troubleshooting your Node.js installation: Try these steps if you don't see any data, cannot log files, or encounter other installation problems with the Node.js agent.
- Troubleshooting Browser instrumentation: If you encounter problems with Browser data, see these additional tips for Node.js.