Red Hat Bugzilla – Bug 498438
SDC Overview System Health Warning Despite Critical Probe Results
Last modified: 2014-05-09 06:38:57 EDT
Created attachment 341930 [details]
Screenshot of SSM monitoring status div.
Description of problem:
The main overview page of the SSM can sometimes display system health warning when in fact there are critical probes in the list.
The jsp page checks the status of the first probe in the list to determine if it should display warning or critical, but the probes are not returned sorted by status and thus warnings can be in the list before criticals.
Version-Release number of selected component (if applicable):
Might need to play around with the order your probes start triggering, in my case I had one critical probe failing first, then another going to warning status later.
Steps to Reproduce:
1. Add monitoring probe to a system that will trigger as critical. (say free memory less than some outlandishly high value)
2. View SDC, see "System Health Critical".
3. Add another probe that will trigger as a warning (system load in my case) and wait until it triggers.
4. View SDC again, should see System Health Warning if the warning is now the first in the list.
See attached screenshot, note that there's a critical probe notification in the list, but system health says warning.
System health should be critical if there are any criticals in the list at all.
First probe I had trigger (the critical one) was memory, the second was system load (the warning). (just incase these are sorted by some alphabetical criteria)
Might want to return them sorted by severity to the JSP, or setup the JSP with a boolean that indicates if there are criticals in the list rather than just looking at the first one.
We don't think this is a regression, so making a can-fix. Also, we think SSM should be replaced by SDC based on the screen-shot.
Whoops, you are corrected. Got my three letter acronyms starting with S mixed up. :)
We have not addressed this specific bug in over 5 years years. This does not seem to have an active customer case with the bug report either. Closing out as wontfix to clear from backlog.
Please re-open if you disagree and wish further review.