- logback-user - mailman3.qos.ch

Logging "Cross Functional" categories
by Ceki Gülcü 25 Oct '06

25 Oct '06

In a recent post log4j-user list a developer asked whether it was possible for log4j to log differently depending on technical partitions such as web-app as opposed to EJB. The original discussion can be found at: http://marc.theaimsgroup.com/?t=116179536800005&r=1&w=2 A kind soul, namely James Stauffer, suggested filtering based on MDC. Here is an example of how you would do it in logback. ------------------------------------------ package chapter5; import org.slf4j.LoggerFactory; import ch.qos.logback.classic.Logger; import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.classic.MDC; import ch.qos.logback.classic.joran.JoranConfigurator; import ch.qos.logback.core.joran.spi.JoranException; import ch.qos.logback.core.util.StatusPrinter; public class GoMDC { public static void main(String[] args) { Logger logger = (Logger) LoggerFactory .getLogger(GoMDC.class); LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); configurator.doConfigure("mdcFilter.xml"); } catch (JoranException je) { StatusPrinter.print(lc); } logger.debug("I know me " + 0); MDC.put("key", "val"); logger.debug("I know me " + 1); StatusPrinter.print(lc); } ------------------------------------------ Here the associated config file, "mdcFilter.xml". <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="Pattern" value="%-4relative [%thread] %-5level %X{testKey} - %msg%n" /> </layout> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <Name>myFilter</Name> <OnMatch>DENY</OnMatch> <Evaluator class="ch.qos.logback.classic.boolex.JaninoEventEvaluator"> <Name>mdcEvaluator</Name> <Expression>mdc!=null && "val".equals(mdc.get("key"))</Expression> </Evaluator> </filter> </appender> <root> <level value="debug" /> <appender-ref ref="STDOUT" /> </root> </configuration> The above has been tested on logback version 0.5. It will yield the following output. 0 [main] DEBUG - I know me 0 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] |-INFO in ch.qos.logback.core.joran.action.NestedComponentIA - is dmmed applicable for /configuration/appender/filter |-INFO in ch.qos.logback.core.joran.action.NestedComponentIA - Pushing component <filter> on top of the object stack. |-INFO in ch.qos.logback.core.joran.action.NestedComponentIA - is dmmed applicable for /configuration/appender/filter/Evaluator |-INFO in ch.qos.logback.core.joran.action.NestedComponentIA - Pushing component <Evaluator> on top of the object stack. |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [STDOUT] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT to Logger[root] Note that the last log statement is suppressed, which is the whole point of the exercise. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

1 0

Auto configuration within unit tests
by Simon BRANDHOF 24 Oct '06

24 Oct '06

Hello, Auto-configuration is very useful. No more explicit initialization. The configuration file is automatically loaded from the classpath thanks to naming convention (for example "log4j.xml" or future "logback.xml"). Logback does not manage yet this feature, but I think it is currently in development. I wish Logback resolves a common need I have with log4j : autoconfiguration within unit tests. The idea is to have a configuration file specific to unit tests (for example with DEBUG levels) without intrusive initialization parameters (Java code, system property, ...). The are only two solutions with log4j : 1/ manage files ordering into the classpath. The unit test log4j.xml precedes the "official" log4j.xml. 2/ have only the unit test log4j.xml into the classpath Those solutions are not so simple to set with tools like maven or eclipse. For example Maven 2 sets the test classpath with the directories src/main/resources then src/test/resources. And no way for me to change the default behaviour ! Here is a draft of solution. Logback loads a file named logback-test.xml instead of logback.xml if the classpath contains a class from the package junit.framework or org.testng. Is it possible ? Do you have any suggestions ? Simon

2 1

What's the benfits of using Logback over Log4j?
by Wesslan 24 Oct '06

24 Oct '06

I've just looked through the docs on your site (http://logback.qos.ch/shortIntro.html) I'm interested in the benefits of using Logback over Log4j but I can't find anything about this in the docs. Cheers

2 1

[ANN] Release 0.4
by Sebastien Pennec 09 Oct '06

09 Oct '06

