I don't imagine this will get fixed for 1.1 but it should be... If there are a bunch of systems, perhaps in various states of normal/down/maintenance, in an HA cloud, the partition events log (JON Administration > Partition Events) can get unwieldy quite quickly -- 7000+ events fired in 12 hours, for example. There should be some sort of filter mechanism on this page which would allow user to display only those events which matter to him/her. Ideally: * Freeform 'search' field * Dropdowns for ** Operation Type ** Initiated By ** Execution Staus ** Server names known to be in the cloud (maybe) * Selector for events that have taken place in the last ** Five Minutes ** Hour ** Day ** Week This is actually looking more like a feature, but in really it's just some specs for what should be in this UI.
yeah, i've had this 75% done since mid last week. just found time this morning to finish it up. will commit shortly. this should enhance large-scale testing verification.
rev1591 - add filtering to partition events history page; can now filter on Details (case-insensitive substring), ExecutionStatus, and PartitionEventType; also, add some defensive coding in StringUtility.getIntegerArray(String[]) when UI logic passing null (either accidentally or purposefully); disable enter key for Detail filter inputText element, to force the user to use the ajax-y "GO" button to refresh the dataTable and datascroller;
RHQ-932 may block this... or more accurately, the root cause (RHQ-930) may. I'm amenable to closing this if RHQ-930 gets pushed to 1.2
We tested this and have opened other issues to track bugs. closing this one.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-866