QEMU/KVM
Monitor your QEMU/KVM virtual machines
CPU, memory, disk and network for every VM on your hypervisors, read through libvirt.
Through libvirt, nothing in the guests
The agent on the hypervisor reads each VM through libvirt. Add its user to the libvirt group and every guest shows up, with nothing to install inside the VMs.
- CPU and memory used by each VM
- Disk read and write throughput
- Network traffic in and out
- Next to the hypervisor’s own CPU, memory and disk
Every guest on every hypervisor
Find the VM that is eating the host, before its neighbours notice.
Every VM
All the guests libvirt knows about, on each hypervisor.
CPU and memory
How much each VM uses, so the noisy neighbour stands out.
Disk throughput
Read and write throughput for each VM.
Network traffic
Bytes in and out for each VM.
No sudo needed
The agent only needs to be in the libvirt group.
24 months of history
Every VM metric is kept for 24 months.
Frequently asked questions
Through libvirt, from the agent running on the hypervisor.
Add the fivenines user to the libvirt group. No sudo is needed for VM metrics.
No. Install the agent in a guest only if you also want its processes and services.
Proxmox has its own integration, which reads clusters, nodes and guests through the Proxmox API.
Linux hypervisors running QEMU/KVM with libvirt.
Something else on your mind? Talk to us →