- logback-user - mailman3.qos.ch

Root logger with debug, appender with trace
by Felix Natter 26 Dec '16

26 Dec '16

hello, I have a spring application that logs to a primary log file ("caseportal.log"): (note: I replaced the real root package of my code by "root.package")  <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${catalina.base}/logs/caseportal.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${catalina.base}/logs/caseportal-%d.log.zip</FileNamePattern> <maxHistory>120</maxHistory> </rollingPolicy> <encoder> <pattern>${logPattern}</pattern> </encoder> </appender> plus *additionally*, for some packages, to several other log files (picked one example, "cp-deletion.log", here): <appender name="deletion" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${catalina.base}/logs/cp-deletion.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${catalina.base}/logs/cp-deletion-%d.log.zip</FileNamePattern> <maxHistory>120</maxHistory> </rollingPolicy> <encoder> <pattern>${logPattern}</pattern> </encoder> </appender> [...] <logger name="root.package.core.service.deletion" level="DEBUG"> <appender-ref ref="deletion"/> </logger> <logger name="root.package.core.domain.deletion" level="DEBUG"> <appender-ref ref="deletion"/> </logger> <logger name="root.package.core.scheduledtasks.BulkDeletionCron" level="DEBUG"> <appender-ref ref="deletion"/> </logger> <logger name="root.package.frontend.runners.BulkDeletionRunner" level="DEBUG"> <appender-ref ref="deletion"/> </logger> Now I would like some packages to *only* log to another log file ("cp-retentionperiodad.log"). I am trying to achieve this by logging with loglevel TRACE, configuring the root logger to log only DEBUG for those packages: <logger name="root.package" level="DEBUG"/> and configuring the other log file with loglevel TRACE for those packages: <appender name="retentionperiodad" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${catalina.base}/logs/cp-retentionperiodad.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${catalina.base}/logs/cp-retentionperiodad-%d.log.zip</FileNamePattern> <maxHistory>120</maxHistory> </rollingPolicy> <encoder> <pattern>${logPattern}</pattern> </encoder> </appender> <logger name="root.package.core.scheduledtasks.RetentionPeriodAdCron" level="TRACE"> <appender-ref ref="retentionperiodad"/> </logger> <logger name="root.package.core.ad.authorize.ActiveDirectoryClient" level="TRACE"> <appender-ref ref="retentionperiodad"/> </logger> But the "root logger" (?) caseportal.log still logs these TRACE messages, so they appear there (and in cp-retentionperiodad.log). Is there a better way to log some packages *only* to another log? If not, how can I get this to work? The complete logback.xml is attached. Many Thanks and Merry Christmas for those who celebrate this! -- Felix Natter

1 0

Announcement: logback-redis adapter for logstash
by Lars Gohlke 20 Dec '16

20 Dec '16

We would like to proudly announce our first public release of ‘logback-redis’. This library enables JVM applications to log directly into a Redis+ELK stack with logback. https://github.com/idealo/logback-redis The logback-redis appender has been battle-tested in conjunction with logstash-logback-encoder [1], which takes care of JSON-encoding and buffering. We aimed for: - developer-friendliness (easy to configure, safe to use) - maximum throughput (Redis pipelining support) - high software quality We use this library for apps in a RELK (Redis-Elasticsearch-Logstash-Kibana) environment in production for over six months, handling easily 1000 messages/second per host, used by over 50 installations concurrently. Why did we implemented another solution? > We experienced load problems with existing libraries at 100 m/s. Another similiar library is aqlu/logstash-logback-encoder-extends [2]. We welcome any feedback at https://github.com/idealo/logback-redis. [1] https://github.com/logstash/logstash-logback-encoder [2] https://github.com/aqlu/logstash-logback-encoder-extends -- Lars K.W. Gohlke Software gardener User-Services *idealo internet GmbH* Ritterstraße 11 10969 Berlin, Deutschland E-Mail: lars.gohlke(a)idealo.de <anja.kettern(a)idealo.de> Geschäftsführer: Dr. Albrecht von Sonntag, Dr. Philipp-Christopher Peitsch, Jörn Rehse HRB 76749 – Amtsgericht Berlin-Charlottenburg [image: idealo Logo] <http://www.idealo.de/>

