[Bug 169] New: Better introspection into logging setup

http://bugzilla.slf4j.org/show_bug.cgi?id=169 Summary: Better introspection into logging setup Product: SLF4J Version: 1.5.x Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: Implementations AssignedTo: slf4j-dev@qos.ch ReportedBy: jo@durchholz.org I'd like to - have a way to enumerate all SLF4J loggers configured, and - get an event whenever any SLF4J logger has its configuration changed. USE CASE: I could improve SLF4JBridgeHandler with that. I have a situation where I need to set j.u.l. logging to ALL for some loggers to get the information I want, and WARN for other loggers to keep performance to acceptable levels. Currently, I'm forced to configure both slf4j *and* j.u.l. This is error-prone because I have to keep redundant logging configurations, and because the logging levels do not map 1:1. With the enumeration, I could initialize a j.u.l. logger for every configured slf4j logger, at a compatible logging level. With the events, I could keep the j.u.l. configuration in sync with the slf4j configuration. HELPING WITH THE WORK I can contribute the code, but I can't decide where in SLF4J's architecture it should go. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

http://bugzilla.slf4j.org/show_bug.cgi?id=169 --- Comment #1 from Ceki Gulcu <listid@qos.ch> 2010-02-25 12:52:00 --- Hello Joachim, SLF4J loggers cannot be configured. So I am afraid I don't see what you are talking about. What do you mean by configuring an SLF4J logger? -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

http://bugzilla.slf4j.org/show_bug.cgi?id=169 --- Comment #2 from Joachim Durchholz <jo@durchholz.org> 2010-02-25 13:08:15 ---
SLF4J loggers cannot be configured. So I am afraid I don't see what you are talking about. What do you mean by configuring an SLF4J logger?
I mean the configuration as found in logback.xml. I had assumed it can be changed after loading the configuration. Of course, if no such changes are possible, then there's not need for events that relay the changes :) -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

http://bugzilla.slf4j.org/show_bug.cgi?id=169 --- Comment #3 from Ceki Gulcu <listid@qos.ch> 2010-02-25 13:16:32 --- Logback loggers can be dynamically configured while SLF4J loggers cannot. This keeps the SLF4J API simple. I suggest we take this to the logback-dev mailing list. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

http://bugzilla.slf4j.org/show_bug.cgi?id=169 Ceki Gulcu <listid@qos.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |listid@qos.ch Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Ceki Gulcu <listid@qos.ch> 2010-03-06 14:40:24 --- Closing as this is more of a logback issue. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@pixie.qos.ch