Compatibility and requirements for the infrastructure agent

Before installing our infrastructure agent, make sure your system meets the requirements.

Processor architectures

The infrastructure agent supports only x86 processor architectures:

Operating systems

The infrastructure agent supports these operating systems:

Operating system Supported by the infrastructure agent
amazon linux.pngAmazon Linux All versions
centos iconCentOS Version 6 or higher
Debian.pngDebian Version 8 ("Jessie") or higher
Docker iconDocker Docker 1.12
Kubernetes iconKubernetes Tested with versions 1.10 to 1.16
redhat iconRed Hat Enterprise Linux (RHEL) Version 6 or higher
suse iconSUSE Linux Enterprise Server (SLES) Versions 11.4, 12
ubuntu iconUbuntu LTS versions 14.04.x, 16.04.x, and 18.04.x
Windows Server iconWindows Server 2012, 2016, and 2019, and their service packs

Operating systems are not supported beyond end-of-life.

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.

Servers named localhost are not reported: it's a default name and inherently non-unique.

Permissions

The infrastructure agent requires these permissions:

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: