December 2014 - logback-user

Cant able to appy <pattern> and <Layout> in <encoder> of logback.xml
by goto meet127 28 Dec '14

28 Dec '14

I am trying to create custom layout in Logback, using the link, http://stackoverflow.com/questions/14168684/creating-a-custom-layout-in-log… and i am successful in creating log file. The problem is when I apply "pattern" tag in encoder tag of logback.xml like this, Logback.xml ========== <appender name="appLogFileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"><rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/tmp.log</fileNamePattern> </rollingPolicy> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <pattern> %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n </pattern> <layout class="com.dces.util.LoggingConsoleLayout" /> </encoder> </appender> it is not applied on log file, which is created, and I am getting content without date&time AS BELOW. *--** [ERROR]main.java.com.srccodes.log.LogbackHello - Welcome to the HelloWorld example of Logback. * *-- **[ERROR]main.java.com.srccodes.log.LogbackHello - Dummy error message.* Actually if I remove class="ch.qos.logback.core.encoder.LayoutWrappingEncoder" in encoder tag ,pattern is working, but then my custom layout is not working. I want to apply *pattern* tag as well as custom *layout* tag on encoder tag.Is it is possible? LoggingConsoleLayout.xml - My Cuatom Layout ===================================== public class LoggingConsoleLayout extends LayoutBase<ILoggingEvent>{ @Override public String doLayout(ILoggingEvent event) { StringBuffer sbuf = null; try { sbuf = new StringBuffer(128); sbuf.append("-- "); sbuf.append("["); sbuf.append(event.getLevel()); sbuf.append("]"); sbuf.append(event.getLoggerName()); sbuf.append(" - "); *sbuf.append(encodeData(event.getFormattedMessage()));* *//here i am encoding my log messages and which is important for me* sbuf.append(CoreConstants.LINE_SEPARATOR); } catch(Exception e) { e.printStackTrace(); } return sbuf.toString(); } } when I tried this, <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="com.dces.util.LoggingConsoleLayout" > <Pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</Pattern> </layout> </encoder> I got *ERROR in ch.qos.logback.core.joran.spi.Interpreter@17:17 - no applicable action for [Pattern], current ElementPath is [[configuration][appender][encoder][layout][Pattern]]* And my pattern is not applied to my layout... Is there is any possibility to have both layout and pattern tags in encoder tag?

1 0

Fwd: Reg Custom Layout in Logback.xml
by goto meet127 27 Dec '14

27 Dec '14

Cant able to appy <pattern> and <Layout> in <encoder> of logback.xml <http://stackoverflow.com/questions/27646632/cant-able-to-appy-pattern-in-lo…> I am trying to create custom layout in Logback, using the link, http://stackoverflow.com/questions/14168684/creating-a-custom-layout-in-log… and i am successful in creating log file. The problem is when I apply "pattern" tag in encoder tag of logback.xml like this, Logback.xml ========== <appender name="appLogFileAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"><rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/tmp.log</fileNamePattern> </rollingPolicy> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <pattern> %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n </pattern> <layout class="com.dces.util.LoggingConsoleLayout" /> </encoder> </appender> it is not applied on log file, which is created, and I am getting content without date&time AS BELOW. *--** [ERROR]main.java.com.srccodes.log.LogbackHello - Welcome to the HelloWorld example of Logback. * *-- **[ERROR]main.java.com.srccodes.log.LogbackHello - Dummy error message.* Actually if I remove class="ch.qos.logback.core.encoder.LayoutWrappingEncoder" in encoder tag ,pattern is working, but then my custom layout is not working. I want to apply *pattern* tag as well as custom *layout* tag on encoder tag.Is it is possible? LoggingConsoleLayout.xml - My Cuatom Layout ===================================== public class LoggingConsoleLayout extends LayoutBase<ILoggingEvent>{ @Override public String doLayout(ILoggingEvent event) { StringBuffer sbuf = null; try { sbuf = new StringBuffer(128); sbuf.append("-- "); sbuf.append("["); sbuf.append(event.getLevel()); sbuf.append("]"); sbuf.append(event.getLoggerName()); sbuf.append(" - "); *sbuf.append(encodeData(event.getFormattedMessage()));* *//here i am encoding my log messages and which is important for me* sbuf.append(CoreConstants.LINE_SEPARATOR); } catch(Exception e) { e.printStackTrace(); } return sbuf.toString(); } } when I tried this, <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="com.dces.util.LoggingConsoleLayout" > <Pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</Pattern> </layout> </encoder> I got *ERROR in ch.qos.logback.core.joran.spi.Interpreter@17:17 - no applicable action for [Pattern], current ElementPath is [[configuration][appender][encoder][layout][Pattern]]* And my pattern is not applied to my layout... Is there is any possibility to have both layout and pattern tags in encoder tag?

