The infrastructure agent is a lightweight executable file that collects data about your hosts. It also forwards data from infrastructure integrations to New Relic, as well as log data for log analytics.
There are multiple ways to install and deploy the infrastructure agent, depending on your setup and needs. Read on to understand how the infrastructure agent works and how to install it.
One agent, many capabilities
Our infrastructure agent collects performance and health data about the system resources and processes of the host where it's enabled (on-premises or virtualized). At the same time, it acts as a forwarder for two types of data: core services metrics, which are collected by on-host integrations, and logs.
Install the infrastructure agent
The infrastructure agent can currently run on many Linux distributions, as well as Windows Server. For more information on where you can run the agent, check the compatibility and requirements page.
The preferred way to install the Linux agent is through the package manager of your distribution. Select your distribution from the list for step-by-step instructions.
To use the links above, you must be logged to your New Relic account.
If you don't have a New Relic account yet, or prefer to follow the procedure manually, see our tutorial. For advanced install needs, you can deploy the agent using our tarball files in assisted or manual mode.
Windows Server and 10
To deploy the agent on a Windows Server host, install it using our MSI installer. For a guided procedure, click the button below and follow the step-by-step instructions:
If you don't have a New Relic account yet, or prefer to follow the procedure manually, see our tutorial. For advanced install needs, you can deploy the agent using our zip files in assisted or manual mode.
Other install scenarios
The infrastructure agent can be deployed programmatically using several config management and deploy tools:
Check the source code
After you've installed the infrastructure agent:
- Learn how to configure the agent or edit the config template.
- Install on-host integrations (for example, for Apache or MySQL).
- Enable log forwarding using the infrastructure agent.
- Learn how to manage the agent.