[
https://issues.jboss.org/browse/TEIID-2402?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-2402 at 2/28/13 7:45 PM:
----------------------------------------------------------------
I've made the session id and vdb name/version available in the MDC as teiid-session
and teiid-vdb respectively. To use those values the logging extension would have to
access org.jboss.logging.MDC or a standard logger could use a format pattern that included
the mdc keys - i.e. {code}%X{teiid-session}{code} - see also
https://community.jboss.org/thread/161799
A caveat is that this will not currently work with the Java logger (used for embedded) as
Java logging lacks an mdc concept. We could enable the functionality by leveraging JBoss
logging in embedded or by rolling our own support.
Does this seem sufficient or should we add the user name as well?
was (Author: shawkins):
I've made the session id and vdb name/version available in the MDC as
teiid-session and teiid-vdb respectively. To use those values the logging extension would
have to access org.jboss.logging.MDC or a standard logger could use a format pattern that
included the mdc keys - i.e. %X{teiid-session} - see also
https://community.jboss.org/thread/161799
A caveat is that this will not currently work with the Java logger (used for embedded) as
Java logging lacks an mdc concept. We could enable the functionality by leveraging JBoss
logging in embedded or by rolling our own support.
Does this seem sufficient or should we add the user name as well?
Enable session context be available in the all log messages
-----------------------------------------------------------
Key: TEIID-2402
URL:
https://issues.jboss.org/browse/TEIID-2402
Project: Teiid
Issue Type: Enhancement
Components: Common
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 8.3
Inject work context into all the Teiid based messages such that a custom logger can be
written to filter based on logged in user, vdb
--
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