Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2010903

Summary: I/O operations/sec reporting wrong values
Product: Red Hat Enterprise Virtualization Manager Reporter: Marian Jankular <mjankula>
Component: ovirt-engine-dwhAssignee: Aviv Litman <alitman>
Status: CLOSED ERRATA QA Contact: Pavel Novotny <pnovotny>
Severity: low Docs Contact:
Priority: low    
Version: 4.4.7CC: emarcus, gdeolive, lsurette, mavital, mhicks, mperina, srevivo
Target Milestone: ovirt-4.5.0   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-dwh-4.5.1 Doc Type: Bug Fix
Doc Text:
Database columns and dashboard field descriptions have been updated to match the real meanings in I/O operations data fields.
 Story Points: ---
Clone Of:
: 2018796 (view as bug list) Environment:
Last Closed: 2022-05-26 16:23:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Metrics RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2014888, 2064259    

Description Marian Jankular 2021-10-05 15:06:47 UTC 
Description of problem:
oVirt Trend Dashboards > Virtual Machines Trend Dashboard > Top 5 Most Utilized Disks - I/O operations/sec values are taken from vdsm getvmstats "writeOps" for the disk value, according to  https://github.com/oVirt/vdsm/blob/master/lib/vdsm/api/vdsm-api.yml this value is "Write operations since VM start" and in the above view it is reported as "I/O operations/sec" as far as i know we are getting only below values for the disk:

-------------------
                "apparentsize": "29796335616",
                "flushLatency": "21530.033333333333",
                "imageID": "b779ebc9-e13d-4183-977d-d718e831f62f",
                "readBytes": "223528208896",
                "readLatency": "0",
                "readOps": "713399",
                "readRate": "0.0",
                "truesize": "29796335616",
                "writeLatency": "238450.35",
                "writeOps": "188434753",
                "writeRate": "3415.170881011688",
                "writtenBytes": "755119997952"
-------------------

I think that for the trend view it would be more suitable to see writeRate value if there is no other easy way to got iops

Version-Release number of selected component (if applicable):
RHV 4.4.7

How reproducible:
everytime

Steps to Reproduce:
1. setup monitoring portal accoring to documentation
2. create loop in vm "while true; do dd if=/dev/zero of=file count=100 bs=1M && sleep 5; done"
3. leave it running for couple of minutes and look at oVirt Trend Dashboards > Virtual Machines Trend Dashboard > Top 5 Most Utilized Disks - I/O operations/sec view where the values for the disk you are writing to will start increasing even the spped operation is still the same


Actual results:
graph is showing "Write operations since VM start" instead of "I/O operations/sec" 

Expected results:
either rename view to total number of iops since start of the vm or adjust source values

Additional info:
Comment 14 Pavel Novotny 2022-05-06 23:49:33 UTC 
Verified in
ovirt-engine-4.5.0.6-0.7.el8ev.noarch
ovirt-engine-dwh-4.5.2-1.el8ev.noarch

Trend dashboard panels with disk I/O statistics were updated to correctly say "since VM start" instead of "per second":

oVirt Trend Dashboards
03 Virtual Machines Trend Dashboard : Top 5 Most Utilized Disks - I/O operations since VM start (over time) (TR03-6)
05 Virtual Machines Resource Usage Dashboard : 
  - Top 5 Most Utilized Disks - Read I/O operations since VM start (TR05-9)
  - Top 5 Most Utilized Disks - Write I/O operations since VM start (TR05-10)

Also the DB columns in the VM samples/hourly/daily tables have been renamed accordingly.
Comment 19 errata-xmlrpc 2022-05-26 16:23:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.0] security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:4711
Comment 20 meital avital 2022-07-20 08:47:43 UTC 
Due to QE capacity we are not going to cover this issue in our automation