[
https://issues.apache.org/jira/browse/ARTEMIS-4498?focusedWorklogId=910346&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910346
]
ASF GitHub Bot logged work on ARTEMIS-4498:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Mar/24 14:35
Start Date: 18/Mar/24 14:35
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4856:
URL:
https://github.com/apache/activemq-artemis/pull/4856#issuecomment-2004087999
@clebertsuconic I agree that everything should be manageable, except perhaps
for some protocol specific queues as you stated.
Since the property "internal" is used to filter weather or not an address or
queue should get exposed for management or not ( as of now ) and said protocol
managers rely on this to filter Advisories for instance, a new property might
be needed to decide if the destination should be manageable or not, instead of
the current "internal" that has other uses, besides deciding manageability.
Since that change would take some more work to implement it is out of scope
for this release, which I 100% agree with.
My interim solution/idea/example is to leave all this logic as is, with the
only change being to manually register management for addresses and queues
under "Notifications, SnF and AMQPMirror(which already ran this for the
queues)". i.e. get management/metrics for the most critical parts for the
upcoming release. This would later be replaced by the aforementioned "proper"
change.
(I don't like doing things that way but I'm weighing it against the
usefulness of these destinations metrics I thought I'd ask at least)
Issue Time Tracking
-------------------
Worklog Id: (was: 910346)
Time Spent: 6.5h (was: 6h 20m)
> 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: 6.5h
> 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)
