Before installing our infrastructure agent, make sure your system and any on-host integrations you configure meet the requirements.
Processor architectures
The infrastructure agent supports only x86 processor architectures:
- Linux: 64-bit architecture (also requires 64-bit package manager and dependencies)
- Windows: both 32 and 64-bit architectures
- ARM: AWS Graviton 2 processor (using the tarball setup instructions). Support is limited to infrastructure monitoring. Integrations, such as log forwarding, may not work as expected.
Operating systems
The infrastructure agent supports these operating systems:
Operating system | Supported by the infrastructure agent |
|---|---|
All versions | |
Version 7 or higher | |
Version 8 ("Jessie") or higher | |
Docker 1.12 | |
Tested with versions 1.10 to 1.16 | |
Version 6 or higher | |
Versions 11.4, 12.1, 12.2, 12.3, and 12.4 | |
LTS versions 14.04.x, 16.04.x, 18.04.x, 20.04.x | |
Windows Server 2012, 2016, and 2019, and their service packs. Windows 10 (only the infrastructure agent is supported). |
Important
Operating systems are not supported beyond end-of-life.
Tip
You can 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_name setting to override the default hostname.
Important
Servers named localhost are not reported: it's 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.
Libraries
For agent versions 1.1.19 or higher, you need the libcap library in order to install Infrastructure. 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:
For more help
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.