Install the Node.js agent

To complete a basic Node.js agent installation, you can use our guided installation for an automated install, (choose EU if you're in the EU) or follow the instructions in this document. Either way, you need a New Relic account if you don't already have one. (It's free, forever!)

Our Node.js agent is publicly available on the Node Package Manager (npm) repository as well as on GitHub.

Important

If you're using the agent in a Docker container, install the agent in each container.

To install the Node.js agent:

Create a New Relic account. Don't have one? Sign up for free! No credit card required.
Ensure you meet the system requirements. In particular, make sure you use a supported Node version.
Use the command npm install newrelic --save for each application you want to monitor.
From node_modules/newrelic, copy newrelic.js into the root directory of your app.
Configure agent via the newrelic.js file or via environment variable:
- Customize the license_key setting with your license key.
- Customize the app_name setting with one or more meaningful app names.
Add require('newrelic'); as the first line of your app's main module.

Important

If you are using Babel or a similar transpiler you can safeguard against any issues related to module load order by utilizing the Node command line option '-r' to preload the 'newrelic' module at application startup. For example, if your application's entry point is ./dist/server.js then you would use the require flag like so:

node -r newrelic ./dist/server.js

If you are unable to require('newrelic'); as the first line of your app's main module and you are unable to use the require flag as above (e.g. asynchronously loading api keys from a remote location during application bootstrapping), you may also add stock instrumentation to an already loaded supported module by using newrelic.instrumentLoadedModule:

// module loaded before newrelic 
const expressModule = require('express');

// load the agent
const newrelic = require('newrelic');

// instrument express after the agent has been loaded
newrelic.instrumentLoadedModule(
  'express',    // the module's name, as a string
  expressModule // the module instance
);

Optional: For additional Node.js runtime-level statistics, ensure the @newrelic/native-metrics package is installed.
Generate some traffic, then wait a few minutes for data to appear in the APM UI.

You can further customize your agent behavior via newrelic.js or an environment variable. To keep the agent configuration separate from your app, edit the NEW_RELIC_HOME environmental variable.

View logs for your APM and infrastructure data

You can also bring your logs and application's data together to make troubleshooting easier and faster. With logs in context, you can see log messages related to your errors and traces directly in your app's UI. You can also see logs in context of your infrastructure data, such as Kubernetes clusters. No need to switch to another UI page.

Keep your Node.js agent up-to-date

To ensure that you have the most up-to-date version of New Relic, refer to the Node.js release notes. When applicable, the release notes include a download link with instructions on how to update the Node.js agent.

Troubleshooting

After you update the agent, generate some traffic and wait a few minutes. If no data appears in the New Relic UI, see the troubleshooting procedures.