[jboss-jira] [JBoss JIRA] (WFLY-6892) Access logging for EJBs

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272448#comment-13272448 ] 

Brian Stansberry commented on WFLY-6892:
----------------------------------------

The management audit log needs to be clearly distinguished from other forms of logging in order to support the RBAC requirement that operations against its management resources can be limited to users in the Auditor role.

This doesn't mean the way it is configured is set in stone. It does mean though that the definition of the resources must be distinct from those of other logging resources, at least to the extent that the definition includes necessary information to identify the resource as being related to management audit logging. Currently what resource patterns are related to management audit logging is hard coded in the RBAC impl.

> Access logging for EJBs
> -----------------------
>
>                 Key: WFLY-6892
>                 URL: https://issues.jboss.org/browse/WFLY-6892
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>    Affects Versions: 10.0.0.Final
>            Reporter: Brad Maxwell
>
> Access logging for EJB requests similar to Web access logging would be very useful.
> Possibly something like:
> {code}
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ...
> [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)