Description of problem: VDSM does not report VM memory statistics to collectd statsd plugin. Version-Release number of selected component (if applicable): vdsm-4.20.7-55 How reproducible: 100% Steps to Reproduce: 1. Setup ovirt-metrics 2. Check statsd plugin statistics 3. Actual results: No memory statistics reported by vdsm. Expected results: Send memory usage statistics for vms to collectd statsd plugin. Additional info:
The patch reports the memory values from bulk stats returned from libvirt. this will be enabled only with this patch https://gerrit.ovirt.org/#/c/80721/ in engine side (not part of ovirt-engine-4.1). I guess that once setting "dommemstat --period 5 [vm-name]" you will get the balloon info also from collectd plugin. In https://gerrit.ovirt.org/#/c/80644/ we take the balloon info and translate it to memoryStats - which then can be sent from vdsm. If this is still useful more than using only collectd virt plugin, the fix indeed adds the desired logic.
Even if we merge the patch and upgrade to 4.2 - adding the set for memballoon in the vm xml requires to run dommemstat manually or creating the vm again.
Can't we automate this so on upgrade this will be set?
I can't imagine valid scenario where after ovirt upgrade all your vms will be rebooted automatically. Tomas - can you attach <stats period='5' /> to memballoon section on runtime for all vms during upgrade to 4.2? I
(In reply to Yaniv Bronhaim from comment #4) > I can't imagine valid scenario where after ovirt upgrade all your vms will > be rebooted automatically. This is a new feature. Where's the problem in waiting for users to reboot the machines when they see fit? > Tomas - can you attach <stats period='5' /> to memballoon section on > runtime for all vms during upgrade to 4.2? I Doing it in runtime is not a problem. But from what I've been told we are not doing this kind of modifications during upgrades in VDSM.
filed Bug #1532681 and Bug #1532692 to cover the requirement to reboot the vms to get memory stats.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
the patch https://gerrit.ovirt.org/#/c/86309 restructures the metrics names to fit collector expectation (vmname.memory.value). This still returns zero values until fetching GA info as part of the stats (Bug #1532692)
Moving the dependency to See also, because infra part can be merged into VDSM, so relevant field will be propagated into metrics store. But those fields values will always be 0 until BZ1532692 is fixed
Abandoning current patch. virt values will be collected in ovirt-4.2.2 by collectd 5.8.0 virt-plugin - this should follow removal patch for all unneeded vm stats that we sent from vdsm (Bug #1370909)
virt stats are being reported correctly in collectd.virt plugin ovirt-engine-metrics-1.1.3.3-1.el7ev.noarch
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.