[
https://issues.jboss.org/browse/WFLY-3164?page=com.atlassian.jira.plugin....
]
Kabir Khan commented on WFLY-3164:
----------------------------------
One issue is that we currently only handle two kinds of 'events':
-controller audit events
-jmx audit events
There is talk of supporting more events like authorization done, connection opened etc. so
what we come up with needs to be flexible enough to handle those, and possibly more events
like that in the future. The concern being if a user implements a custom formatter for
9.0.0, and we add some more events for 9.1.0 their custom formatter should still work
although more events were added for 9.1.0.
A half-baked idea, take with a pinch of salt, is that perhaps for the custom formatter we
could have a reference back to one of the WF provided handler types as a
'fallback' for events not handled by the custom formatter.
Create customized Audit Logger
------------------------------
Key: WFLY-3164
URL:
https://issues.jboss.org/browse/WFLY-3164
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Kabir Khan
Assignee: Kabir Khan
Labels: EAP
Fix For: 9.0.0.CR1
Some users want to have a single line audit log formatter. I think it would be better to
have the ability to add your own formatter from a module, something along the lines of:
{code}
<custom-formatter code="org.blah.MyCustomFormatter"
module="org.blah/mymodule">
<property name="layout">...</property>
<property name="propB">...</property>
</custom-formatter>
{code}
We'd need an SPI, and a slight reworking of the audit log internals. In any case
doing this will put us in a better position to provide the single line logger if this
proposal is not acceptable to our users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira