[teiid-issues] [JBoss JIRA] Commented: (TEIID-667) Simplify "Command Logging"
[
https://jira.jboss.org/jira/browse/TEIID-667?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-667:
------------------------------------
By default the messages are now in the main log file. User can configure the
"log4j.properties" file to stream to separate file by configuring a
FileAppender.
Database Appender implementation is up to the user, as Teiid not going to support any
database dependency. To write a database appender, configure the
"log4j.properties" file to add a category
org.teiid.COMMAND_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.CommandLogMessage". Cast your message to this class,
and extract the variables from the object and write to your database destination. The
schema can be inferred from the type of variables user wants to log from the message
object.
Simplify "Command Logging"
--------------------------
Key: TEIID-667
URL: https://jira.jboss.org/jira/browse/TEIID-667
Project: Teiid
Issue Type: Task
Components: Common
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
Currently the command logging is defined by Tracking Service and it can be extended by
the user through "CommandLoggerSPI". This is verbose, Command Logger should be
no different than any other logging, only that the messages are sent to a specific
context. User should have ability to stream to Teiid log file, or can add appender to
separate them from main log file. File based appender should 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