[
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=913642&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-913642
]
ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Apr/24 08:05
Start Date: 09/Apr/24 08:05
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4856:
URL:
https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2044391474
@clebertsuconic this doesn't quite do it for me as the change still leaves
out management and metrics for the internal queues. In my use case I'm
primarily looking for metrics on the clusters SnF queues as well as the
notification queues.
Perhaps the servers `createQueue` could get overloaded with a variant that
inhibits creation of management objects that can be used for the relevant MQTT
and OpenWire destinations?
Issue Time Tracking
-------------------
Worklog Id: (was: 913642)
Time Spent: 7h (was: 6h 50m)
> Enable management for internal addresses & queues
> -------------------------------------------------
>
> 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: 7h
> 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)
