- logback-user - mailman3.qos.ch

Groovy 1.8.x
by Pier-Luc Caron St-Pierre 01 Mar '12

01 Mar '12

Hello, On one of our system, we have the following little problem with groovy. http://jira.codehaus.org/browse/GROOVY-3495 Since before this day, groovy was only use for logback. So the version of groovy is the one used in logback. I was wondering if logback have any plan to upgrade to groovy 1.8.x ? -- Cordialement, Pier-Luc

1 0

Sane solution for centralised logging with logback
by Michael McCarthy 29 Feb '12

29 Feb '12

Hi all, Just working on a solution for centralised logging in our development environment, and it would be good to get some feedback. The solution until this morning was this: - Developers build apps with their own logback.xml inside - These get deployed to jboss. A system property for the logback file kicks in, and the logback file on jboss takes precedence over the application one. This logback file has a gelf appender, and all logging is done centrally. This works perfectly, logback is working well, logback-gelf is working well to. The only problem with it is once more applications are deployed. When looking at logs we suddenly have no idea which app a log is coming from. The change of plan would be to use the contextName. What I was thinking was that the war files get stripped at deploy time, their logback files removed and replaced with a generic one (that has the gelf stuff). This logback config would have a contextName which would be written to on the fly. The war would then get re-assembled and deployed. Any feedback appreciated, the basic goals are that all applications should be logging the exact same way, centrally, and that is should be possible to distinguish which app a log has come from given that multiple apps can be deployed to the same app server. Many thanks :)

1 0

Multiple date patterns in filename pattern
by Chris Lemper 28 Feb '12

28 Feb '12

Hi Logback users! I would like to store daily log files in the format: /logs/%d{yyyy/MM}/app.%d{yyyyMMdd}.log So that the end result is: /logs/2012/02/app.20120228.log That is I would like all daily log files for a given month in a single directory but each log file containing the full date. However, when I configure this filename pattern using ch.qos.logback.core.rolling.TimeBasedRollingPolicy, logback bases the rolling policy only on the first pattern: INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy/MM' from file name pattern '/logs/%d{yyyy/MM}/app.%d{yyyyMMdd}.log'. INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Rollover at start of every month. Is it possible to accomplish this, even by just forcing the rollover to be daily (at midnight) independent of the filename pattern? I have looked through the mailing lists, documentation, and source code and cannot figure out how or if it can be done. Thanks, Chris Lemper

3 2

Is it possible to acces MDC values as properties?
by Stefan Eder 26 Feb '12

26 Feb '12

Hi, applies to Logback classic 1.0.0. Is it possible to acces MDC values as properties like this: <file>${catalina.base}/logs/exchanges/${breadcrumbId}-gsem.log</file> <encoder> <pattern>...</pattern> </encoder> where 'breadcrumbId' is mapped in the MDC. The above example produces a file named breadcrumbId_IS_UNDEFINED-gsem.log. The snippet is used in a sifting appender, but 'breadcrumbId' is not the descriminator. Do I have to use another notation or do I have to implement ch.qos.logback.core.spi.PropertyDefiner? Thanks, Stefan

2 2

class & line conversion words not working
by Chris Cheshire 23 Feb '12

23 Feb '12

I have just upgraded to logback 1.0 (from 0.9.x), and now the conversion words for %class and %line just produce a question mark. My pattern layout is <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger %n%n Class : %class%n Line : %line%n%n%message%n</Pattern> </layout> Prior to the update this was working and now it's not. Everything else in the layout displays as specified, except %class and %line. I do have the java compiler generating debug information too. Any suggestions? Chris

1 2

issues with logback-demo
by Arun Ramakrishnan 23 Feb '12

23 Feb '12

I tried the demo today and ran into the following issues during the jetty:run stage. This is for Maven 3 and Mac OS X. This is the full console output <https://gist.github.com/1889422>to the command "mvn package jetty:run" Here is the first exception thats thrown. ************** 02:43:01 [pool-1-thread-1] INFO ch.qos.logback.demo.LoggingTask - Howdydy-diddly-ho - 99 java.lang.Exception: e at ch.qos.logback.demo.LoggingTask.run(LoggingTask.java:28) [classes/:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [na:1.6.0_29] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [na:1.6.0_29] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [na:1.6.0_29] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [na:1.6.0_29] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [na:1.6.0_29] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [na:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [na:1.6.0_29] 02:43:11 [pool-1-thread-1] INFO ch.qos.logback.demo.LoggingTask - Howdydy-diddly-ho - 199 java.lang.Exception: e at ch.qos.logback.demo.LoggingTask.run(LoggingTask.java:28) [classes/:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [na:1.6.0_29] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [na:1.6.0_29] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [na:1.6.0_29] *************************** System Info ******************************* Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac" *************************************

