- logback-user - mailman3.qos.ch

FileAppender : change log filename at runtime with a datePattern
by Alessio Pollero 04 Dec '11

04 Dec '11

Hi to all, i just switched to logback from log4j now and i want to change at runtime some settings contained in the logback.xml configuration file. I have a logback.xml configuration file that looks like the following : <configuration> <property name="defaultPattern" value="%d{dd/MM/yyyy HH:mm:ss.SSS} [%thread] %-5level - %msg%n" />  <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <target>System.err</target> <filter class="com.aleroot.ErrOutFilter" /> <encoder> <pattern>${defaultPattern}</pattern> </encoder> </appender> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>aleroot.log</file> <append>true</append> <encoder> <pattern>${defaultPattern}</pattern> </encoder> </appender>  <root level="debug"> <appender-ref ref="FILE" /> <appender-ref ref="CONSOLE"/> </root> <logger name="mainLogger" level="debug"> <appender-ref ref="FILE" /> <appender-ref ref="CONSOLE"/> </logger> </configuration> i want to change the file property of the FILE appender at runtime and add a DatePattern to the filename, i've tried with this code : LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); ch.qos.logback.classic.Logger logbackLogger = lc.getLogger("mainLogger"); FileAppender<ILoggingEvent> fileAppender = (FileAppender<ILoggingEvent>) logbackLogger.getAppender("FILE"); if(fileAppender != null) { fileAppender.stop(); fileAppender.setFile("aleroot-ddMMyyyy.log"); fileAppender.setContext(lc); fileAppender.start(); } The problem is that the file aleroot.log is created anyway also if i have changed the filename, furthermore i get another file that is named exactly : aleroot-ddMMyyyy.log while i want to have a filename like aleroot-04122011.log . How can i achieve that ? Is there a settings to avoid that the log file will be created at the LoggerFactory.getLogger("mainLogger") call ? I want that the log file will be created only the first time that i write into the log files, there is no need to create an empty log file . The log file should be created the first time that i log something to the log, for example at the first logger.debug("Something.log") , Is there a settings to achieve that ? Thanks.

1 0

Logback configuration using Groovy
by Yuvi 29 Nov '11

29 Nov '11

