Host Requirements for Agent Installation

Sysdig agents can be installed on a wide array of Linux hosts. Check your environment to ensure it meets the minimum supported platform, operating system, runtime, and orchestration requirements and uses the appropriate installation instructions.

Versioning Scheme

The versioning scheme for agent releases has been updated with version 9.5.0. Previous versions used the format, <version number><hotfix> such as, 0.94.0.

Sysdig is aligning version numbers to the rest of the product. The new version number reflects the maturity of the agent software over the last several years. Starting v9.5.0, all agent versions are numbered as Major.minor.hotfix

We encourage users to be on the latest version of the agent. Starting with v9.6.0, we support n-3 versions backbased on the minor number. For example, if the release is v9.6.0, we will support n-3 versions back, for example, to 9.3.0. The old version scheme is 0.93.0.

Agent Installation Requirements

Cloud Platform or Private Data Center

Cloud Platforms Supported

  • AWS AWS Elastic Kubernetes Service (EKS), Elastic Cloud Compute (EC2), AWS Elastic Container Service (ECS) on AWS Cloud or AWS Outpost

  • Google Cloud Provider (GCP) and Google Kubernetes Engine (GKE).

  • Microsoft Azure and Microsoft Azure Container Service (AKS)

  • IBM: Including IBM Cloud Kubernetes Service (IKS)

Private Data Center

See the Supported Linux Distributions table, below.

Container Runtimes

The agent supports the detection of Docker, RKT, LXC, containerd, CRI-O, and Mesos containers.

Prerequisites for CRI-O Environments

Agent artifacts are stored on the Docker registry. In CRI-O and Kubernetes environments, Docker is not a specified registry by default. In order to prevent image pull failure for Sysdig agent installations in CRI-O environments, add docker.ioto the CRI-O configuration file:

  • Edit /etc/crio/crio.conf.

  • Add registries = [""] to the crio.conf file.

    For example:

    # registries is used to specify a comma separated list of registries to be used
    # when pulling an unqualified image (e.g. fedora:rawhide).
    registries = [
  • Restart CRI-O.

Prerequisites for Podman Environments

Sysdig agent supports running as a Podman container.

  • Enable Podman API service for all the users.

    The agent will not able to collect Podman-managed container metadata, such as the container name, if the API service is not enabled.

  • Secure rules and policies that depend on container metadata other than the container ID will not work.

  • Pausing and terminating containers will not work because Policy actions for Podman are not supported.

  • The containers started as a non-root user will have the podman_owner_uid label associated with it if the API service is enabled for that user. The value of podman_owner_uid will be the numeric user ID corresponding to the user that started the container.

Supported Container Registries


    For example, to pull the latest agent container from

    docker pull
  • Docker Hub

    For example, to pull the latest agent container from Docker Hub:

    docker pull sysdig/agent

Supported Linux Distributions

Private Data Center





Core set of distributions:

  • Debian 6.0+

  • Ubuntu 10.04+

  • CentOS 6+

  • RHEL 6+

  • Fedora 13+

  • Linux Mint 9+

  • Oracle 6.0+ (UEK kernels R3+, all RHCK kernels)

  • Amazon AMI

    (any version available from the AWS Marketplace) and

    Amazon Linux 2


  • Core set

Core set


Core set

Orchestrator: Yes/No

  • If NO orchestrator is used, follow the installation instructions for Agent Install: Non-Orchestrated .

  • If you ARE using an orchestrator what kind are you using?

Supported Open-Source Orchestrators

KubernetesMesos/MarathonDocker Swarm
Supported versions1.9+Docker 1.12+
Use Orchestrator to install agents?Agent Install: KubernetesAgent Install: Mesos/MarathonAgent Install: Non-Orchestrated

Supported Container Platforms




Azure CS

Docker Datacenter


Special installation instructions?

Agent Install: Kubernetes

(with OpenShift options)

Agent Install: Kubernetes

(with GKE options)

Agent Install: Non-Orchestrated

(+ AWS Integration instructions)

Agent Install: Non-Orchestrated

No special instructions

Agent Install: Non-Orchestrated

No special instructions

Agent Install: Non-Orchestrated

No special instructions

Supported Java Versions and Vendors

The Sysdig agent supports only:

Java versions: 7 and above

Vendors: Oracle, OpenJDK

For Java-based applications (Cassandra, Elasticsearch, Kafka, Tomcat, Zookeeper and etc.), the Sysdig agent requires the Java runtime environment (JRE) to be installed to poll for metrics (beans).

If the Docker-container-based Sysdig agent is installed, the JRE is installed alongside the agent binaries and no further dependencies exist. However, if you are installing the service-based agent (non-container) and you do not see the JVM/JMX metrics reporting, your host may not have the JRE installed or it may not be installed in the expected location: usr/bin/java

Resource Limits

The resource requirements of the agent are subjective to the size and load of the host— more activity equates to more resources required. At a minimum, the agent requires 2% of the total CPU and 512MiB of memory.

It is typical to see between 5-20KiB/s of bandwidth consumed—different variables can increase the throughput required such as the number of metrics, events, Kubernetes objects, and which products and features are enabled. When a Sysdig Capture is being collected, you can expect to see a spike in bandwidth while the capture file is being ingested.

We do not recommend placing bandwidth shaping or caps on the agent to ensure data can be sent to our collection service.

Supported Web Browsers

Sysdig supports, tests, and verifies the latest versions of Chrome and Firefox.

Other browsers may also work, but are not tested in the same way.

Additional Requirements

Access key

The installation of the Sysdig agent requires an access key. This key and the agent installation instructions are presented to you after activating your account and using a web-based wizard upon initial login.

The same information can also be found in the Settings > Agent Installation menu of the web interface after logging in. See Agent Installation: Overview and Key for details.

Network connection

A Sysdig agent (containerized or native) is installed into each host being monitored and will need to be able to connect to the Sysdig Monitor backend servers to report host metrics. The agent must be able to reach the Sysdig Collector addresses. For example, for US East, it is ‘’ (via multiple IPs) over port tcp/6443 . See Sysdig Collector Ports for supported ports for other regions.

The agent supports the HTTP proxy for communicating with Sysdig backend components. For more information, see Enable HTTP Proxy for Agents.


Tagging your hosts is highly recommended. Tags allow you to sort nodes of your infrastructure into custom groups in Sysdig Monitor.

Replace the [TAGS] parameter in the configuration file with a comma-separated list in the form of TAG_NAME:TAG_VALUE. For example, role:webserver,location:europe.

See Understanding the Agent Config Files.

TracePoints Support

All supported distribution released kernels have this support but if creating a custom kernel, it must support the following options:



See Also

Kernel Header Troubleshooting

Last modified September 15, 2021: Update generated docs (314e99b6)