Skip to end of metadata
Go to start of metadata
Since the logging subsystem changed in JBoss AS7, the below extension does not work Teiid 8.1. This feature is fixed in Teiid 8.2

The Teiid system provides a wealth of information using logging. To control logging level, contexts, and log locations, you should be familiar with container's standalone.xml or domain.xml configuration fileand check out "logging" subsystem. Refer to the Administrator Guide for more details about different Teiid contexts available. Refer to http://logging.apache.org/log4j/ for more information about log4j.

If you want a custom appender, follow the Log4J directions to write a custom appender. Refer to the instructions at http://logging.apache.org/log4net/release/faq.html. If you develop a custom logging solution, the implementation jar should be placed as a jar in "org.jboss.teiid" module and define its name in the module.xml file as part of the module.

Command Logging API

If you want to build a custom appender for command logging that will have access to log4j "LoggingEvents" to the "COMMAND_LOG" context, the appender will receive a message that is an instance of org.teiid.logging.CommandLogMessage. The relevant Teiid classes are defined in the teiid-api-7.6.jar. The CommmdLogMessage includes information about vdb, session, command sql, etc. CommandLogMessages are logged at the DEBUG level.

Sample CommandLogMessage Usage

Audit Logging API

If you want to build a custom appender for command logging that will have access to log4j "LoggingEvents" to the "org.teiid.AUDIT_LOG" context, the appender will receive a message that is an instance of org.teiid.logging.AuditMessage. The relevant Teiid classes are defined in the teiid-api-7.6.jar. The AuditMessage includes information about user, the action, and the target(s) of the action. AuditMessages are logged at the DEBUG level.

Sample AuditMessage Usage
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.