You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Memory metrics are collected one per event, with a field for the name of the metric and another one for the value.
There are no integration tests.
There is test code in the metricset.
It is called kvm, but it actually uses libvirt for monitoring, that can support other hypervisors as Xen or VMware, should we rename the module and offer support for other backends?
I think that this module should be completely revamped, possibly with new metricsets, or as a new libvirt module, some things to do:
Refactor current collected data so metrics are grouped in single events
Add more metrics
Add a dashboard
Use common fields (e.g. kvm.domain.id, kvm.domain.name...)
As reference of available monitoring data, these are the monitoring commands exposed by virsh for example:
Domain Monitoring (help keyword 'monitor')
domblkerror Show errors on block devices
domblkinfo domain block device size information
domblklist list all domain blocks
domblkstat get device block stats for a domain
domcontrol domain control interface state
domif-getlink get link state of a virtual interface
domifaddr Get network interfaces' addresses for a running domain
domiflist list all domain virtual interfaces
domifstat get network interface stats for a domain
dominfo domain information
dommemstat get memory statistics for a domain
domstate domain state
domstats get statistics about one or multiple domains
domtime domain time
list list domains
virsh domstats has a good summary of metrics, other subcommands may be needed to get metadata.
Module for kvm in metricbeat has some issues that should be addressed:
I think that this module should be completely revamped, possibly with new metricsets, or as a new
libvirtmodule, some things to do:kvm.domain.id,kvm.domain.name...)Some potential datasets could be:
As reference of available monitoring data, these are the monitoring commands exposed by virsh for example:
virsh domstatshas a good summary of metrics, other subcommands may be needed to get metadata.For metadata, the non-metrics data of the domain info may be a good reference: