Our infrastructure monitoring agent for Linux can be installed using several package managers. You can use our launcher, or follow the instructions in this document to complete a basic installation.
No matter which installation option you choose, make sure you've created a free New Relic account (No credit card required).
The quickest way to get started with our infrastructure monitoring agent is through our guided install.
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.
Installing the agent using tarball files is officially supported only for the AWS Graviton 2 processor.
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.
- Add custom attributes to annotate your infrastructure data.
- Connect your AWS account if your servers are hosted on Amazon EC2.
- Enable log forwarding.
- Add other New Relic infrastructure integrations to collect data from external services.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.