Feature #472

Get cpu consumption from KVM VMs

Added by Javi Fontan over 10 years ago. Updated over 10 years ago.

Status:ClosedStart date:01/21/2011
Priority:NormalDue date:
Assignee:Javi Fontan% Done:


Category:Drivers - Auth
Target version:Release 2.2
Resolution:fixed Pull request:


KVM virtual machines lack cpu consumption information

Associated revisions

Revision ff8e45da
Added by Javi Fontan over 10 years ago

New probes and ganglia readers (from branch feature-446)

Feature #244: Network interface statistics for KVM
Feature #446: Probe to get monitoring info from ganglia
Feature #472: Get cpu consumption from KVM VMs

poll_xen_kvm.rb - This new probe gets information from XEN and KVM vms.
If it is called with the name of a VM then its monitoring information
is written in standard poll probe way. If called without parameters
a base64-encoded yaml-representation of a hash containing the information
about all the VMs running in the host is returned.

poll_ganglia.rb - This probe gets information from ganglia pushed by gmetric.
Consumes the information generated by poll_xen_kvm.rb

ganglia_probe - Gets host monitoring information from ganglia. It pushes all
metrics that start by OPENNEBULA_

Ganglia.rb - library that holds ganglia reading code

Revision d785ca94
Added by Jaime Melis almost 4 years ago

Merge pull request #472 from abelCoronado93/feature-5326

F #5326: Enabled 'Delete' buttom in snapshot-tab when the vCenter VM …


#1 Updated by Ruben S. Montero over 10 years ago

  • Target version set to Release 2.2

#2 Updated by Shi Jin over 10 years ago

I am very happy to see the monitoring code here.
Just one thing: the poll code calls the ps command for CPU utilization which is the average from the starting of the VM while I would say we should use something like top to get more instantaneous (averaged since last top update, typically 3 seconds) CPU monitoring. Of course we need to first define what the CPU column from the "onevm list" output is for: instantaneous or average from the start.

Thank you.

#3 Updated by Javi Fontan over 10 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

We will deal with the way we get CPU info for kvm machines in later releases.

Also available in: Atom PDF