[ 
https://issues.apache.org/jira/browse/ARTEMIS-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432526#comment-16432526
 ] 

ASF subversion and git services commented on ARTEMIS-1799:
----------------------------------------------------------

Commit 4795f7c6d0e9242c2fc1f364b1cc025a1ce037b6 in activemq-artemis's branch 
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=4795f7c ]

ARTEMIS-1799 - Add a NotificationActiveMQServerPlugin

Adds a new plugin that will support sending new types of notifications
for broker events which will allow enhanced broker monitoring


> Create a NotificationActiveMQServerPlugin to publish new types of 
> notifications
> -------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1799
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1799
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 2.5.0
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 2.6.0
>
>
> For monitoring the broker it would be helpful to support publishing of new 
> notification types that can be listened for.  This is similar to the 
> advisories that ActiveMQ 5.x supports.
> By adding this functionality to a plugin it can be easily enabled/disabled by 
> the user through configuration and fine tuned to a user's requirements.  For 
> this initial Jira I'm proposing adding the following notification types: 
> connection creation/destroyed events, session created/closed events, address 
> added/removed events, delivered messages, and expired messages.
> It will be easy to enhance these new notifications in future Jiras (ie add 
> more properties to the messages if necessary) and also easy to add new 
> notifications to the plugin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to