ASF GitHub Bot commented on ARTEMIS-1799:

Github user cshannon commented on the issue:

    I don't understand the confusion.  That call just calls off to any 
registered plugins if they exist.  This commit is a brand new plugin that 
implements the afterDeliver call and fires off a notification. But it only 
fires off that notification if the flag in the plugin is set to true.

> 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

Reply via email to