The quickest way to get started with our infrastructure monitoring agent is through our guided install. If you're in the EU, try our EU guided install. Either way, you'll need a New Relic account if you don't have one. You can create a one for free, forever.
If guided install doesn't work, you can install the agent manually. Before installing infrastructure, be sure to:
To install infrastructure in Linux, follow these instructions:
Create the configuration file and add your license key:
echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /etc/newrelic-infra.yml
Determine the distribution version number:
Enable New Relic's GPG key:
Add the infrastructure monitoring agent repository:
Refresh the repositories:
newrelic-infrapackage in root (default), privileged user, or unprivileged user mode. For more information on each running mode, see Linux agent running modes.
Once the infrastructure monitoring agent is installed or updated, you can start, stop, or check the agent status.
As of version 1.4.0, the infrastructure monitoring agent package includes the additional
newrelic-infra-ctl binary, which is used to help troubleshoot a running agent. Although this binary is not required to execute the agent, we recommend to add it in your path.
To install the infrastructure monitoring agent with a configuration management tool, see the documentation for:
This is especially useful when you need to adapt the default installation settings to your environment, or to install the infrastructure monitoring agent on distributions that lack the
newrelic-infra package in their repositories.
Note that custom installation of the infrastructure agent using tarball files is not officially supported.
Follow standard procedures to update the infrastructure monitoring agent.
If you are using
sudo to install or update the agent, use the
-E argument to allow bypassing the environment variables, or specify the
NRIA_MODE environment variable just after
sudo -E YOUR_PACKAGE_MANAGER_UPDATE_COMMAND
The hostname for your server cannot be
localhost. Data will not be reported for servers with that name. Make sure the host name uses a unique name.