1 0

Creating logback logger programmatically
by Yusuf Soysal 22 Feb '12

22 Feb '12

Hello everyone, I'm sorry to post this message again, but I have no clue to continue. Is it possible to solve this issue in anyway? By the way, I was able to accomplish this with log4j :( Regards ---------------------- Hello, I have a problem regarding to logback project. My requirement is I have to create log properties dynamically. Let me explain this by an example. My project creates socket communication with external system and it may have multiple sockets. For each socket, I want to have different log files which will contain the messages that is read and sent. To accomplish this, I create the logger for sockets programmatically. Problem is when I want to reconfigure loggers based on logback.xml (by adding scan="true" or by reinitializing the logback), the loggers I created becomes unusable. How can I fixed that or can you advise me another solution? This is my configuration file (logback.xml) <?xml version="1.0" ?> <configuration> <property name="HOME_PATH" value="/data/logs/myapp/" scope="CONTEXT" /> <property name="MYAPP_LOG_FILE" value="myapp.log" /> <property name="MYAPP_ROLLING_TEMPLATE" value="%d{yy-MM-dd}" scope="CONTEXT" /> <property name="MYAPP_OLD_LOG_FILE" value="${MYAPP_LOG_FILE}.%d{yy-MM-dd}" /> <property name="DEFAULT_PATTERN" value="%d{yyyy-MM-dd HH:mm:ss.SSS} [%file:%line] [%level] %msg%n" scope="CONTEXT" /> <appender name="myAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${HOME_PATH}${MYAPP_LOG_FILE}</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${HOME_PATH}${MYAPP_LOG_FILE}.${MYAPP_ROLLING_TEMPLATE}</fileNamePattern> </rollingPolicy> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>${DEFAULT_PATTERN}</pattern> </encoder> </appender> <logger name="com.myapp" level="DEBUG" additivity="false"> <appender-ref ref="myAppender" /> </logger> <root level="OFF"> </root> </configuration> and here you can see how I create loggers programmatically (again, I do this only for socket logs). public static Logger createLogger(String name) { ch.qos.logback.classic.Logger templateLogger = (ch.qos.logback.classic.Logger) LogUtil.getLogger("com.myapp"); LoggerContext context = templateLogger.getLoggerContext(); String logDir = context.getProperty("HOME_PATH"); PatternLayoutEncoder encoder = new PatternLayoutEncoder(); encoder.setPattern(context.getProperty("DEFAULT_PATTERN")); encoder.setContext(context); DefaultTimeBasedFileNamingAndTriggeringPolicy<ILoggingEvent> timeBasedTriggeringPolicy = new DefaultTimeBasedFileNamingAndTriggeringPolicy<ILoggingEvent>(); timeBasedTriggeringPolicy.setContext(context); TimeBasedRollingPolicy<ILoggingEvent> timeBasedRollingPolicy = new TimeBasedRollingPolicy<ILoggingEvent>(); timeBasedRollingPolicy.setContext(context); timeBasedRollingPolicy.setFileNamePattern(logDir + name + ".log." + context.getProperty("MYAPP_ROLLING_TEMPLATE")); timeBasedRollingPolicy.setTimeBasedFileNamingAndTriggeringPolicy(timeBasedTriggeringPolicy); timeBasedTriggeringPolicy.setTimeBasedRollingPolicy(timeBasedRollingPolicy); RollingFileAppender<ILoggingEvent> rollingFileAppender = new RollingFileAppender<ILoggingEvent>(); rollingFileAppender.setAppend(true); rollingFileAppender.setContext(context); rollingFileAppender.setEncoder(encoder); rollingFileAppender.setFile(logDir + name + ".log"); rollingFileAppender.setName(name + "Appender"); rollingFileAppender.setPrudent(false); rollingFileAppender.setRollingPolicy(timeBasedRollingPolicy); rollingFileAppender.setTriggeringPolicy(timeBasedTriggeringPolicy); timeBasedRollingPolicy.setParent(rollingFileAppender); encoder.start(); timeBasedRollingPolicy.start(); rollingFileAppender.stop(); rollingFileAppender.start(); ch.qos.logback.classic.Logger logbackLogger = (ch.qos.logback.classic.Logger) LogUtil.getLogger(name); logbackLogger.setLevel(templateLogger.getLevel()); logbackLogger.setAdditive(false); logbackLogger.addAppender(rollingFileAppender); return logbackLogger; } And this is how I reinitialize logback private static void initializeLogback() { File logbackFile = new File(logFilePath); System.setProperty("logback.configurationFile", logbackFile.getAbsolutePath()); StaticLoggerBinder loggerBinder = StaticLoggerBinder.getSingleton(); LoggerContext loggerContext = (LoggerContext) loggerBinder.getLoggerFactory(); loggerContext.reset(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(loggerContext); try { configurator.doConfigure(logbackFile); } catch( JoranException e ) { throw new ColumbusRuntimeException(e.getMessage(), e); } } Note: I also posted the same question to stackoverflow: http://stackoverflow.com/questions/9060545/creating-logback-logger-programm…