October 9th, 2006 - Release of logback 0.4 Version 0.4 for all three logback modules is now available. This release offers a much improved access module, with specific implementations for Jetty and Tomcat servers. Documentation was also added to show how to integrate logback access with Jetty. Outside of the access module, several appenders and layouts have been added or improved. The error reporting of logback is also improved, prompting the user with a link to an online page presenting possible reasons for the error. A joran documentation was added, with examples in the core module. You can download the modules, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://logback.qos.ch/mailinglist.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

1 0

Re: What's the benfits of using Logback over Log4j?
by Ceki Gülcü 26 Sep '06

26 Sep '06

Hello, Logback is a rewrite of log4j based on the lessons learned during the years. Logback has a smaller memory footprint and is faster by a wide margin. It has much better error reporting capability and is generally more robust. Logback has support for markers which enables capabilities not found elsewhere. We will be documenting these capabilities in the near future. Just as imporantly, logback`s access module supports Tomcat and Jetty. Thus, many of the logging capabilites offered by the classic module are also available for http access logging. I hope this anwers your question, -- -- Ceki Gülcü For log4j documentation consider "The complete log4j manual" http://www.qos.ch/shop/products/eclm/

1 0

What is the log4j.properties file equivalent for logback?
by Newcomb, Michael-P57487 22 Sep '06

22 Sep '06

Or, do I really have to do this: Logger logger = LoggerFactory.getLogger(MyAppWithConfigFile.class); LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); configurator.doConfigure(args[0]); Thanks, Michael

2 1

RE: [LOGBack-user] slf4j simple logger
by Ceki Gülcü 21 Sep '06

21 Sep '06

Actually, Jetty (the servlet container) uses it as its default logging system. They do not want debug statements to appear on the console. It is getting late. I'd like to rethink this with a clear head. At 10:45 PM 9/13/2006, Newcomb, Michael-P57487 wrote: >I was assuming slf4j-simple.jar would be used mostly by library developers >who don't want to fool around with including log4j/logback/jdk14 etc... >That is what I would like to use it for, but now I will have to create a >custom binding (or include one of the above packages) to see debug during >my tests? > >I will create the binding if necessary, but does it make sense to create a >slf4j-simple-debug.jar or something? > >Thanks, >Michael -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

2 1

Unable to use RollingFileAppender
by Samuel Doyle 15 Sep '06

15 Sep '06

Hello, I'm new to logback but read your documentation, I an not receiving any output to my logfile. Here is my configuration file, following this is the output from logback to the console. The only thing I notice is a warning about a TriggerPolicy. If this is the case do you have example syntax? --- <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <param name="append" value="true"/> <param name="MaxBackupIndex" value="1"/> <param name="file" value="/tmp/bitran.log"/> <param name="MaxFileSize" value="5MB"/> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%d [%-15.15t] %-5p %-30.30c{1} - %m%n"/> </layout> </appender> <logger name="org.accma.concentrator.services.bitran.BiTranService" additivity="false"> <level value="debug"/> <appender-ref ref="bitranlog"/> </logger> <root> <level value="debug" /> <appender-ref ref="bitranlog" /> </root> </configuration> --- Here is console output when using LoggerStatusPrinter: --- startElement [configuration] startElement [appender] startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@8c5ea2 startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@198defc startElement [layout] startElement [param] startElement [logger] startElement [level] startElement [appender-ref] startElement [root] startElement [level] startElement [appender-ref] INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch .qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from t he object stack INFO in ch.qos.logback.classic.joran.action.LevelAction - org.accma.concentrator.services.bitran.Bi TranService level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[org.accma.concentrator.services.bitran.BiTranService] INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[root] Thanks, S.D.

3 8

Re: [LOGBack-user] slf4j simple logger
by Ceki Gülcü 13 Sep '06

13 Sep '06

Michael, The simple binding (slf4j-simple.jar) has always dropped logging request of level debug. It's now the expected behavior of that binding. You could easily modify it to log debug requests as well. Even better, create your own binding. Any of the above acceptable to you? At 03:28 PM 9/13/2006, Newcomb, Michael-P57487 wrote: >This logger should default to all levels on > >Thanks, >Michael -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

2 1

slf4j simple logger
by Newcomb, Michael-P57487 13 Sep '06

13 Sep '06

This logger should default to all levels on... Thanks, Michael

1 0