[teiid-issues] [JBoss JIRA] Resolved: (TEIID-668) Simplify "Audit Logging"
[
https://jira.jboss.org/jira/browse/TEIID-668?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-668.
--------------------------------
Resolution: Done
Assignee: Ramesh Reddy (was: Steven Hawkins)
Except for (c) all the above should be now possible. Database implementation (appender) is
up to the user right now, as Teiid is getting out of the database dependency. To write a
database appender, configure the "log4j.properties" file to add a category
org.teiid.AUDIT_LOG
at INFO level, then write a Log4J appender that writes to a database. The message object
you can expect to see on your overridden appender's log call is
"com.metamatrix.dqp.service.AuditMessage". Cast your message to this class, and
extract the variables from the object and write to your database destination.
Simplify "Audit Logging"
------------------------
Key: TEIID-668
URL: https://jira.jboss.org/jira/browse/TEIID-668
Project: Teiid
Issue Type: Task
Components: Common
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
Currently "Audit" logging, is managed by a separate logging framework, this
should be no different than logging in Teiid, except that these messages should be placed
a well known context. By default the messages can be streamed to Teiid's main log file
at INFO level, however there must be an way to user to send these messages to a separate
destination. A File based destination must be supported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira