Description of problem ====================== Description of Health panel of At-a-Glance section on Volume dashboard is insufficient, because it doesn't provide a list of all possible states of a volume health the dashboard recognizes. Version-Release number of selected component ============================================ tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch Steps to Reproduce ================== 1. Instal RHGS WA using tendrl-ansible 2. Import Trusted storage pool with at least one volume 3. Go to Volume dashboard and check Health panel's description (available via little "i" icon on top left corner of the panel). Actual results ============== The description states: > The Health panel displays the overall health for a given volume. See screenshot 1 Expected results ================ The description provides more details, including list of all possible health states which WA dashboard recognizes with a brief description (if needed).
Created attachment 1474596 [details] screenshot 1: description of health panel on volume dashboard
Proposed Description: The Health panel displays the overall health for a given volume, which is either Up, Down, Failed, Up(Degraded), Up (Partial) or Unknown
(In reply to gowtham from comment #3) > Proposed Description: > > The Health panel displays the overall health for a given volume, which is > either Up, Down, Failed, Up(Degraded), Up (Partial) or Unknown Atin, does this make sense from gluster point of view?
Barring started and stopped, the rest of the states are derived by higher layer by looking at volume configuration, bricks & their status along with volume status.
Proposed Description: The Health panel displays the overall health for a given volume, which is either Up, Down, Up(Degraded), Up (Partial) or Unknown I removed Failed state, There is no failed state for volume
PR is under review: https://github.com/Tendrl/monitoring-integration/pull/554
(In reply to gowtham from comment #7) > PR is under review: https://github.com/Tendrl/monitoring-integration/pull/554 Seems to be merged. What's the next step?
Will target this for 3.5.z
This is a very minor enhancement. Since the decision is to ship only the critical and customer impacting bugs, I don't think this will qualify for a batch update. Closing this bug.