[
https://issues.apache.org/jira/browse/AMQ-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225895#comment-14225895
]
Lionel Cons commented on AMQ-4237:
----------------------------------
FWIW, here are the patterns we use in our monitoring. They only return
destinations, not consumers:
{code}
org.apache.activemq:type=Broker,brokerName=*,destinationType=Topic,destinationName=*
org.apache.activemq:type=Broker,brokerName=*,destinationType=Queue,destinationName=*
{code}
> JMX ObjectNames do not follow JMX Best practices to use a Hierarchical format
> -----------------------------------------------------------------------------
>
> Key: AMQ-4237
> URL: https://issues.apache.org/jira/browse/AMQ-4237
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Reporter: Rob Davies
> Assignee: Rob Davies
> Fix For: 5.8.0
>
>
> The Current JMX ObjectNames result in a disjointed view from JConsole of the
> managed objects and services of the ActiveMQ Broker. By following best
> practices, it will be easier to find and monitor all the endpoints associated
> with a Destination - for example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
