This check monitors CRI-O.
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.
The integration relies on the
--enable-metrics option of CRI-O that is disabled by default, when enabled metrics are exposed at
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 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.
|Counter of CRI-O operations|
|Sum of CRI-O operations latency|
Shown as microsecond
|Count of CRI-O operations latency|
|Quantiles of CRI-O operations latency|
|Total user and system CPU time spent in seconds|
Shown as second
|Resident memory size in bytes|
Shown as byte
|Virtual memory size in bytes|
Shown as byte
CRI-O includes a service check about the reachability of the metrics endpoint.
CRI-O does not include any events.
Need help? Contact Datadog support.
Mistake in the docs? Feel free to contribute!