obsdog

CRI-O integration metrics

The official Datadog integration for monitoring CRI-O. It collects 7 metrics.

Official summary

Track all your CRI-O metrics with Datadog

Metric types

  • gauge (value at a point in time): 6
  • count (occurrences in the interval): 1

Metrics

Descriptions are the official definitions, unedited.

MetricTypeUnit
crio.cpu.timeTotal user and system CPU time spent in secondsgaugesecond
crio.mem.residentResident memory size in bytesgaugebyte
crio.mem.virtualVirtual memory size in bytesgaugebyte
crio.operations.countCounter of CRI-O operationscount-
crio.operations.latency.countCount of CRI-O operations latencygauge-
crio.operations.latency.quantileQuantiles of CRI-O operations latencygauge-
crio.operations.latency.sumSum of CRI-O operations latencygaugemicrosecond

Official documentation

Official documentation for the CRI-O integration

Metric names and descriptions are the official Datadog integration definitions (Copyright Datadog, Inc., BSD-3-Clause), reproduced unedited. The full license terms are on the About page.

Related products

IntegrationsIntegrations are the bundle of entry points that pour data from external systems such as AWS and MySQL into Datadog. Where you configure them splits into two families, the Agent side and the cloud account side, and which one you choose changes both what you can see and how billing is counted.Foundation and data collectionContainer MonitoringA mechanism for following containers that are born and gone within seconds and keep moving between nodes, with the same hands-on approach as host monitoring. On Kubernetes, how the Agent is placed and how billing is counted are both specific to containers, so we cover those two points first.Infrastructure monitoringDatadog AgentSoftware that runs resident on the servers and containers you monitor and delivers metrics, logs, and traces to Datadog.Foundation and data collectionMetricsFrom CPU utilization to user sign-ups, metrics are the core data of Datadog, recording every number in your environment as a time series. If you understand how they are counted before how they are collected, you avoid aggregation mistakes and unexpected charges.Foundation and data collection

Other Containers integrations

Datadog Cluster Agent98 metricsDocker Daemon121 metricsAmazon ECS on AWS Fargate34 metricsetcd196 metricsHarbor4 metricsKubernetes API server metrics78 metricsKubernetes Controller Manager28 metricsKube DNS10 metricsKubernetes Metrics Server15 metricsKube Proxy18 metricsKubernetes Scheduler43 metricsKubelet101 metrics