Bug 1034452 - Metrics in storage node UI should report current values
Metrics in storage node UI should report current values
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server, Core UI, Storage Node (Show other bugs)
4.9
Unspecified Unspecified
unspecified Severity medium (vote)
: GA
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-25 16:11 EST by John Sanda
Modified: 2013-11-25 16:29 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screenshot of alerts (81.54 KB, image/png)
2013-11-25 16:11 EST, John Sanda
no flags Details
screenshot of metrics (85.62 KB, image/png)
2013-11-25 16:12 EST, John Sanda
no flags Details

  None (edit)
Description John Sanda 2013-11-25 16:11:03 EST
Description of problem:
I was monitoring a storage node cluster, periodically checking the storage node admin UI for alerts. I was primarily looking at the list view. Eventually I started seeing alerts for a couple nodes due to high disk usage. My first inclination was to look at the disk metrics in the details view for each node. The values reported by the metrics did not indicate any problems. Then I realized that this is likely because are aggregate values for the past 8 hours. I wound up logging onto each machine and inspecting the file systems from the command line. The alerts were 100% correct. The data files for the raw_metrics table were starting to take up a lot of space.

This is far from ideal. Users are likely go to the storage node details view when alerts are generated just like I did. While the metrics reported are correct, they are not helpful for dealing with the alerts. I think we need to display current values somewhere to help users deal with the situation. We may want to get some UXD input on this as well.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 John Sanda 2013-11-25 16:11:56 EST
Created attachment 828891 [details]
screenshot of alerts
Comment 2 John Sanda 2013-11-25 16:12:26 EST
Created attachment 828892 [details]
screenshot of metrics
Comment 3 John Sanda 2013-11-25 16:13:44 EST
I have attached a couple screenshots from my test environment that show the list view when alerts have been generated along with the details view of a node for which several alerts have fired.

Note You need to log in before you can comment on or make changes to this bug.