1 0

LOGBACK-1189: detect previous copyAttributeMap calls
by Mark Elliot 07 Dec '16

07 Dec '16

Hi, there's a serious functionality bug with logback-access described in LOGBACK-1189 (which also proposes a fix). I pushed a fix here https://github.com/qos-ch/logback/pull/336 <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_qos-2Dch_lo…>, and wonder when we might be able to get this merged and released. I suspect http://mailman.qos.ch/pipermail/logback-user/2016-September/004800.html is another (and high profile) manifestation of this problem. Thanks, Mark

1 1

service on all qos.ch lists will be interrupted due to host migration EOM
by Ceki Gulcu 24 Nov '16

24 Nov '16

1 0

Is there a way to define a variable by making a call to Joran?
by Benson Margulies 04 Nov '16

04 Nov '16

I looked quickly through the class stack for the Joran configurator, but I didn't spot anything. Is there something I'm missing? I want to have an XML file with some variable references, configure explicitly with Joran, and set some vars. I can write code to edit the XML or to set system props, but I was hoping for something cleaner.

1 0

Log forging prevention
by Svetlin Zarev 04 Nov '16

04 Nov '16

Hello, What's the recommended way to protect against log forging attacks with logback (using pattern layout) ? Is there a way to specify a set of reserved characters and tell logback to escape them ? Kind regards, Svetlin

2 2

The level propagator is noisy, is there any cure?
by Benson Margulies 04 Nov '16

04 Nov '16

I do not have INFO messages enabled for ch.qos, is there something else I need to do to avoid this noise from <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"/> ? 09:54:34,959 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.basistech.ws.worker.core.ComponentServiceTrackerImpl] to INFO 09:54:34,959 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@7d70d1b1 - Propagating INFO level on Logger[com.basistech.ws.worker.core.ComponentServiceTrackerImpl] onto the JUL framework 09:54:34,959 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache] to WARN 09:54:34,959 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@7d70d1b1 - Propagating WARN level on Logger[org.apache] onto the JUL framework 09:54:34,959 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.felix] to INFO

2 1

context-name in WebApplicationInitializer
by Robert . 31 Oct '16

31 Oct '16

I'm trying to set the context-name for each web application to try to separate logging per web application as documented in http://logback.qos.ch/manual/loggingSeparation.html I am using a WebApplicationInitializer so try to set the logback/context-name env-entry in Java code. I have tried the following in the onStartup method: InitialContext initialContext = new InitialContext(); initialContext.addToEnvironment("logback/context-name", "mycontext"); I see logback is trying to get the contextName in ContextJNDISelector.getLoggerContext(). Unfortunately the lookup returns null even though I can see the "logback/context-name" entry in ctx.getEnvironment() What's the correct way to add the context-name to IntialContext?

1 0

SizeAndTimeBasedRollingPolicy not deleting files with 4 digit “%i”
by Arnab Biswas 20 Oct '16

20 Oct '16

Hi All, We are using SizeAndTimeBasedRollingPolicy/SizeAndTimeBasedFNATP in our product (logback 1.1.3). Here is snip from the logback configuration file : <appender name="SERVER_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${MY_LOGS}/myabc.log</file> <append>true</append>  <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${MY_LOGS}/myabc-%d{yyyy-MM-dd}.*%i.gz* </fileNamePattern>  <maxHistory>30</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.*SizeAndTimeBasedFNATP">*  <maxFileSize>250MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%d{yyyy-MM-dd'T'HH:mm:ss.SSS} [%thread] %-5level %logger{24} [%C{1}.%M]</pattern> </encoder> </appender> The log files generated have the following names : myabc-2016-11-21.0.gz, myabc-2016-11-21.1.gz, myabc-2016-11-21.2.gz etc. The problem is if a log file has extension (%i) more than 3 digits, it is not being deleted after 30 days (maxHistory). For example, myabc-2016-11-21.0.gz gets deleted after 30 days, but myabc-2016-11-21. *1000*.gz is *NOT* getting deleted. Is there any other appender/configuration which I need to add to the logback configuration file to make sure files with more than 3 digit extension also gets deleted or is it a bug in logback? I know that total number of log files generated can be controlled by setting the property "totalSizeCap" and that way I can avoid generating more than 999 files per day. But that is not the answer I am looking for. Also, I have tried with logback 1.1.7, but that did not help. Since for us this issue has been raised by the customer, for the sake of urgency, I have posted this question in stack overflow <http://stackoverflow.com/questions/40144806/logback-sizeandtimebasedrolling…> as well. To avoid duplicity, I can delete the other thread if needed. Your help will be highly appreciated. Thanks, Arnab

