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

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

Commit 8a04ee07de8a7c863daf37a07a1176131151caa0 in activemq-artemis's branch 
refs/heads/master from Andy Taylor
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=8a04ee0 ]

ARTEMIS-2648 - audit logging improvements

https://issues.apache.org/jira/browse/ARTEMIS-2648


> Improve the Audit logging capabilities
> --------------------------------------
>
>                 Key: ARTEMIS-2648
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2648
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Andy Taylor
>            Assignee: Andy Taylor
>            Priority: Major
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> This will improve the current audit logging feature. currently there are 2 
> loggers which are very verbose so this will add a 3rd which focus mainly 
> around access to resources that a console user or a jmx client may use. Also 
> currently no success/failure is logged only entry points in methods, this new 
> logger will log success or failure.
> Here is a list of the improvements:
>  * New Resource logger added
>  ** This will log more resource related access from JMX/console mainly around 
> creation of resources and access to these resource
>  ** It will be enabled independently of the other loggers
>  * Message audit  log will be changed to be configurable independently not 
> with base audit log, and the new resource logger will also be configurable 
> independently.
>  * Add the ability to capture the remote address of the calling client 
> whether it be through JMX/console or a normal Netty connection
>  * Add the ability to capture authentication success or failure from the 
> console
>  
>  * Add the ability to log failures to JMX mbeans in the authentication 
> process.
>  
> Also tidy up the current logger codes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to