[
https://issues.apache.org/jira/browse/ARTEMIS-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-4498:
------------------------------------
Description: Originally "internal" addresses and queues weren't meant to be
exposed via management. However, due to a bug where the "internal" attribute of
a queue was not persisted properly such queues have been exposed to management
for a long time. This was fixed via ARTEMIS-4396, but users still want the
ability to manage internal queues because it is extremely helpful when trying
to troubleshoot issues. Therefore, this functionality should be configurable.
(was: This was enabled by default in previous versions of the broker and where
quite good for troubleshooting and observability purposes)
> Expose internal queues for management and observability
> -------------------------------------------------------
>
> Key: ARTEMIS-4498
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4498
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Originally "internal" addresses and queues weren't meant to be exposed via
> management. However, due to a bug where the "internal" attribute of a queue
> was not persisted properly such queues have been exposed to management for a
> long time. This was fixed via ARTEMIS-4396, but users still want the ability
> to manage internal queues because it is extremely helpful when trying to
> troubleshoot issues. Therefore, this functionality should be configurable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
