Before installing our infrastructure agent, make sure your system and any on-host integrations you configure meet the requirements. You also need a New Relic account. Sign up for free. No credit card required.
Processor architectures
The infrastructure agent supports these processor architectures:
- Linux: 64-bit for x86 processor architectures (also requires 64-bit package manager and dependencies)
- Windows: 64-bit for x86 processor architectures
- ARM: arm64 architecture including AWS Graviton 2 processor is supported on compatible Linux operating sytems. On-host integrations are also supported (with the exception of the Oracle integration).
- macOS: both 64-bit x86 and Apple silicon.
Operating systems
The infrastructure agent supports these operating systems up to their manufacturer's end-of-life. The agent might still be compatible with older versions, but please refer to the step-by-step instructions for each operating system if the guided installation is no longer available for a specific operating system version.
Operating system | Supported by the infrastructure agent |
|---|---|
All versions | |
CentOS Stream 9 or higher ( CentOS 10 installs via tarball; package manager is work in progress ) | |
AlmaLinux 8 and 9 | |
RockyLinux 8 and 9 | |
Version 11 ("bullseye") or higher | |
Version 7.9 or higher ( RHEL 10 installs via tarball; package manager is a work in progress ) | |
Version 7.9 or higher | |
Versions 12.5, 15.3, 15.4, 15.5, 15.6 | |
LTS versions 16.04.x, 18.04.x, 20.04.x, 22.04.x, 24.04.x | |
Windows Server 2016, 2019, 2022 and 2025. Windows 10 (Microsoft EOL date October 14th 2025), Windows 11. | |
3 most recent major versions. Currently: 13 (Ventura), 14 (Sonoma), 15 (Sequoia) |
You can also monitor Amazon BottleRocket workloads:
- When running EC2 instances, use the containerized agent.
- On EKS, install the Kubernetes integration.
- For ECS clusters, deploy the ECS integration.
Unique hostname
The infrastructure agent uses the hostname to uniquely identify each server. To avoid inaccurate metrics from combining multiple servers under a single hostname, make sure that each monitored server has a unique hostname.
- You can use the optional
display_namesetting to override the default hostname. - Servers named
localhostare not reported because this is a default name and inherently non-unique.
Permissions
The infrastructure agent requires these permissions:
- Linux: By default, the agent runs and installs as root. You can also select privileged or unprivileged run modes.
- Windows: The agent must be installed from an Administrator account and requires Administrator privileges to run.
- macOS: The agent can be installed from any user account.
Libraries
For agent versions 1.1.19 or higher, you need the libcap library in order to install. It's available in the official repositories of your distribution.
Network access
In order to report data to New Relic, our infrastructure agent must have outbound access to certain domains and ports. If your system needs a proxy to connect to these domains, use the proxy setting.
Container software
The infrastructure agent instruments Docker containers when installed on the host server. We support Docker versions 1.12 or higher.
CPU, memory, and disk usage
The infrastructure agent is fairly lightweight. For typical CPU, memory, and disk usage, see our page on agent performance overhead. For more information on supported file systems, see Storage sample attributes.
Configuration management tools
The infrastructure agent can be deployed programmatically using several config management and deploy tools:
Other integrations
If you're installing the Kubernetes integration, make sure that you meet the Kubernetes compatibility and requirements.