KubeVirt Handler integration metrics

The official Datadog integration for monitoring KubeVirt Handler. It collects 45 metrics.

Official summary

Collect key metrics to monitor the health of your KubeVirt Handler Daemons.

Metric types

  • count (occurrences in the interval): 32
  • gauge (value at a point in time): 13

Metrics

Descriptions are the official definitions, unedited.

MetricTypeUnit
kubevirt_handler.can_connectValue of 1 if the agent can connect to the KubeVirt Handler, and 0 otherwise.gauge-
kubevirt_handler.vmi.cpu_system_usage_seconds.countTotal CPU time spent in system mode.countsecond
kubevirt_handler.vmi.cpu_usage_seconds.countTotal CPU time spent in all modes (sum of both vcpu and hypervisor usage).countsecond
kubevirt_handler.vmi.cpu_user_usage_seconds.countTotal CPU time spent in user mode.countsecond
kubevirt_handler.vmi.memory_actual_balloon_bytesCurrent balloon size in bytes.gaugebyte
kubevirt_handler.vmi.memory_available_bytesAmount of usable memory as seen by the domain.gaugebyte
kubevirt_handler.vmi.memory_domain_bytesThe amount of memory in bytes allocated to the domain.gaugebyte
kubevirt_handler.vmi.memory_pgmajfault.countThe number of page faults when disk IO was required.countpage
kubevirt_handler.vmi.memory_pgminfault.countThe number of other page faults, when disk IO was not required.countpage
kubevirt_handler.vmi.memory_resident_bytesResident set size of the process running the domain.gaugebyte
kubevirt_handler.vmi.memory_swap_in_traffic_bytesThe total amount of data read from swap space of the guest in bytes.gaugebyte
kubevirt_handler.vmi.memory_swap_out_traffic_bytesThe total amount of memory written out to swap space of the guest in bytes.gaugebyte
kubevirt_handler.vmi.memory_unused_bytesThe amount of memory left completely unused by the system.gaugebyte
kubevirt_handler.vmi.memory_usable_bytesThe amount of memory which can be reclaimed by balloon without pushing the guest system to swap, corresponds to 'Available' in /proc/meminfogaugebyte
kubevirt_handler.vmi.network_receive_bytes.countTotal network traffic received in bytes.countbyte
kubevirt_handler.vmi.network_receive_errors.countTotal network received error packets.countpacket
kubevirt_handler.vmi.network_receive_packets.countTotal network traffic received packets.countpacket
kubevirt_handler.vmi.network_receive_packets_dropped.countThe total number of rx packets dropped on vNIC interfaces.countpacket
kubevirt_handler.vmi.network_transmit_bytes.countTotal network traffic transmitted in bytes.countbyte
kubevirt_handler.vmi.network_transmit_errors.countTotal network transmitted error packets.countpacket
kubevirt_handler.vmi.network_transmit_packets.countTotal network traffic transmitted packets.countpacket
kubevirt_handler.vmi.network_transmit_packets_dropped.countThe total number of tx packets dropped on vNIC interfaces.countpacket
kubevirt_handler.vmi.node_cpu_affinityNumber of VMI CPU affinities to node physical cores.gauge-
kubevirt_handler.vmi.storage_flush_requests.countTotal storage flush requests.countrequest
kubevirt_handler.vmi.storage_flush_times_seconds.countTotal time spent on cache flushing.countsecond
kubevirt_handler.vmi.storage_iops_read.countTotal number of I/O read operations.countread
kubevirt_handler.vmi.storage_iops_write.countTotal number of I/O write operations.countwrite
kubevirt_handler.vmi.storage_read_times_seconds.countTotal time spent on read operations.countsecond
kubevirt_handler.vmi.storage_read_traffic_bytes.countTotal number of bytes read from storage.countbyte
kubevirt_handler.vmi.storage_write_times_seconds.countTotal time spent on write operations.countsecond
kubevirt_handler.vmi.storage_write_traffic_bytes.countTotal number of written bytes.countbyte
kubevirt_handler.vmi.vcpu_delay_seconds.countAmount of time spent by each vcpu waiting in the queue instead of running.countsecond
kubevirt_handler.vmi.vcpu_seconds.countTotal amount of time spent in each state by each vcpu (cpu_time excluding hypervisor time). Where id is the vcpu identifier and state can be one of the following: [OFFLINE, RUNNING, BLOCKED].countsecond
kubevirt_handler.vmi.vcpu_wait_seconds.countAmount of time spent by each vcpu while waiting on I/O.countsecond
kubevirt_handler.workqueue.adds.countTotal number of adds handled by workqueuecountitem
kubevirt_handler.workqueue.depthCurrent depth of workqueuegaugeitem
kubevirt_handler.workqueue.longest_running_processor_secondsHow many seconds has the longest running processor for workqueue been running.gaugesecond
kubevirt_handler.workqueue.queue_duration_seconds.bucketHow long an item stays in workqueue before being requested.countsecond
kubevirt_handler.workqueue.queue_duration_seconds.countHow long an item stays in workqueue before being requested.countsecond
kubevirt_handler.workqueue.queue_duration_seconds.sumHow long an item stays in workqueue before being requested.countsecond
kubevirt_handler.workqueue.retries.countTotal number of retries handled by workqueuecount-
kubevirt_handler.workqueue.unfinished_work_secondsHow many seconds of work has done that is in progress and hasn't been observed by work_duration. Large values indicate stuck threads. One can deduce the number of stuck threads by observing the rate at which this increases.gaugesecond
kubevirt_handler.workqueue.work_duration_seconds.bucketHow long in seconds processing an item from workqueue takes.countsecond
kubevirt_handler.workqueue.work_duration_seconds.countHow long in seconds processing an item from workqueue takes.countsecond
kubevirt_handler.workqueue.work_duration_seconds.sumHow long in seconds processing an item from workqueue takes.countsecond

Official documentation

Official documentation for the KubeVirt Handler 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.