[
https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766925#comment-15766925
]
Christopher L. Shannon commented on ARTEMIS-796:
------------------------------------------------
Having an idea of the number of producers and which connections are producers
(and firing events and keeping statistics on creation/destruction) is ideal for
debugging purposes and auditing. This is probably a discussion better had on
the dev list to see what other people think but my opinion is that it is
something worth exploring as I find it useful.
> Add support for advisory messages
> ---------------------------------
>
> Key: ARTEMIS-796
> URL: https://issues.apache.org/jira/browse/ARTEMIS-796
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Christopher L. Shannon
>
> ActiveMQ 5.x supports several advisory messages that are sent when certain
> events happen in the broker. They are described here:
> http://activemq.apache.org/advisory-message.html
> I am proposing that we provide the same advisory messages as described in the
> above documentation. These advisory messages provide a lot of useful
> information for monitoring what is going on with the broker in real time.
> One issue to work out is the protocol to use for the Advisory messages. A
> couple advisory messages are already being sent by the
> OpenWireProtocolManager for OpenWire clients but it may make more sense to
> send these messages at a more central location as the CORE protocol and then
> they can be converted to the correct type of message depending on the client.
> Sub tasks can be created for the different types of advisory messages that
> need to be added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