Hi, If i use logback.groovy to configure logback, i have to have groovy jar in classpath, else it fails. However logback dependencies page (http://logback.qos.ch/dependencies.html) doesn't speak about this. Am i missing something here? -Yuvaraj -- View this message in context: http://old.nabble.com/Logback-configuration-using-Groovy-tp32880402p3288040… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Re: [logback-user] EventLogger usage
by Yuvaraj Vanarase 29 Nov '11

29 Nov '11

Thanks Ralph. It was good explanation. Regards, Yuvaraj Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 15 Best IT Employers for 5 consecutive years (link). - Celebrating 10 Years! -----Original Message----- From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of logback-user-request(a)qos.ch Sent: Monday, November 28, 2011 10:22 PM To: logback-user(a)qos.ch Subject: Logback-user Digest, Vol 2, Issue 40 Send Logback-user mailing list submissions to logback-user(a)qos.ch To subscribe or unsubscribe via the World Wide Web, visit http://mailman.qos.ch/mailman/listinfo/logback-user or, via email, send a message with subject or body 'help' to logback-user-request(a)qos.ch You can reach the person managing the list at logback-user-owner(a)qos.ch When replying, please edit your Subject line so it is more specific than "Re: Contents of Logback-user digest..." Today's Topics: 1. EventLogger usage (Yuvaraj Vanarase) 2. Re: EventLogger usage (Ralph Goers) 3. Substituting class/method names in logback log files with original names when deploying obfuscated code (Christopher BROWN) 4. Re: Substituting class/method names in logback log files with original names when deploying obfuscated code (Chris Pratt) ---------------------------------------------------------------------- Message: 1 Date: Mon, 28 Nov 2011 06:19:23 -0600 From: Yuvaraj Vanarase <yuvaraj.vanarase(a)synechron.com> To: "logback-user(a)qos.ch" <logback-user(a)qos.ch> Subject: [logback-user] EventLogger usage Message-ID: <5669C1899552264CA699F54A78E534D40F948B34F2(a)DFW1MBX18.mex07a.mlsrvr.com> Content-Type: text/plain; charset="us-ascii" Hi, Not able to understand the connection between MDC and EventLogger (slf4j). What I understood is, instead of doing separate log requests, one can populate EventData object and log the object by EventLogger. Anybody could illustrate this concept please? Regards, Yuvaraj Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 15 Best IT Employers for 5 consecutive years (link<http://www.synechron.com/news/news_best_employer_sep2011.htm>). - Celebrating 10 Years!

1 0

EventLogger usage
by Yuvaraj Vanarase 28 Nov '11

28 Nov '11

Hi, Not able to understand the connection between MDC and EventLogger (slf4j). What I understood is, instead of doing separate log requests, one can populate EventData object and log the object by EventLogger. Anybody could illustrate this concept please? Regards, Yuvaraj Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 15 Best IT Employers for 5 consecutive years (link<http://www.synechron.com/news/news_best_employer_sep2011.htm>). - Celebrating 10 Years!

2 1

How to retrieve parent logger?
by Christian Migowski 25 Nov '11

25 Nov '11

Hi, how can I get the parent logger of a given logger in logback? What I want is to retrieve a list of all effective appenders on a given logger, I suppose therefore I need to call iteratorForAppenders() on the logger itself as well as on all parents, right? log4j had logger.getParent() but I cannot find something similar in logback. thanks in advance, best regards, christian! P.S. what I really want is to port this from log4j to logback, it gets a list of all logfiles attached to a given logger: org.apache.log4j.Logger testlogger = org.apache.log4j.Logger.getLogger(log.getName()); ArrayList<String> recvdMsg = new ArrayList<String>(); while (testlogger != null && testlogger instanceof org.apache.log4j.Logger) { Enumeration<Appender> loggers = testlogger.getAllAppenders(); while (loggers.hasMoreElements()) { Appender x = loggers.nextElement(); if (x instanceof FileAppender) { String filename = ((FileAppender) x).getFile(); if (filename != null) { File logfile = new File(filename); try { recvdMsg.add(logfile.getCanonicalPath()); } catch (IOException e) { //so we don't add the path, thats enough handling } } } } testlogger = (org.apache.log4j.Logger) testlogger.getParent(); }

1 1

tomcat internal logs + logback app logs in one file
by Rohi Fadlun 23 Nov '11

23 Nov '11

Hi, I'm working on a project that needs to have tomcat internal logs and application logs in one file. At the moment I'm using logback to log tomcat internals with grgrzybek's project (https://github.com/grgrzybek/tomcat-slf4j-logback) in which there is a modified version of juli that redirects calls to logback - if I didn't understand wrong) and it works really fine, I just modified a bit its logback configuration so that all 4 loggers refer to only 1 appender; for my application I'm using a simple configuration that outputs to a file, uses a size and time based rolling policy: <configuration scan="true" scanPeriod="30 seconds" > <appender name="MYAPP-TRIAL" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp.log</file> <append>true</append> <encoder> <charset>utf-8</charset> <pattern>MYAPPLICATION TRIAL %d{HH:mm:ss.SSS} %-5level {%thread} [%logger{40}] : %msg%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp-%d{yyyyMMdd}-%i.log.zip</fileNamePattern> <maxHistory>60</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>10MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> </appender> <root level="info"> <appender-ref ref="MYAPP-TRIAL" /> </root> </configuration> Now I know there are 2 different approaches 1 - using prudent: but i can't use it because of its limitation with the rolling policy (in fact it doesn't work at all with this configuration) 2 - using <include> tag importing the appender from tomcat/conf/logback.xml (I followed logback manual, referencing the appender and so on). This approach doesn't work either, I think because the class used in the tomcat/conf/logback.xml is not logback's classic one: <included> <appender name="MYAPPTEST" class=" org.apache.juli.logging.ch.qos.logback.core.rolling.RollingFileAppender"> <file>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp.log</file> <encoder> <charset>utf-8</charset> <pattern>%d{HH:mm:ss.SSS} %logger{0} {%thread} %level : %msg%n</pattern> </encoder> <rollingPolicy class="org.apache.juli.logging.ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp-%d{yyyyMMdd}-%i.log.zip</fileNamePattern> <maxHistory>60</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="org.apache.juli.logging.ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>20MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> </appender> </included> Someone got another approach to suggest? or am I making something wrong here? I'm using tomcat x64 7.0.22, logback 1.0.0, Win7 x64 Thanks a lot! Rohi

1 0

Groovy-config fails without outside code noticing.
by Endre Stølsvik 18 Nov '11

18 Nov '11

Hi! This groovy-file ...: import ch.qos.logback.classic.PatternLayout import ch.qos.logback.core.ConsoleAppender import ch.qos.logback.core.encoder.LayoutWrappingEncoder appender("STDOUT", ConsoleAppender) { encoder(LayoutWrappingEncoder) { layout(PatternLayout) { pattern = "%d{HH:mm:ss.SSS} [%thread] %-5level %logger{55}.%M.%L - %msg%n" } } } root(ALL, ["STDOUT"]) ... apparently crashes the configuration as such: Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: groovy.lang.MissingPropertyException: No such property: ALL for class: Script1 at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at Script1.run(Script1.groovy:13) at Script1$run.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112) at ch.qos.logback.classic.gaffer.GafferConfigurator.run(GafferConfigurator.groovy:59) at ch.qos.logback.classic.gaffer.GafferConfigurator$run.callCurrent(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141) at ch.qos.logback.classic.gaffer.GafferConfigurator.run(GafferConfigurator.groovy:37) at ch.qos.logback.classic.gaffer.GafferUtil.runGafferConfiguratorOn(GafferUtil.java:44) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:67) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:279) at XYZ.doLogConfig(XYZ.java:40) at XYZ.main(XYZ:169) * The problem is obviously the not-defined property "ALL". The problem I am reporting is that this isn't caught.* The console-dump happens in the *"We should never get here"* catch block below: void init() { try { try { new ContextInitializer(defaultLoggerContext).autoConfig(); } catch (JoranException je) { Util.report("Failed to auto configure default logger context", je); } StatusPrinter.printInCaseOfErrorsOrWarnings(defaultLoggerContext); contextSelectorBinder.init(defaultLoggerContext, KEY); initialized = true; } catch (Throwable t) { // we should never get here Util.report("Failed to instantiate [" + LoggerContext.class.getName() + "]", t); } } Notice that the StatusManager does not know that the config failed: 13:32:07,643 |-INFO in ch.qos.logback.classic.LoggerContext[Emma logcontext] - Found resource [logback.groovy] at [file:/XYZ/target/classes/logback.groovy] 13:32:08,807 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@2111e072 - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 13:32:08,809 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@2111e072 - Naming appender as [STDOUT] Kind regards, Endre Stølsvik.

2 1

Joran errors I don't understand
by Steve Cohen 17 Nov '11

17 Nov '11

We have this configuration <configuration> ... <conversionRule conversionWord="ourcaller" converterClass="com.whatever.CallerDataConverter" /> <appender name="jms" class="com.whatever.JMSQueueAppender"> <encoder> <pattern>%d %-5p [%t] %ourcaller{1} - %m%n</pattern> </encoder> </appender> <appender name="stdout" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d %-5p [%t] %ourcaller{1} %n - %m%n</pattern> </encoder> </appender> ... ====================================== This configuration produces these errors: 3:21:43,935 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@18:14 - no applicable action for [encoder], current pattern is [[configuration][appender][encoder]] 13:21:43,935 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@19:16 - no applicable action for [pattern], current pattern is [[configuration][appender][encoder][pattern]] The line numbers here refer to the JMSQueueAppender. The console appender which is structured basically identically has no such problem. What is Joran trying to tell me here. It appears to be telling me the pattern I am using, but does not tell me why it finds this objectionable. Thanks.

2 4

How to log FROM an appender?
by Steve Cohen 16 Nov '11

16 Nov '11

We have a custom appender that may itself need to issue logging statements. But placing a logger in such a class causes various exceptions on initialization and loading. So we are resorting to System.out.println for lack of a better solution. I suppose there must be a better way. What would that be?

4 16

Re: [logback-user] Logback-user Digest, Vol 2, Issue 32
by Yuvaraj Vanarase 16 Nov '11

16 Nov '11

Hello Ceki, It would be great if you provide confirmation for your answer below: There is a serious bug in AccessViewStatus servlet. That is probably why you are seeing the 'Could not find status manager' message which will be fixed with the logback next release. Does this also cause the logback-access initialization logs to be absent on console? I mean I wouldn't able to see something like: 21:56:09,921 |-INFO in c.q.lb.access.j.a.ConfigurationAction - Ignoring debug attribute. 21:56:09,921 |-INFO in c.q.lb.core.j.a.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 21:56:09,921 |-INFO in c.q.lb.core.j.a.AppenderAction - Naming appender as [STDOUT] 21:56:10,000 |-INFO in c.q.lb.core.j.a.NestedComponentIA - Pushing component [layout] on top of the object stack. 21:56:10,015 |-INFO in c.q.lb.core.j.a.AppenderAction - Popping appender named [STDOUT] from the object stack 21:56:10,015 |-INFO in c.q.lb.core.j.a.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.access.tomcat.LogbackValve[Catalina] 21:56:10,015 |-INFO in c.q.lb.access.j.a.ConfigurationAction - End of configuration. Because apart from status manager issue, I do not see above initialization log either. Regards, Yuvaraj Date: Wed, 16 Nov 2011 08:02:14 +0100 From: Ceki Gulcu <ceki(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Subject: Re: [logback-user] Using logback access Message-ID: <4EC35FF6.10907(a)qos.ch> Content-Type: text/plain; charset=windows-1252; format=flowed Hello Yuvaraj, Responses inline. On 16.11.2011 07:05, Yuvaraj Vanarase wrote: > Hi, > > I have 2 questions. > > 1. What is logback access exactly. Is it about providing webserver > request information in terms of log. Doesn?t such facility come with web > server itself? (catalina.log for tomcat etc) Yes, web-containers already support access logging. Logback-access provides the same functionality but in addition logback-access is more flexible with much better filtering and rolling capabilities. > 2. I am trying to use logback access with Tomcat, however just not > getting there. It would be great if someone points out any miss-outs. > > Below are details: > > -Tomcat 6.0.33 > > -Logback core 0.9.30 > > -Logback access 0.9.30 > > I have put above logback jars into tomcat jar directory. I have added > ?Valve? configuration in server.xml and as required put the > logback-access.xml in conf directory of tomcat. I referred > http://logback.qos.ch/access.html > > My webapp has single simple servlet that just prints login name on page > which has been input from html login form. This works well however I do > not see any logback initialization logs. When I query > ?AccessViewStatusMessages?, again I do not see any messages except one > *?Could not find status manager?* There is a serious bug in AccessViewStatus servlet. That is probably why you are seeing the 'Could not find status manager' message which will be fixed with the logback next release. > Yuvaraj ------------------------------ _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user End of Logback-user Digest, Vol 2, Issue 32 *******************************************

2 1