CRI is a core Datadog Agent check that needs to be configured in the datadog.yaml with the cri.d/conf.yaml.
In datadog.yaml, configure your cri_socket_path for the Agent to query your current CRI (you can also configure default timeouts). In cri.d/conf.yaml, configure the check instance settings such as collect_disk if your CRI (such as containerd) reports disk usage metrics.
Note: If you’re using the Agent in a container, set the DD_CRI_SOCKET_PATH environment variable to automatically enable the CRI check with the default configuration.
Installation on containers
If you are using the Agent in a container, setting the DD_CRI_SOCKET_PATH environment variable to the CRI socket automatically enables the CRI integration with the default configuration.
For example, to install the integration on Kubernetes, edit your daemonset to mount the CRI socket from the host node to the Agent container and set the DD_CRI_SOCKET_PATH env var to the daemonset mountPath:
Note: The /var/run directory must be mounted from the host to run the integration without issues.
Configuration
Edit the 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.