The Service Map for APM is here!

CRI

Agent Check Agent Check

Supported OS: Linux

Overview

This check monitors a Container Runtime Interface

Setup

Installation

CRI is a core agent 6 check and thus need to be configured in both in datadog.yaml and with cri.d/conf.yaml.

In 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.

Configuration

  1. 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.

  2. [Restart the Agent][3]

Validation

Run the Agent’s status subcommand and look for cri under the Checks section.

Data Collected

Metrics

cri.mem.rss
(gauge)
The amount of working set memory in bytes
shown as byte
cri.cpu.usage
(rate)
Cumulative CPU usage (sum across all cores) since object creation
shown as nanocore
cri.disk.used
(gauge)
Represents the bytes used for images on the filesystem
shown as byte
cri.disk.inodes
(gauge)
Represents the inodes used by the images
shown as inode

Service Checks

CRI does not include service checks.

Events

CRI does not include any events.

Troubleshooting

Need help? Contact Datadog Support.


Mistake in the docs? Feel free to contribute!