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, for example, suffering from slow database performance.
Before you install New Relic's Node.js agent, make sure your application meets these system requirements.
New Relic recommends using the latest LTS version of Node.js for best performance, currently v6.x.
New Relic's Node.js agent is tested on and supports versions 4 and later of Node.js (including the latest version, 7.x). Other supported versions are 0.8, 0.10* and 0.12. Unstable versions of Node.js are not supported.
* Node.js version 0.10.34 is not supported.
If you are using a supported framework with default routers, New Relic's Node.js agent can read these frameworks' route names as is. However, if you want more specific names than are provided by your framework, you may want to use one or more of the tools New Relic provides. For more information, see Node.js transaction naming API.
|Security requirements||As a standard security measure for data collection, your app server must support SHA-2 (256-bit). SHA-1 is not supported.|
Extend your instrumentation
After installing the Node.js agent, extend your instrumentation:
- 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.
- Page load 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 page load timing: If you encounter problems with page load timing, see these additional tips for Node.js.
For more help
Additional documentation resources include: