Bug 1887149
| Summary: | [RFE] VM Disk stats should contain IOPS stats | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine-dwh | Reporter: | Shirly Radco <sradco> |
| Component: | RFEs | Assignee: | Shirly Radco <sradco> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Guilherme Santos <gdeolive> |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.4.3 | CC: | ahadas, alitman, bugs, gdeolive, jean-louis, lleistne, michal.skrivanek, mperina, pelauter, sbonazzo, sradco, tnisan, vjuranek |
| Target Milestone: | ovirt-4.4.5 | Keywords: | FutureFeature |
| Target Release: | 4.4.5 | Flags: | pm-rhel:
ovirt-4.4+
pelauter: planning_ack+ sbonazzo: devel_ack+ lleistne: testing_ack+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-dwh-4.4.5 | Doc Type: | Enhancement |
| Doc Text: |
Feature:
Collect VM disks IOPS stats to DWH database
Reason:
Allow users to view VM disks IOPS stats
Result:
VM disks IOPS stats are now saved to DWH database and aggregated to hourly and daily data.
|
Story Points: | --- |
| Clone Of: | 1880424 | Environment: | |
| Last Closed: | 2021-03-18 15:12:51 UTC | Type: | --- |
| 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: | 1880424 | ||
| Bug Blocks: | 1899573 | ||
|
Description
Shirly Radco
2020-10-11 10:02:09 UTC
Already (partly) implemented: https://gerrit.ovirt.org/#/c/111834/ It just needs an updated etl export! This fix requires two steps: 1. Add the requested columns (read and write IOPS stats) to DWH. 2. Add the requested columns into reports in Grafana. The first step will be documented in this bug, and the second step will be documented in bug: https://bugzilla.redhat.com/show_bug.cgi?id=1899573 Hi Shirly, is the verification steps for this bz to query the iops data from the iops newly created tables and compare with the vdsm one (with virsh), or is there more to be tested? Thanks (In reply to Guilherme Santos from comment #3) > Hi Shirly, is the verification steps for this bz to query the iops data from > the iops newly created tables and compare with the vdsm one (with virsh), or > is there more to be tested? Thanks Also,have DWH running for at least 2 days and see that the daily and hourly aggregations also work as expected. Verified on:
ovirt-engine-4.4.5.9-0.1.el8ev.noarch
Steps:
1. Had an engine with hosts running for 1 ~ 2 days
2. Validated new columns
ovirt_engine_history=# select read_ops_per_second, write_ops_per_second from vm_disk_samples_history order by history_id desc limit 5;
read_ops_per_second | write_ops_per_second
---------------------+----------------------
10052 | 8436
10052 | 8426
10052 | 8420
10052 | 8412
10052 | 8406
(5 rows)
ovirt_engine_history=# select read_ops_per_second, max_read_ops_per_second, write_ops_per_second, max_write_ops_per_second from vm_disk_hourly_history order by history_id desc limit 5;
read_ops_per_second | max_read_ops_per_second | write_ops_per_second | max_write_ops_per_second
---------------------+-------------------------+----------------------+--------------------------
10052 | 10052 | 7763 | 7950
10052 | 10052 | 7413 | 7590
10052 | 10052 | 7044 | 7235
10052 | 10052 | 6680 | 6854
10052 | 10052 | 6313 | 6495
(5 rows)
ovirt_engine_history=# select read_ops_per_second, max_read_ops_per_second, write_ops_per_second, max_write_ops_per_second from vm_disk_daily_history order by history_id desc limit 5;
read_ops_per_second | max_read_ops_per_second | write_ops_per_second | max_write_ops_per_second
---------------------+-------------------------+----------------------+--------------------------
0 | 0 | 0 | 0
33972 | 34910 | 190063 | 323702
0 | 0 | 0 | 0
40066 | 56160 | 126900 | 182968
0 | 0 | 0 | 0
(5 rows)
Results:
Columns present in the DW and hourly and daily aggregations working as expected
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.5 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. |