This check monitors a Container Runtime Interface
CRI is a core agent 6 check and thus need to be configured in both in
datadog.yaml and with
datadog.yaml you will need to configure your
cri_socket_path for the agent to query your current CRI (you can also configure default timeouts) and in
cri.d/conf.yaml you can configure the check instance settings such as
collect_disk if your CRI (such as
containerd) reports disk usage metrics.
Note that if you’re using the agent in a container, setting
DD_CRI_SOCKET_PATH environment variable will automatically enable the
CRI check with the default configuration.
cri.d/conf.yaml file, in the
conf.d/ folder at the root of your
Agent’s configuration directory to start collecting your crio performance data.
See the sample cri.d/conf.yaml for all available configuration options.
[Restart the Agent]
Run the Agent’s
status subcommand and look for
cri under the Checks section.
|The amount of working set memory in bytes
shown as byte
|Cumulative CPU usage (sum across all cores) since object creation
shown as nanocore
|Represents the bytes used for images on the filesystem
shown as byte
|Represents the inodes used by the images
shown as inode
CRI does not include service checks.
CRI does not include any events.
Need help? Contact Datadog support.
Mistake in the docs? Feel free to contribute!