Before installing our infrastructure agent, make sure your system meets the requirements.
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)
The infrastructure agent supports these operating systems:
|Operating system||Supported by the infrastructure agent|
|Amazon Linux||All versions|
|CentOS||Version 6 or higher|
|Debian||Version 8 ("Jessie") or higher|
|Kubernetes||Tested with versions 1.10 to 1.16|
|Red Hat Enterprise Linux (RHEL)||Version 6 or higher|
|SUSE Linux Enterprise Server (SLES)||Versions 11.4, 12|
|Ubuntu||LTS versions 14.04.x, 16.04.x, and 18.04.x|
|Windows Server||2012, 2016, and 2019, and their service packs|
Operating systems are not supported beyond end-of-life.
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.
localhost are not reported: it's a default name and inherently non-unique.
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.
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.
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: