[
https://issues.apache.org/jira/browse/SLING-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-4840.
------------------------------------
Resolution: Fixed
Done in http://svn.apache.org/r1692218
Log config now support a log level {{DEFAULT}}. If the level is set to
{{DEFAULT}} then for those loggers the config would remain but the logger state
would be set to default
# additivity -> true
# level -> null thus they inherit the level from parent
# no appender registered
This would allow the Logger config to remain present but would not have any
affect on runtime logging behaviour thus effectively disabling that logger
config
> Provide an option to disable a set of logger via config
> -------------------------------------------------------
>
> Key: SLING-4840
> URL: https://issues.apache.org/jira/browse/SLING-4840
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: Commons Log 4.0.4
>
>
> Logsupport Web Console plugin simplifies configuring the loggers with content
> assist. At times for debugging purpose users routes logs from set of loggers
> to a specific file.
> Post debugging these loggers have to be deleted. It would helpful if UI
> provides an option to turn off the loggers i.e. have the config be there but
> not applied
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
