Red Hat Bugzilla – Bug 1012512
[Usability] Improve runtime statistics for messaging destinations
Last modified: 2015-08-31 23:29:36 EDT
Ideas for improving runtime statistics tab for destinations: - improve the scale on messages count bars - don't use real numbers if the number of messages is low, give user absolute number of messages (the scale labels sometimes don't go all the way to 100%) - list how many clients are connected to the destinations, for topics also list subscription IDs and how many messages was consumed per subscription - list more than 4 destinations in the table or let the user set how many of them she wants to see
Created attachment 803456 [details] Screenshot of the metrics bar labels Notice how the last label is before the end of the bar, resulting in the user not being able to see the total number of messages.
In agreement with Catherine we've decided that UX issues will be tracked separately.
Issue moved under the UX component. Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.
To be addressed in EAP 7 monitoring designs.
Including some of the labels recommended within the original design handoff might help to resolve some of the issues.
Created attachment 926175 [details] Original design recommendation. This is a copy of the original recommended design. It included additional labels, summary text and a legend.
Created attachment 930480 [details] current message stats
Should this still remain in POST state?
-numbers from bars are listed next to the bar and therefore easy to read -better message stats