Supported OS
This check monitors CRI-O .
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.
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.
Run the Agent’s status subcommand
and look for crio under the Checks section.
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.
| crio.operations.count (count) | 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 |
crio.prometheus.health
Returns CRITICAL if the check can’t access the metrics endpoint.
Statuses: ok, critical
Need help? Contact Datadog support .