1 0

Problem in FileAppender 'append' flag
by pedro rijo 18 Dec '14

18 Dec '14

Hey, I'm creating a log with FileAppender to my application programmatically, and I set the append flag to false, but it keeps append the logging in the same file, instead of reseting the file. The code is in https://gist.github.com/pedrorijo91/6ce3e8f9144302ef4bc1 What may be the problem? How can I reset the log file in every application execution ? Note: the method is used by several classes, the idea is that every class logs into that file, and in another application run the file be reseted. -- Kind Regards, Pedro Rijo

1 0

Escaping $ in logback.xml
by Paul Bemowski 12 Dec '14

12 Dec '14

I'm working on a custom layout to mask sensitive information in our production logs. One of the key features is to use regular expressions - so i need the syntax of logback.xml to support the special characters in regex - including $. I have searched high and low with google - and read the source a bit. but it looks like there is no mechanism to escape this character. Here is a fragment of my config file: ... <layout class="log.PIIFilterLayout"> <pattern>:%d{HH:mm:ss.SSS} [%thread] %-5level %logger{1} - %msg %n</pattern>  <regex>mdn='(.+)'</regex> <regex>accountName=(.+)$</regex>... I have tried: - $ - \$ - \\$ - $ No matter what - i get this: Failed to instantiate [ch.qos.logback.classic.LoggerContext]Reported exception:java.lang.IllegalArgumentException: Failed to parse input [accountName=(.+)\\$] at ch.qos.logback.core.util.OptionHelper.substVars(OptionHelper.java:119) at ch.qos.logback.core.joran.spi.InterpretationContext.subst(InterpretationContext.java:159) at ch.qos.logback.core.joran.action.NestedBasicPropertyIA.body(NestedBasicPropertyIA.java:87) at ch.qos.logback.core.joran.spi.Interpreter.callBodyAction(Interpreter.java:295) at ch.qos.logback.core.joran.spi.Interpreter.characters(Interpreter.java:175) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:57) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) 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:129) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:302) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:276) at util.LogFactory.getLogger(LogFactory.java:27) at log.PIITest.<clinit>(PIITest.java:20)Caused by: ch.qos.logback.core.spi.ScanException: Unexpected end of pattern string How can i escape $ in logback.xml? Paul

1 0

Sending only recent messages with SMTPAppender
by Matthieu Desmons 12 Dec '14

12 Dec '14

Hi, The SMTPAppender can be configured to send only the latest X messages thanks to the BufferSize parameter. But is there a way to filter messages so that it sends only the latest X messages emitted within say 1 hour? This way, if an ERROR message happens, the email will only contain potential events that happened just recently. I read the doc, don't think Filters or Evaluators will do it. As far as I can see my only option would be to develop my own CyclicBufferTracker and configure the SMTPAppender to use it, but I was wondering if: a) There's an easier way to do this? b) If there's no other way, would developing my own CyclicBufferTracker work? Thanks Matthieu Privileged or confidential information may be contained in this message. If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Gresham does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Gresham does not accept liability for any damage sustained as a result of viruses. Statements in this message that do not relate to the business of Gresham are neither given nor endorsed by the company or its directors. Gresham Computing plc Registered in England and Wales. Company No. 01072032 Registered Office: Aldermary House, 10-15 Queen Street, London, EC4N 1TX. Further information about Gresham Computing can be found on our website: www.gresham-computing.com

1 0

Rolling files on Android
by Chris Kelly 08 Dec '14

08 Dec '14

I've gone through a bit of trial and error, and have not been able to get logs to roll over, no matter how aggressively I set up triggering and rolling policies. My intent is to have daily logs with a max size all configured in code, thus no assets/logback.xml. I've enabled debugging and the only status message is (which I would expect): I/System.out﹕ 17:37:13,194 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [assets/logback.xml] In a nutshell I have the TimeBasedRollingPolicy set up to use a file as rollingPolicy.setFileNamePattern(ctx.getCacheDir().getAbsolutePath() + File.separator + "logs" + File.separator + name +".%d{yyyy-MM-dd_HH}.log"); // exprimenting with hourly and the size based triggering at 25k like sizeTriggerPolicy.setMaxFileSize("25KB"); I then set these to the rollingFileAppender, set up a pattern encoder and add it, then start the appender. I can see the messages in my log file as expected, but it continues to grow well past the max size and past any time based trigger (even while log events continue). Any suggestions? Thanks, Chris

