New announcements for Serverless, Network, RUM, and more from Dash! New announcements from Dash!

CRI-O

Agent Check Agent Check

Supported OS: Linux Mac OS Windows

Overview

This check monitors CRI-O.

Setup

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.

Installation

The integration relies on the --enable-metrics option of CRI-O that is disabled by default, when enabled metrics are exposed at 127.0.0.1:9090/metrics.

Configuration

  1. Edit the crio.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your CRI-O performance data. See the sample crio.d/conf.yaml for all available configuration options.

  2. Restart the Agent

Validation

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

Data Collected

CRI-O collect metrics about the count and latency of operations that are done by the runtime. Datadog-CRI-O integration is also collecting CPU and memory usage of CRI-O golang binary itself.

Metrics

crio.operations.count
(counter)
Counter of CRI-O operations
crio.operations.latency.sum
(gauge)
Sum of CRI-O operations latency
Shown as microsecond
crio.operations.latency.count
(gauge)
Count of CRI-O operations latency
crio.operations.latency.quantile
(gauge)
Quantiles of CRI-O operations latency
crio.cpu.time
(gauge)
Total user and system CPU time spent in seconds
Shown as second
crio.mem.resident
(gauge)
Resident memory size in bytes
Shown as byte
crio.mem.virtual
(gauge)
Virtual memory size in bytes
Shown as byte

Service Checks

CRI-O includes a service check about the reachability of the metrics endpoint.

Events

CRI-O does not include any events.

Troubleshooting

Need help? Contact Datadog support.


Mistake in the docs? Feel free to contribute!