Bug 977923
Summary: | Rfe: View several queues in a single chart / table | ||||||
---|---|---|---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Michael Burman <yak> | ||||
Component: | Core UI | Assignee: | Nobody <nobody> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | unspecified | CC: | hrupp | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
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: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Michael Burman
2013-06-25 15:14:53 UTC
Could that be solved by a group that contains the interesting entities - perhaps generated by a DynaGroup expression? If you e.g. go to HornetQ->default->JMS Queues you can click on JMS Queues to form a so called AutoGroup, that has a monitoring tab that shows the aggregates etc. I can see though that if the interesting resources are below the autogroup node, this does not work out of the box. Here's a small paint-editing example: https://skydrive.live.com/redir?resid=73950695EB898688!1399&authkey=!APwiy5-cJokUvIs From IRC: " <pilhuhn> So basically on the monitoring tab of the group, you can go to the "metrics" aka tables view and see all the metrics and number of reporters. And then either a) click the interesting metrics and click on "show details" to get a table that show the individual resources along with the selected metrics or b) have another tab below "monitoring", where all the resources show and the columns (=metrics) are selected with the column selector ? " My take on this is to use the b) option, as it would allow comparing the groups different resources on several metrics at the same time. For example, to monitor queues, we could see how many queues have messages and for example, what's been the delta from last update (if no messages are getting out, processing is most likely stuck). Adding this data to a graph would allow easier visual monitoring also (all message counts to a single graph). Created attachment 767317 [details]
Photoshopped screenshot of proposal
|