April 2015 - logback-user - mailman3.qos.ch

Modifing MDCPropertyMap of LoggingEvents
by Cemo 17 May '15

17 May '15

I have a layout which is generating JSON from logging events and MDC Context. MDC is great and I want to add parameters to MDC Context conditionally. For example, I would like add request information as JSON into MDC conditionally on Error Level log entries. I am not familiar with Logback internals but gave a try with Logback Filter implementation. I have used: public FilterReply decide(ILoggingEvent event) { // simplified for demo // conditionally I am putting some attributes here Map<String, String> mdcPropertyMap = event.getMDCPropertyMap(); if (event.getLevel().isGreaterOrEqual(Level.ERROR)) { mdcPropertyMap.put("demo", "demo"); } return FilterReply.ACCEPT; } I am expecting mdcPropertyMap to be cleared for each event but it does not. LoggingEvent has a internal CACHED_NULL_MAP map and its modified per touch. private static final Map<String, String> CACHED_NULL_MAP = new HashMap<String, String>(); I could not be sure but it seems a little bid buggy to me. Can someone verify this behaviour? For those who are interested why I am not using MDC.put in a Servlet Filter implementation because I am conditionally adding some attributes. Serialising HttpRequest into JSON is not cheap task but having Http Request information is giving great insights about error. Using Filter is the only way I found to add conditionally attributes so far. What I would like to use is: public FilterReply decide(ILoggingEvent event) { if (event.getLevel().isGreaterOrEqual(Level.WARN)) { MDC.put("demo", "demo"); } return FilterReply.ACCEPT; }

3 3

Fwd: ContextSelector JNDI (in WildFly)
by Janario Oliveira 29 Apr '15

29 Apr '15

Hi guys, I'm looking for a full replacement to Logback in WildFly. I already added modules remove another ones and disabled log manager. Also I defined a default logback.xml and set it by property logback.configurationFile I was looking to work with JNDI context selector but as I see Loggers created from modules are attached to default LoggerContext and still after reuse from application classes My application logs works with the right contextSelector and consequentially the right appenders. But when I call some logger from modules, for example a query (SqlStatementLogger), its loggers are attached with default LoggerContext what selects the default appenders not application ones Is there a way to Logger dynamic select another context after it has been created? Has anyone made this work (as a full replacement)?

2 1

Wire up logback
by Russ Lavoie 28 Apr '15

28 Apr '15

Hello, I have an application that already has logback 1.1.3 packaged up with it. I want to take the logback.xml configuration that is in the application and override the log path without building a new package. I can currently accomplish this by just adding logback jars to lib/logging/, but that means i have the same jars on the file system twice. Is there a way I can utilize the already loaded jars instead of keeping two locations sync Thanks, Russ

1 0

Can I have level specific patterns?
by Andrew E. Davidson 15 Apr '15

15 Apr '15

Is it possible to have a logbook-text.xml file that defines two different patterns? For example if the level is debug, I want the level, time stamp, thread, file, line number, and message. If the level is error or warn, I want the level and message If the level is info I just want the message Thanks Andy

2 5

Max history for size and daily failing
by Fabiano, Lucas 06 Apr '15

06 Apr '15

Hi everyone, I’m using the configuration below for the appender. What I want to do is rollout the file after reach a size or in a daily bases. My problem is regarding how many files I want to have. I use the maxHistory and it works well for daily log and remove the old ones. The problem is when the file achieve the maximum size for it in the same day. It creates a new file with the index number on the file name but I can’t control how many files I can have. I tried to use the max and min index it inside timeBasedFileNamingAndTriggeringPolicy tag but when the config load it shows na error saying the configuration is in the wrong place. Even if I put the maxhistory inside this tag it shows the same problem and don’t rollout by size. <appender name="APPLICATION" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${destination}/${contextName}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${destination}/${contextName}-%d{yyyyMMdd}.%i.log.zip</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>1MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>2</maxHistory> </rollingPolicy> <encoder> <pattern>%date{yyyyMMdd|HHmmss.SSS}|%-5level|%10X{tid}|%logger{0}:%line|%msg%n</pattern> </encoder> </appender> Any advice will be welcome. Thank you! Lucas ________________________________ This email and any attachments are for the exclusive and confidential use of the named intended recipient(s) and may be legally privileged. Any review, re-transmission, dissemination or any other use of its contents, or taking of any action in reliance upon this information by persons and/or entities other than the named intended recipient(s) is strictly prohibited. If you have received this communication in error, please send this communication back to the sender, disregard its contents, and promptly delete the original message and any copy of it from your computer systems. The misuse of this message will be dealt according to company rules and current legislation. This message expresses the sender’s point of view about the topics described and not necessarily expresses Serasa Experian’s opinion about them. As informações contidas nesta mensagem e no(s) arquivo(s) anexo(s) são endereçadas exclusivamente à(s) pessoa(s) e/ou instituição(ões) acima indicada(s), e podem conter dados confidenciais. É expressamente proibido a pessoas não autorizadas, sob qualquer forma ou pretexto, utilizá-las, divulgá-las, alterá-las, de forma impressa ou copiada, total ou parcialmente. Caso tenha recebido esta mensagem erroneamente, por favor, notifique o remetente e providencie imediata exclusão da original e de qualquer cópia. O uso impróprio será tratado conforme as normas da empresa e da legislação em vigor. Esta mensagem expressa o posicionamento pessoal do subscritor e não reflete necessariamente a opinião da Serasa Experian.

2 1

Writting logs to current date
by Srikanth Hugar 06 Apr '15

06 Apr '15

Hello I am using logback to write files and i have the below mentioned appender configuration. Below configuration works fine. My question is,how to write the logs in current directory? Is it possible? Currently written as, What i am looking is to write karaf.log on current date directory. Would be helpful, if some experts could let me know about the changes. *2015-04-03* *2015-04-04* *2015-04-05* *karaf.log* <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>data/log/karaf.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>data/log/%d{yyyy-MM-dd}/karaf.%d{yyyy-MM-dd}.%i.gz </fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>10MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy>  <maxHistory>10</maxHistory> </rollingPolicy> <append>true</append> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n </pattern> </encoder> </appender>

1 0

log files are not rolling with logback.xml conf in karaf
by Srikanth Hugar 01 Apr '15

01 Apr '15

Hello All, My log files are not rolling when it reached 10MB with below configuration. I tried other combination too, could not succeed. Please help me in resolving the issue. What i could be configuring wrong here. <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>data/log/karaf.log</file> <encoder> <pattern>%d{ISO8601} | %-5level | %thread | %logger{1} | %message%n </pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <maxIndex>15</maxIndex> <fileNamePattern>data/log/karaf.%d{yyyy-MM-dd}.%i.gz </fileNamePattern> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>10MB</MaxFileSize> </triggeringPolicy> </appender> Thanks. Srikanth.

2 1