Most of them are outdated, but provide historical design context.
They are not user documentation and should not be treated as such.
Documentation is available here.
ATTENTION: This page is no longer up to date. Please follow the link for the updated documentation:
Metrics Store - Collected Data
collectd gathers oVirt statistics from the oVirt engine and hypervisors, and transfers the data to fluentd.
The data is then transformed, enriched, and sent to the remote metrics store.
oVirt Metrics - collectd loaded plugins list
Disk utilization: Sectors read/written, number of read/write actions, average time an IO-operation took to complete.
CPU time spent in the system, user, nice, idle, wait, interrupt, softirq and steal.
Collects information about the used, buffered, cached and free RAM memory.
The average number of runnable tasks in the run-queue, for one, five, and fifteen minute average.
Virt (Applies only to oVirt hypervisors).
CPU, memory, disk, and network I/O statistics from virtual machines.
NFS usage: A count of the number of procedure calls for each procedure, grouped by version and whether the system runs as a server or client. NFS version 4 is not supported for now.
Amount of entropy available to the system.
Records the free, cached, and used memory utilized by swap and swap in/out.
Collects file system (incl. the hard drive) usage information such as free, reserved, and used space.
Collects network traffic download and upload data, including the number of octets, packets, and errors transmitted and received, for each network interface.
Aggregates multiple values into a single value, using one or several consolidation functions, e.g. summation and average.
Collects the number of processes, grouped by their state (incl. running, blocked, sleeping, paging, stopped and zombies).
PostgreSQL (Applies only to oVirt engine).
PostgreSQL database statistics: custom_deadlocks, table_states, disk_io, disk_usage.
fluentd collects oVirt logs from the oVirt engine and hypervisors. The data is then transformed, enriched and sent to the remote metrics store.
Logs collected from the engine machine include:
Logs collected from the hypervisors machines include: