[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767048#comment-15767048 ] Christopher L. Shannon commented on ARTEMIS-796: Yeah that's fine to close this if you want to extend the notification API and track it somewhere else. I suppose we should create a new JIRA to track the enhancement? > 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767036#comment-15767036 ] clebert suconic commented on ARTEMIS-796: - So, can I close these as won't fix, given we already have support for management? > 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767033#comment-15767033 ] clebert suconic commented on ARTEMIS-796: - Producer is a client's object. Some protocols will inform the server the server when a producer was created.. some won't. (MQTT for instance won't as far as I remember). We can certainly add events for producer created on existing protocols, and extend the Management events for that on the protocols that will support it, but i wouldn't change core for that... as that will only bring a massive task in place with little benefit beyond showing when an event, that could be replaced by when the first message is sent. I will close this JIRA since we have management in place at Artemis, and I don't think we should implement the exact same API, as I said I'm more interested in investing the time on new things... Feel free to open the management event for created producers JIRA (on the existing protocols). > 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765439#comment-15765439 ] clebert suconic commented on ARTEMIS-796: - I think it will be too hard to be done..I'm not sure about the benefit though. > 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765212#comment-15765212 ] Christopher L. Shannon commented on ARTEMIS-796: Yea that is another issue I was going to bring up. Producer tracking is very useful in many cases. Right now it can only really be done on the first message send but it would be better to be able to track the producer when it is created by the JMS API call if using JMS. I don't know think it would be that hard to add but would unfortunately require a change to the protocol and a new packet type to be sent on producer creation. > 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765113#comment-15765113 ] clebert suconic commented on ARTEMIS-796: - There's no producer in Artemis server core. Some protocols will have it.. but nothing on the Server supporting that. Producer might be a bit difficult, it's basically a serverSend(Address). > 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569185#comment-15569185 ] Christopher L. Shannon commented on ARTEMIS-796: Adding a depends upon link to ARTEMIS-780 as that will be necessary for topic advisories. > 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)
[jira] [Commented] (ARTEMIS-796) Add support for advisory messages
[ https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569179#comment-15569179 ] Christopher L. Shannon commented on ARTEMIS-796: My thinking with this is we could use the NotificationListener framework that already exists. We could send notifications for various events in the broker. Some of these events already exists of course such as consumer created, etc. Others need to be added such as new producers. Then we could maybe have some type of Advisory manager that listens for these notifications and fires advisories to the proper destinations. Thoughts? > 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)
