CRI-O

Supported OS Linux Mac OS Windows

통합 버전5.0.0
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Overview

This check monitors CRI-O.

Setup

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 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

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

crio.prometheus.health

Returns CRITICAL if the check can’t access the metrics endpoint.

Statuses: ok, critical

Events

CRI-O does not include any events.

Service Checks

See service_checks.json for a list of service checks provided by this integration.

Troubleshooting

Need help? Contact Datadog support.