[
https://issues.apache.org/jira/browse/ARTEMIS-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Taylor updated ARTEMIS-5406:
---------------------------------
Description:
The issue of requiring to navigate between addresses and queues tabs very
often, even for simple task. Let's say I want to cleanup old queues which are a
left over of a legacy JMS subscription topic. First I have to go to Queues
tab, then order by consumer count, find a queue which has 0 consumers, click on
address name of that queue to ensure that another queue for that address exist,
delete legacy queue, go back into queues tab and repeat all actions for the
next item in the list. This switches tabs at least couple of times.
I think having some kind of limited representation of hierarchy on particular
address or queue page would be very useful, and there will be no need to move
away from the tab. As an example you can see how hierarchy is represented in
RabbitMQ management UI. One queue page with bindings below
[https://pasteboard.co/8jXYZ1bOYSBk.png] , one exchange with all bound queue
[https://pasteboard.co/B1Ln592HA6x7.png] (exchange == address in Artemis terms).
Also
* Address/Queue name in the list should be clickable and go into particular
object overview.
* Various basic operation buttons should be visible and not hidden under
"three dots" menu. Some basic operations, like queue purge, send message, etc.
could appear in the object overview window mentioned above. Now you have to
hunt for those actions partly in Artemis JMX view, partly by clicking three
dots menu.
* Navigating without the tree means clicking very little numbers, such as the
number of queues when navigating from a list of addresses.
* Getting back from the list of queues to the list of addresses is only
possible by clicking the Addresses panel, and that returns me back to page 1.
was:
The issue of requiring to navigate between addresses and queues tabs very
often, even for simple task. Let's say I want to cleanup old queues which are a
left over of a legacy JMS subscription topic. First I have to go to Queues
tab, then order by consumer count, find a queue which has 0 consumers, click on
address name of that queue to ensure that another queue for that address exist,
delete legacy queue, go back into queues tab and repeat all actions for the
next item in the list. This switches tabs at least couple of times.
I think having some kind of limited representation of hierarchy on particular
address or queue page would be very useful, and there will be no need to move
away from the tab. As an example you can see how hierarchy is represented in
RabbitMQ management UI. One queue page with bindings below
[https://pasteboard.co/8jXYZ1bOYSBk.png] , one exchange with all bound queue
[https://pasteboard.co/B1Ln592HA6x7.png] (exchange == address in Artemis terms).
Also
* Address/Queue name in the list should be clickable and go into particular
object overview.
* Various basic operation buttons should be visible and not hidden under
"three dots" menu. Some basic operations, like queue purge, send message, etc.
could appear in the object overview window mentioned above. Now you have to
hunt for those actions partly in Artemis JMX view, partly by clicking three
dots menu.
> Improve Navigation between addresses and queues
> -----------------------------------------------
>
> Key: ARTEMIS-5406
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5406
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Web Console
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Priority: Major
>
> The issue of requiring to navigate between addresses and queues tabs very
> often, even for simple task. Let's say I want to cleanup old queues which are
> a left over of a legacy JMS subscription topic. First I have to go to Queues
> tab, then order by consumer count, find a queue which has 0 consumers, click
> on address name of that queue to ensure that another queue for that address
> exist, delete legacy queue, go back into queues tab and repeat all actions
> for the next item in the list. This switches tabs at least couple of times.
> I think having some kind of limited representation of hierarchy on particular
> address or queue page would be very useful, and there will be no need to move
> away from the tab. As an example you can see how hierarchy is represented in
> RabbitMQ management UI. One queue page with bindings below
> [https://pasteboard.co/8jXYZ1bOYSBk.png] , one exchange with all bound queue
> [https://pasteboard.co/B1Ln592HA6x7.png] (exchange == address in Artemis
> terms).
>
>
> Also
>
> * Address/Queue name in the list should be clickable and go into particular
> object overview.
> * Various basic operation buttons should be visible and not hidden under
> "three dots" menu. Some basic operations, like queue purge, send message,
> etc. could appear in the object overview window mentioned above. Now you have
> to hunt for those actions partly in Artemis JMX view, partly by clicking
> three dots menu.
> * Navigating without the tree means clicking very little numbers, such as
> the number of queues when navigating from a list of addresses.
> * Getting back from the list of queues to the list of addresses is only
> possible by clicking the Addresses panel, and that returns me back to page 1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
![https://pasteboard.co/8jXYZ1bOYSBk.png]](https://pasteboard.co/8jXYZ1bOYSBk.png] ){kind=link}
![https://pasteboard.co/B1Ln592HA6x7.png]](https://pasteboard.co/B1Ln592HA6x7.png] ){kind=link}