[ 
https://issues.apache.org/jira/browse/ARTEMIS-4743?focusedWorklogId=916116&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-916116
 ]

ASF GitHub Bot logged work on ARTEMIS-4743:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Apr/24 03:11
            Start Date: 24/Apr/24 03:11
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on code in PR #4905:
URL: https://github.com/apache/activemq-artemis/pull/4905#discussion_r1577182698


##########
docs/user-manual/versions.adoc:
##########
@@ -32,6 +32,8 @@ However, connections will no longer be pooled regardless of 
the configuration.
   ** This was done in an attempt to allow administrators to act when things 
are not working as expected, to get metrics on these objects and allow more 
transparency for the broker.
   ** this includes all Openwire Advisor queues and addresses, MQTT internal 
objects, Cluster Store and Forward (SNF) Queues, Mirror SNF.
   ** You may want to revisit authorizations if you mean to control access to 
certain users on the web console.
+* The CLI operation `./artemis queue stat` has its output improved and 
updated. If you parse the previous output you will see differences in the 
output.

Review Comment:
   @erwindon as promised ^^^
   let me know if you can think of a better text here or anywhere else 





Issue Time Tracking
-------------------

    Worklog Id:     (was: 916116)
    Time Spent: 2h 10m  (was: 2h)

> Improve CLI Queue Stat Output: Split lines and include internal queue 
> attribute
> -------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4743
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4743
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.33.0
>            Reporter: Clebert Suconic
>            Priority: Major
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to