---
title: CRI-O
description: Track all your CRI-O metrics with Datadog
breadcrumbs: Docs > Integrations > CRI-O
---

# CRI-O
Supported OS Integration version5.4.0
## Overview{% #overview %}

This check monitors [CRI-O](http://cri-o.io).

**Minimum Agent version:** 6.6.0

## Setup{% #setup %}

### Installation{% #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{% #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](https://github.com/DataDog/integrations-core/blob/master/crio/datadog_checks/crio/data/conf.yaml.example) for all available configuration options.

1. [Restart the Agent](https://docs.datadoghq.com/agent/guide/agent-commands.md#restart-the-agent).

### Validation{% #validation %}

[Run the Agent's status subcommand](https://docs.datadoghq.com/agent/guide/agent-commands.md#agent-information) and look for `crio` under the Checks section.

## Data Collected{% #data-collected %}

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

### Metrics{% #metrics %}

|  |
|  |
| **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*                      |
| **crio.operations.count**(count)            | Counter of CRI-O operations                                      |
| **crio.operations.latency.count**(gauge)    | Count of CRI-O operations latency                                |
| **crio.operations.latency.quantile**(gauge) | Quantiles of CRI-O operations latency                            |
| **crio.operations.latency.sum**(gauge)      | Sum of CRI-O operations latency*Shown as microsecond*            |

### Service Checks{% #service-checks %}

**crio.prometheus.health**:Returns `CRITICAL` if the Agent cannot reach the metrics endpoints.

### Events{% #events %}

CRI-O does not include any events.

### Service Checks{% #service-checks-1 %}

**crio.prometheus.health**

Returns `CRITICAL` if the check can't access the metrics endpoint.

*Statuses: ok, critical*

## Troubleshooting{% #troubleshooting %}

Need help? Contact [Datadog support](https://docs.datadoghq.com/help/).