Currently the DWH contains read/write stats for each VM: v4_4_statistics_vms_disks_resources_usage_samples contains: read_rate_bytes_per_second | read_latency_seconds | write_rate_bytes_per_second | write_latency_seconds | flush_latency_seconds It would be nice if this could be extended with read and write IOPS stats. As far as I can see VDSM already reads those stats, but they are never parsed/saved in the ovirt-engine. I think IOPS stats are equally important as read/write byte stats, as it could be you have huge amount of IOPS on a VM, but low troughput. So without IOPS stats you cannot notice this.
Created attachment 1715392 [details] Possible patch attached a possible patch. Might have forgotten things, but should be quite ok :)
Created attachment 1715393 [details] Now with upgrade db script added
Shirly can you please review?
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
can you please push(and follow on) the patch to gerrit.ovirt.org?
$ git tag --contains 583dce8ab676eba10b1fb58b4d28d11cfa7bb22d ovirt-engine-4.4.3.10 ovirt-engine-4.4.3.8 ovirt-engine-4.4.3.9 This can be tested with 4.4.3 build
Verified on ovirt-engine-4.4.4.2-0.1.el8ev.noarch with the following steps: 1. Create a VM with disk and OS 2. Run the VM 3. Perform cp to a big file and in parallel check that read_ops and write_ops values are changing in the DB: # engine-psql.sh -c "SELECT image_id, read_ops, write_ops from disk_image_dynamic" Moving to 'Verified'.
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.4 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.