2 2

clean up logs after N gigabytes of logs (i.e. ArchiveRemover)
by Don Gately 08 Dec '14

08 Dec '14

Hi All, I recently filled up a disk with logs, and so now I'm trying to figure out how to ensure that I can set an upper-limit on the size of all logs in the directory. I've found how to trigger file rollover @ a given size, and how to clean up logs after, say 3 days, but provided I'm thinking about this correctly, what I really want is: 1) roll over logs @ midnight each day 2) cleanup logs if size of all logs gets larger than X bytes I haven't found a way to do this without writing my own RollingPolicy (and maybe TriggerPolicy, NamingPolicy, etc). This seems like it would be a common goal for users, so am I missing some way to do this with Logback off-the-shelf (i.e. no custom code)? Thanks, BIM

3 3

logback android - robolectric tests console output is missing native android logging statements
by athanasios kaliakoudas 06 Dec '14

06 Dec '14

Logging statements found in the android source code that are not slf4j, but in the form of Log.e(TAG, "details"); do not appear in console. Some of my robolectric tests were failing and as I was going through the code I noticed that in the android class "android.database.sqlite.SQLiteDatabase" method there is a method "insert" that looks like this: public long insert(String table, String nullColumnHack, ContentValues values) { try { return insertWithOnConflict(table, nullColumnHack, values, CONFLICT_NONE); } catch (SQLException e) { Log.e(TAG, "Error inserting " + values, e); return -1; } } When my test run this method returned -1 but after looking at the output in Intellijs console I noticed that the log statement explaining the error was missing. Is there a way for this statement that is not slf4j to be displayed in the console? I assume that if I was running the application and the same error occurred it would appear in the logcat window. my logback.xml for tests looks like this <?xml version="1.0" encoding="UTF-8"?> <configuration> <property name="appender.encoder.pattern" value="%d | %-10r | %5p | %-30t | %-100logger{100} | %-50M | %-5L | %m %n"/> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>${appender.encoder.pattern}</pattern> </encoder> </appender> <logger name="com.myapp"> <level value="TRACE"/> </logger> <root> <level value="INFO"/> <appender-ref ref="CONSOLE"/> </root> </configuration>

2 1

Re: [logback-user] logback.xml not reloaded
by Johanes Soetanto 02 Dec '14

02 Dec '14

