Install the Node.js agent for Docker

You can use our Node.js agent to instrument Node.js applications deployed in Docker containers. This document explains how to build, configure, and deploy your Dockerized Node.js application that you've instrumented with New Relic.

If you need general help with the Node.js agent installation, see our main installation instructions.

Instrument your container

注意

Don't include your license key in your Dockerfile or Docker image. For more information, see our documentation on license key security.

By making a few configuration changes and adding New Relic environment variables to your existing Dockerfile, you can instrument your Dockerized app with our Node.js agent.

Add newrelic to your package.json:
```
"newrelic": "latest",
```
You can update the value latest to install a specific version, or use any of the other options provided by the package.json format. Check the Node.js agent release notes for information about past agent versions.
Inject the agent in your node start command to instrument your application. Your container setup may allow you to edit the ENTRYPOINT to include newrelic module first with the Node.js -r/--require flag when the node command is invoked. If your Dockerfile contains any of these start commands, you can change them this way:
- Change node YOUR_PROGRAM.js to node -r newrelic YOUR_PROGRAM.js
- Change ENTRYPOINT ['node', 'YOUR_PROGRAM.js'] to ENTRYPOINT ['node', '-r', 'newrelic', 'YOUR_PROGRAM.js']
- Change CMD ['node', 'YOUR_PROGRAM.js'] to CMD ['node', '-r', 'newrelic', 'YOUR_PROGRAM.js']
- If you have an npm script to run your program such as npm start, you can programmatically modify this script by running npm pkg set scripts.start="node -r newrelic your-program.js".
- If you can't control how your program runs, you can load the newrelic module before any other module in your program by adding require('newrelic') to the top of your entry file.
Build your Docker image the way you normally do.
To run your Docker app with the agent enabled, add your and app name to your docker run command as environment variables:
bash
```
$docker run -e NEW_RELIC_LICENSE_KEY=YOUR_LICENSE_KEY \
>        -e NEW_RELIC_APP_NAME="YOUR_APP_NAME" \
>        YOUR_IMAGE_NAME:latest
```

このドキュメントはインストールの役に立ちましたか？

Other configuration options

重要

If your Node.js agent is older than v7.2.0 you will need to add the environment variable NEW_RELIC_NO_CONFIG_FILE=true to your Dockerfile so the agent can run without a configuration file. More information on our configuration settings and order of precedence can be found here.

If your Node.js agent is older than v8.3.0 and you want to use distributed tracing, you'll need to enable it by setting the environment variable NEW_RELIC_DISTRIBUTED_TRACING_ENABLED to true.

In addition to setting your application name or license key, you can set other configuration options by starting your container with the -e option. You can also:

Enable a feature flag using its environment variable (NEW_RELIC_NAME_OF_FEATURE_FLAG_ENABLED), as in this snippet below, replacing NAME_OF_FEATURE_FLAG with the capitalized name of the feature flag:

bash

$docker run -e NEW_RELIC_LICENSE_KEY=YOUR_LICENSE_KEY \
>        -e NEW_RELIC_APP_NAME="YOUR_APP_NAME" \
>        -e NEW_RELIC_NAME_OF_FEATURE_FLAG_ENABLED=true \
>        YOUR_IMAGE_NAME:latest

Set configuration options in your Dockerfile using ENV directives:

ENV NEW_RELIC_NAME_OF_FEATURE_FLAG_ENABLED=true \
    NEW_RELIC_LOG=stdout
    # etc.

Instrument your container .css-21sua1{background:none;border:none;width:0;padding:0;}

注意

このドキュメントはインストールの役に立ちましたか？

Other configuration options

重要

Instrument your container