This Check monitors the Container Runtime Containerd.

Containerd is a core Agent 6 check and thus needs to be configured in both in datadog.yaml and with containerd.d/conf.yaml.

In datadog.yaml, configure your cri_socket_path for the Agent to query Containerd. In containerd.d/conf.yaml, configure the Check instance settings (such as filters) for the events.

Note: If you are using the Agent in a container, setting the DD_CRI_SOCKET_PATH environment variable automatically enables the Containerd Check with the default configuration.

1. Edit the containerd.d/conf.yaml file, in the conf.d/ folder at the root of your Agent's configuration directory to start collecting your Containerd performance data. See the sample containerd.d/conf.yaml for all available configuration options.

2. Restart the Agent

Run the Agent's status subcommand and look for containerd under the Checks section.

Containerd collects metrics about the resource usage of your containers.

CPU, memory, block I/O, or huge page table metrics are collected out of the box. Additionally, you can also collect some disk metrics.

See metadata.csv for a list of metrics provided by this Integration.

Containerd includes a Service Check containerd.health to notify on the health of the connection to the Containerd Socket.

The Containerd Check can collect events. Use filters to select the relevant events. Refer to the sample containerd.d/conf.yaml to have more details.

Need help? Contact Datadog support.