Quoting the doc "In order to improve performance, ReconfigureOnChangeFilter is in reality "alive" only once every *N* logging operations. Depending on how often your application logs, the value of *N* can be modified on the fly by logback. By default N is 16, although it can go as high as 2^16 (= 65536) for CPU-intensive applications. In short, when a configuration file changes, it will be automatically reloaded but only after several logger invocations *and* after a delay determined by the scanning period. " Correct me if i'm wrong, if the check happens ever N log operation, shouldn't it use modulus instead of masking for the check? e.g. if (((invocationCounter++) % mask) != 0) { Thanks, Johanes On 2 December 2014 at 22:00, <logback-user-request(a)qos.ch> wrote: > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 2 Dec 2014 17:05:05 +1100 > From: Johanes Soetanto <otnateos(a)gmail.com> > To: logback-user(a)qos.ch > Subject: > Re: [logback-user] logback.xml not reloaded > Message-ID: > < > CAHn_Lrwmbson+n4zrRwHNQkEL-ch3BUGE5VvFMyykmnAwmqMHA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Finally I manage to get a time to debug the app. Looking > into ReconfigureOnChangeFilter (version 1.0.13) , the execution is stopped > by line #108 where the mask is always set to 65535 . > > I'm clueless on how to change the mask as it seems like it is being managed > automatically by updateMaskIfNecessary (line #147) . I believe it was added > for optimization, but with mask value of 65535, it will be a while for the > configuration to be loaded even though i set my configuration to be scanned > every 200 seconds. > > Any hint how to fix this? Thanks, > > Johanes > > > > > > Message: 1 > > Date: Wed, 12 Nov 2014 12:10:38 +1100 > > From: Johanes Soetanto <otnateos(a)gmail.com> > > To: logback-user(a)qos.ch > > Subject: Re: [logback-user] logback.xml not reloaded > > Message-ID: > > <CAHn_LrykvJuj=UF4=-YhoW+QdUb2y+iHKS9u=5wT5D= > > dCv8uNA(a)mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > Upon my investigation, it seems like my problem with reloading is related > > to the change made in version 1.0.2 ( > http://jira.qos.ch/browse/LOGBACK-327 > > ). > > > > I tested with version 1.0.1 or 1.1.2 the configuration is not reloaded > when > > there is change. > > > > > > Note: I haven't run the app on debug mode. > > > > Johanes > > > > > > > > Message: 4 > > > Date: Tue, 4 Nov 2014 10:01:11 +0000 > > > From: David Roussel <nabble(a)diroussel.xsmail.com> > > > To: logback users list <logback-user(a)qos.ch> > > > Subject: > > Re: [logback-user] logback.xml not reloaded > > > Message-ID: > > > <EEBB841D-A28F-4616-80CD-83E3A326CF70(a)diroussel.xsmail.com> > > > Content-Type: text/plain; charset="us-ascii" > > > > > > My only suggestion is running it in a debugging session in your IDE and > > > seeing what is happening that way. > > > > > > David > > > > > > > On 4 Nov 2014, at 07:34, Johanes Soetanto <otnateos(a)gmail.com> > wrote: > > > > > > > > Hi there, > > > > > > > > I would like to know if there is a way to debug why logback.xml > > > configuration change cannot be reloaded by our application. It had been > > > working correctly on our application for a long time, however I > discover > > > from a week ago that change at runtime is not applied. If i restart the > > > application, the change is applied properly. configuration xml is using > > > basic one using scan="true". > > > > > > > > I tried adding debug="true" but no information message apart from > usual > > > logback information message before application startup. The only > change I > > > can think of is we change Tomcat from 6.0.x to 7.0.56. We are using > > logback > > > version 1.0.13. > > > > > > > > Any assistance is appreciated. > > > > > > > > Thanks > > > > > > > > Johanes > > > > >

2 1

logback.xml scan & reload issue when using context properties
by Sagar Shah 02 Dec '14

02 Dec '14

Hello Logback-User support, I am using common logback.xml file, which is loaded programmatically from different J2EE web applications and which writes to different log files using "SiftingAppender". Everything works fine unless logback.xml file has been modified. Once it has been modified, it gets scanned & reloaded as per configuration of scanPeriod, post which it does not recognize the context properties and it still writes all the logs, but in a separate file (with suffix of application-name_IS_UNDEFINED) for al lthe applications. Logback version : 1.0.13 Logback configuration <appender name="LogFile" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator> <key>application-name</key> <defaultValue>5</defaultValue> </discriminator> <sift> <appender name="${application-name}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <prudent>false</prudent> <file>C:/logs/${application-name}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>c:/logs/${application-name}.%d{yyyy-MM-dd}.%i.log</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>5MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy>  <MaxHistory>30</MaxHistory> </rollingPolicy> <encoder> <pattern> <Pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger - %msg%n</Pattern> </pattern> </encoder> </appender> </sift> </appender> Logback Loading programmatically from the Context Listener class LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator jc = new JoranConfigurator(); jc.setContext(context); context.reset(); context.putProperty("application-name", sce.getServletContext().getServletContextName()); String logFilePath = sce.getServletContext().getInitParameter(INIT_PARAM_NAME); if (logFilePath==null){ throw new RuntimeException("Unable to load init parameter " + INIT_PARAM_NAME + " from web.xml file"); } try{ jc.doConfigure(logFilePath); } catch (Exception e){ e.printStackTrace(); throw new RuntimeException("Unable to load logback.xml file successfully @ " + logFilePath, e); } Is this a known issue? Is there a fix for this already? Please advise. Appreciate! Regards, Sagar Shah Sagar Shah Contractor [MEDHOST logo] 6550 Carothers Pkwy STE 100 Franklin, TN 37067 p. c. f. Sagar.Shah(a)medhost.com<mailto:Sagar.Shah@medhost.com> Register for the 2015 MEDHOST MPACT Summit held September 14-18, 2015 in Nashville, Tennessee. CONFIDENTIALITY STATEMENT: The documents accompanying this transmission may contain confidential and/or legally privileged health or other information. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of these documents is strictly prohibited. If you have received this information in error, please notify the sender immediately and arrange for the return or destruction of these documents.

1 0