[
https://issues.jboss.org/browse/AS7-2318?page=com.atlassian.jira.plugin.s...
]
Doug Grove commented on AS7-2318:
---------------------------------
Thanks for that, it is a better description. So we have the situation described,
literally every day, in GSS. "Logging isn't working". And we know to tell
the customer that the threshold is set to INFO and it needs to be lowered.
We also have the case where in normal operation the customer will set the threshold to
WARN. They don't care about INFO logging and want the log files to be concise. When
they have a problem, they will then set the threshold to something lower.
In either case, a visual indication on the web console for the "active" (for
want of a better word) loggers would be useful.
Do not set the threshold (level) on the FILE appender by default
----------------------------------------------------------------
Key: AS7-2318
URL:
https://issues.jboss.org/browse/AS7-2318
Project: Application Server 7
Issue Type: Enhancement
Components: Logging
Affects Versions: 7.0.2.Final
Reporter: Jim Tyrrell
Assignee: jaikiran pai
Labels: eap6-ux
If the root logger is set to info, it will grab all of the log messages and not allow for
a debug logging later on in the hierarchy. This is a support issue as they often have
users turn on more logging, but the user has not "turned off" the root logger so
it is not able to grab any debug messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira