[
https://issues.apache.org/jira/browse/ARTEMIS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336400#comment-16336400
]
ASF GitHub Bot commented on ARTEMIS-1623:
-----------------------------------------
Github user pgfox commented on the issue:
https://github.com/apache/activemq-artemis/pull/1796
@jbertram , @michaelandrepearce Thanks for reviewing this PR. I will try
to implement all the above suggestions.
on the DEBUG vs. INFO I will make it clearer in the docs; there is a
before/after on most of the plugin events . For INFO I log a slightly reduced
log in the "after" point. For DEBUG I log a more detailed entry before and
after.
I will try to follow the established pattern for the LOG codes; create an
interface LoggingActiveMQServerPluginLogger that extends the BasicLogger. It
there any restriction on the 2 digit Logger Code I use - I think "83" is the
last number currently used so I guess "84" would be ok? Or is there a pattern
to choosing that value?
> create an ActiveMQServerPlugin for logging various broker events
> -----------------------------------------------------------------
>
> Key: ARTEMIS-1623
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1623
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.4.0
> Reporter: Pat Fox
> Priority: Minor
>
> create an implementation of ActiveMQServerPlugin for logging various broker
> events , consumer created, message delivered etc. This should be configurable
> to log only events user is interested in.
> Similar functionality to the ActiveMQ 5.x loggingBrokerPlugin.
> http://activemq.apache.org/logging-interceptor.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