1 0

Problems with logback rotation of logs (using with LSC-Project)
by Massimo Ciancio 18 Oct '16

18 Oct '16

Hello to all, I have problems with log rotation. Using the configuration for debugging in logback.xml but my lsc.log do not rotate. I run LSC 2.1 ( lsc-2.1.3-0.el5.noarch) with Java: java version "1.7.0_79" Java(TM) SE Runtime Environment (build 1.7.0_79-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode) and permissions in the /var/log/lsc seem correct: drwxr-xr-x 2 lsc lsc 4.0K Sep 29 11:42 . drwxr-xr-x. 10 root root 4.0K Sep 27 23:58 .. -rw-r--r-- 1 lsc lsc 157K Sep 29 15:23 lsc.ldif -rw-r--r-- 1 lsc lsc 5.1G Sep 29 22:55 lsc.log (5.1 GB!!!) -rw-r--r-- 1 lsc lsc 480 Sep 29 17:48 lsc.status Can you help me? thanks in advance regards -----Logback.xml----- <?xml version="1.0" encoding="UTF-8"?> <configuration>  <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="org.lsc.utils.output.LdifLayout"> <Pattern>%date{MMM dd HH:mm:ss} - %-5level - %message%n</Pattern> </layout> </encoder> </appender>   <appender name="LSC" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/log/lsc/lsc.log</file> <layout class="org.lsc.utils.output.LdifLayout"> <Pattern>%date{MMM dd HH:mm:ss} - %-5level - %message%n</Pattern> </layout> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>DEBUG</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <FileNamePattern>lsc.log.%i.gz</FileNamePattern> <MinIndex>1</MinIndex> <MaxIndex>7</MaxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>10000KB</MaxFileSize> </triggeringPolicy> </appender>   <appender name="LSC_STATUS" class="ch.qos.logback.core.FileAppender"> <append>false</append> <file>/var/log/lsc/lsc.status</file> <layout class="org.lsc.utils.output.LdifLayout"> <Pattern>%date{MMM dd HH:mm:ss} - %-5level - %message%n</Pattern> </layout> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> </appender>   <appender name="LDIF" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/var/log/lsc/lsc.ldif</file> <layout class="org.lsc.utils.output.LdifLayout"> <Pattern>%m%n</Pattern> <onlyLdif>true</onlyLdif> </layout> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <FileNamePattern>lsc.ldif.%i.gz</FileNamePattern> <MinIndex>1</MinIndex> <MaxIndex>7</MaxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>10000KB</MaxFileSize> </triggeringPolicy> </appender>  <logger name="org.lsc" level="DEBUG"> <appender-ref ref="LSC"/> <appender-ref ref="LSC_STATUS"/> </logger>  <logger name="lsc" level="INFO"> <appender-ref ref="LDIF"/> </logger>  <logger name="communicationLogger" level="WARN"> <appender-ref ref="CONSOLE"/> </logger> <logger name="org.apache" level="WARN"> <appender-ref ref="CONSOLE"/> </logger> <logger name="poolLogger" level="WARN"> <appender-ref ref="CONSOLE"/> </logger>  <root level="WARN"> <appender-ref ref="CONSOLE"/> </root> </configuration> --- EOF ---

1 0