Description of problem: Provide the correct heading for "Disk IO" panel in host dashboard (Capacity and Disk load section) Version-Release number of selected component (if applicable):3.4 (Sandbox Environment) How reproducible: Always Steps to Reproduce: 1. View the Disk IO panel in host dashboard 2. 3. Actual results: Expected results: The panel is display latency, so the panel heading should reflect that (like "Disk IO Latency") and as well as the panel information. Additional info:
Assuming this has been reported based on sandbox-usm1 instance, the full package version list follows: ``` [root@sandbox-usm1-server ~]# rpm -qa | grep tendrl | sort tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-7.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-5.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-5.el7rhgs.noarch tendrl-node-agent-1.6.3-7.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-4.el7rhgs.noarch ```
Created attachment 1455105 [details] screenshot of disk IO chart
Changed "Disk IO" panel name to "Disk IO Latency". https://github.com/Tendrl/monitoring-integration/pull/512/files
Created attachment 1464891 [details] Disk IO Latency panel correct label
Disk IO panel in host dashboard was renamed to "Disk IO Latency". (attachment 1464891 [details]). Version-Release number of selected component: grafana-4.3.2-3.el7rhgs.x86_64 tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-4.el7rhgs.noarch tendrl-api-httpd-1.6.3-4.el7rhgs.noarch tendrl-commons-1.6.3-9.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-7.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch tendrl-node-agent-1.6.3-9.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-8.el7rhgs.noarch >> VERIFIED
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, 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-2018:2616