1 0

File appenders under SecurityManager
by Sergey Kabashnyuk 22 Feb '12

22 Feb '12

Hello I'd like to contribute the FileAppender and RollingFileAppender what made file operation from it's own name. It will allow to user code with restricted file access by SecurityManager to use loggers with file backend. If proposition is interesting I can create jira issue and provide patches with implementation. Example of SecurityFileAppender /** * Implementation of FileAppender what made file operation from it's own name. * Created to be used with enabled SecurityManager. */ public class SecurityFileAppender<E> extends FileAppender<E> { /** * @see ch.qos.logback.core.FileAppender#openFile(java.lang.String) */ @Override public void openFile(final String file_name) throws IOException { try { AccessController.doPrivileged(new PrivilegedExceptionAction<Void>() { @Override public Void run() throws Exception { SecurityFileAppender.super.openFile(file_name); return null; } }); } catch (PrivilegedActionException e) { throw new IOException(e.getLocalizedMessage(), e); } } /** * @see ch.qos.logback.core.FileAppender#writeOut(java.lang.Object) */ @Override protected void writeOut(final E event) throws IOException { try { AccessController.doPrivileged(new PrivilegedExceptionAction<Void>() { @Override public Void run() throws Exception { SecurityFileAppender.super.writeOut(event); return null; } }); } catch (PrivilegedActionException e) { throw new IOException(e.getLocalizedMessage(), e); } } } Sergey Kabashnyuk

1 0

Add a ContextListener in Groovy Config
by Pepper Lebeck-Jobe 22 Feb '12

22 Feb '12

Sorry if this has been asked before. I'm new to the user list, and I find it difficult to search the archives. How can I add a contextListener in a logback.groovy config file? On this page: http://logback.qos.ch/manual/configuration.html#contextListener It talks about adding a context listener specifically to deal with LevelChangePropogator. I'd like to do this, but I generally prefer the groovy syntax to the xml syntax. This page: http://logback.qos.ch/manual/groovy.html Talks a lot about the groovy syntax, but it doesn't specifically mention how to set up a contextListener. How can I do it? I have tried some things I thought would work, but they didn't. Groovy Version: 2.0.0 Logback Classic: 1.0.0 Thanks, Pepper

1 1

daily rollover w/ timezone problem
by Paul 21 Feb '12

21 Feb '12

If I setup a daily rollover with EST timezone I see the following in the log for yesterday: ----- <stuff deleted> 2012-02-20 18:58:51 INFO [main] logBackMain [logBackMain.java:19] step 1366 2012-02-20 18:59:01 INFO [main] logBackMain [logBackMain.java:19] step 1367 2012-02-20 18:59:11 INFO [main] logBackMain [logBackMain.java:19] step 1368 2012-02-20 18:59:21 INFO [main] logBackMain [logBackMain.java:19] step 1369 2012-02-20 18:59:31 INFO [main] logBackMain [logBackMain.java:19] step 1370 2012-02-20 18:59:41 INFO [main] logBackMain [logBackMain.java:19] step 1371 2012-02-20 18:59:51 INFO [main] logBackMain [logBackMain.java:19] step 1372 ----- The last logged message is close to 7pm EST or midnight GMT. With this setup a single day now shows up across 2 log files which makes trouleshooting application errors more difficult. Is there a way to have both EST time output and rollover happening relative to EST? Maybe there is a way to subtract an offset to the time of 5hrs? Here is my test appender: <appender name="DAILY" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>daily.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>daily.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date{yyyy-MM-dd HH:mm:ss,EST} %level [%thread] %logger{10} [%file:%line] %msg%n</pattern> </encoder> </appender> thanks, Paul.

1 0