Agent Check: CRI

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.

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:

apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: datadog-agent
spec:
  template:
    spec:
      containers:
        - name: datadog-agent
          # ...
          env:
            - name: DD_CRI_SOCKET_PATH
              value: /var/run/crio/crio.sock
          volumeMounts:
            - name: crisocket
              mountPath: /var/run/crio/crio.sock
            - mountPath: /host/var/run
              name: var-run
              readOnly: true
          volumes:
            - hostPath:
                path: /var/run/crio/crio.sock
              name: crisocket
            - hostPath:
                path: /var/run
              name: var-run

Note: The /var/run directory must be mounted from the host to run the integration without issues.

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

Validation

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

Data Collected

Metrics

CRI collect metrics about the resource usage of your containers running through the CRI.

CPU and memory metrics are collected out of the box and you can additionally collect some disk metrics if they are supported by your CRI (CRI-O doesn't support them for now)

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

Service Checks

CRI does not include service checks.

Events

CRI does not include any events.

Troubleshooting

Need help? Contact Datadog support.