KubeVirt Handler

Supported OS Linux Windows Mac OS

Integration version1.1.0
This integration is in public beta and should be enabled on production workloads with caution.

Overview

This check monitors KubeVirt Handler through the Datadog Agent.

Setup

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.

Installation

The KubeVirt Handler check is included in the Datadog Agent package. No additional installation is needed on your server.

Configuration

  1. Edit the kubevirt_handler.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your kubevirt_handler performance data. See the sample kubevirt_handler.d/conf.yaml for all available configuration options.

  2. Restart the Agent.

Validation

Run the Agent’s status subcommand and look for kubevirt_handler under the Checks section.

Data Collected

Metrics

kubevirt_handler.can_connect
(gauge)
Value of 1 if the agent can connect to the KubeVirt Handler, and 0 otherwise.
kubevirt_handler.vmi.cpu_system_usage_seconds.count
(count)
Total CPU time spent in system mode.
Shown as second
kubevirt_handler.vmi.cpu_usage_seconds.count
(count)
Total CPU time spent in all modes (sum of both vcpu and hypervisor usage).
Shown as second
kubevirt_handler.vmi.cpu_user_usage_seconds.count
(count)
Total CPU time spent in user mode.
Shown as second
kubevirt_handler.vmi.memory_actual_balloon_bytes
(gauge)
Current balloon size in bytes.
Shown as byte
kubevirt_handler.vmi.memory_available_bytes
(gauge)
Amount of usable memory as seen by the domain.
Shown as byte
kubevirt_handler.vmi.memory_domain_bytes
(gauge)
The amount of memory in bytes allocated to the domain.
Shown as byte
kubevirt_handler.vmi.memory_pgmajfault.count
(count)
The number of page faults when disk IO was required.
Shown as page
kubevirt_handler.vmi.memory_pgminfault.count
(count)
The number of other page faults, when disk IO was not required.
Shown as page
kubevirt_handler.vmi.memory_resident_bytes
(gauge)
Resident set size of the process running the domain.
Shown as byte
kubevirt_handler.vmi.memory_swap_in_traffic_bytes
(gauge)
The total amount of data read from swap space of the guest in bytes.
Shown as byte
kubevirt_handler.vmi.memory_swap_out_traffic_bytes
(gauge)
The total amount of memory written out to swap space of the guest in bytes.
Shown as byte
kubevirt_handler.vmi.memory_unused_bytes
(gauge)
The amount of memory left completely unused by the system.
Shown as byte
kubevirt_handler.vmi.memory_usable_bytes
(gauge)
The amount of memory which can be reclaimed by balloon without pushing the guest system to swap, corresponds to 'Available' in /proc/meminfo
Shown as byte
kubevirt_handler.vmi.network_receive_bytes.count
(count)
Total network traffic received in bytes.
Shown as byte
kubevirt_handler.vmi.network_receive_errors.count
(count)
Total network received error packets.
Shown as packet
kubevirt_handler.vmi.network_receive_packets.count
(count)
Total network traffic received packets.
Shown as packet
kubevirt_handler.vmi.network_receive_packets_dropped.count
(count)
The total number of rx packets dropped on vNIC interfaces.
Shown as packet
kubevirt_handler.vmi.network_transmit_bytes.count
(count)
Total network traffic transmitted in bytes.
Shown as byte
kubevirt_handler.vmi.network_transmit_errors.count
(count)
Total network transmitted error packets.
Shown as packet
kubevirt_handler.vmi.network_transmit_packets.count
(count)
Total network traffic transmitted packets.
Shown as packet
kubevirt_handler.vmi.network_transmit_packets_dropped.count
(count)
The total number of tx packets dropped on vNIC interfaces.
Shown as packet
kubevirt_handler.vmi.node_cpu_affinity
(gauge)
Number of VMI CPU affinities to node physical cores.
kubevirt_handler.vmi.storage_flush_requests.count
(count)
Total storage flush requests.
Shown as request
kubevirt_handler.vmi.storage_flush_times_seconds.count
(count)
Total time spent on cache flushing.
Shown as second
kubevirt_handler.vmi.storage_iops_read.count
(count)
Total number of I/O read operations.
Shown as read
kubevirt_handler.vmi.storage_iops_write.count
(count)
Total number of I/O write operations.
Shown as write
kubevirt_handler.vmi.storage_read_times_seconds.count
(count)
Total time spent on read operations.
Shown as second
kubevirt_handler.vmi.storage_read_traffic_bytes.count
(count)
Total number of bytes read from storage.
Shown as byte
kubevirt_handler.vmi.storage_write_times_seconds.count
(count)
Total time spent on write operations.
Shown as second
kubevirt_handler.vmi.storage_write_traffic_bytes.count
(count)
Total number of written bytes.
Shown as byte
kubevirt_handler.vmi.vcpu_delay_seconds.count
(count)
Amount of time spent by each vcpu waiting in the queue instead of running.
Shown as second
kubevirt_handler.vmi.vcpu_seconds.count
(count)
Total 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].
Shown as second
kubevirt_handler.vmi.vcpu_wait_seconds.count
(count)
Amount of time spent by each vcpu while waiting on I/O.
Shown as second
kubevirt_handler.workqueue.adds.count
(count)
Total number of adds handled by workqueue
Shown as item
kubevirt_handler.workqueue.depth
(gauge)
Current depth of workqueue
Shown as item
kubevirt_handler.workqueue.longest_running_processor_seconds
(gauge)
How many seconds has the longest running processor for workqueue been running.
Shown as second
kubevirt_handler.workqueue.queue_duration_seconds.bucket
(count)
How long an item stays in workqueue before being requested.
Shown as second
kubevirt_handler.workqueue.queue_duration_seconds.count
(count)
How long an item stays in workqueue before being requested.
Shown as second
kubevirt_handler.workqueue.queue_duration_seconds.sum
(count)
How long an item stays in workqueue before being requested.
Shown as second
kubevirt_handler.workqueue.retries.count
(count)
Total number of retries handled by workqueue
kubevirt_handler.workqueue.unfinished_work_seconds
(gauge)
How 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.
Shown as second
kubevirt_handler.workqueue.work_duration_seconds.bucket
(count)
How long in seconds processing an item from workqueue takes.
Shown as second
kubevirt_handler.workqueue.work_duration_seconds.count
(count)
How long in seconds processing an item from workqueue takes.
Shown as second
kubevirt_handler.workqueue.work_duration_seconds.sum
(count)
How long in seconds processing an item from workqueue takes.
Shown as second

Events

The KubeVirt Handler integration does not include any events.

Service Checks

The KubeVirt Handler integration does not include any service checks.

Troubleshooting

Need help? Contact Datadog support.