May 2019 - logback-user - mailman3.qos.ch

Multiple FileAppenders writing to single file no longer working in Logback 1.2.3
by John Morton 24 Sep '19

24 Sep '19

Hello there Logback users. An application I’m responsible uses logback for its internal logging. It logs to various files at various levels. I’ve extended it successfully to reformat certain log messages and save them into a new log called “combined-audit.log”. This is all within a single JVM, logging to a file on a local filesystem. The reason for the three loggers/appenders is that I want to log from three different packages, at different levels, filter each differently, and encode each differently. This is all necessary because I cannot make changes to the app itself, so I’m trying to use Logback to accomplish my needs. The below configuration works in Logback 1.1.3 and not in Logback 1.2.3. In Logback 1.2.3, only messages from one of the three loggers are logged to the single file. When I change the file name to three different files, messages from each logger are in each file. I read through release notes from 1.1.3 to 1.2.3 and nothing jumped out at me as having the potential to change this behavior. Is this a supported configuration in 1.2.3? Does anyone have any ideas for how to accomplish the objective?  <appender name="COMBINED_AUDIT" class="ch.qos.logback.core.FileAppender"> <File>${logging.directory}/combined-audit.log</File> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <charset>UTF-8</charset> <Pattern>%date{ISO8601}|%mdc{m.remote_addr}|%mdc{m.jsessionid}||%msg%n</Pattern> </encoder> </appender> <logger name="j.k.l" level="ALL" additivity="false"> <appender-ref ref="COMBINED_AUDIT"/> </logger>  <appender name="COMBINED_LDAP" class="ch.qos.logback.core.FileAppender"> <File>${logging.directory}/combined-audit.log</File> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <charset>UTF-8</charset> <Pattern>%date{ISO8601}|%mdc{m.remote_addr}|%mdc{m.jsessionid}|%replace(%replace(%replace(%msg){'^.*resultCode=',''}){',.*identifier=','|'}){', context=.*$',''}|LDAP|||%n</Pattern> </encoder> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>return message.contains("authenticate response=");</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> <logger name="a.b.c.d" level="DEBUG" additivity="false"> <appender-ref ref="COMBINED_LDAP"/> </logger>  <appender name="COMBINED_INVALID_USERNAME" class="ch.qos.logback.core.FileAppender"> <File>${logging.directory}/combined-audit.log</File> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <charset>UTF-8</charset> <Pattern>%date{ISO8601}|%mdc{m.remote_addr}|%mdc{m.jsessionid}|INVALID_USERNAME||LDAP|||%n</Pattern> </encoder> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>return message.contains("failed using filter=");</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> <logger name="v.w.x.y.z" level="INFO" additivity="false"> <appender-ref ref="COMBINED_INVALID_USERNAME"/> </logger>

3 4

logger name too long
by Joud Kassem 29 May '19

29 May '19

Hi all, I'm new to logback and I have the following question: Is there a way to show only the left part of a logger name? like if I have "liquibase.changelog.ChangeSet" logger, I need to show only liquibase in the log. In the log pattern the focus always on the right part not the left as I see (%logger{36}). If not, is there a way to rename a logger in a plugin? like in the liquibase-core plugin, I want liquibase.changelog.ChangeSet to be liquibase.. Thanks in advance

1 0

Logs from Receiver not being displayed by Appenders
by ULStudent:ADAM.O'MAHONY 29 May '19

29 May '19

Hi all, Recently I have been trying to implement a centralised loggin server using slf4j with Logback. To try and understand how the receiver architecture works, I set up two java applications built with maven. One (Client) creates logs and sends them via ch.qos.logback.classic.net.SocketAppender to the second (Server) receiving with a ch.qos.logback.classic.net.server.ServerSocketReceiver. The problem I have encountered is that the logs sent from the client are not displayed by the Server's appenders. I have used a packet sniffer to confirm that the packets are indeed send and received. I have also tried changing the receiver and socket layout i.e SocketAppender -> ServerSocketAppender and ServerSocketReceiver -> SocketReceiver but got the same results. When nothing I was trying worked I tried using the examples given in the Logback documentation exactly but again, got the same result. Finally I tried sending logs via Log4j 2 (Log4j 2 Socket Appender -> Logback ServerSocketReceiver) but again no luck. The connect was established between appender and receiver in each test before logs began to send. I would like to also note that any logs local to the applications are displayed perfectly by their respected appenders. Any help with this problem would be greatly appreciated. Kind regards, Adam.

1 0

<logger/> to spi
by Rolf Schumacher 25 May '19

25 May '19

Just made my first spi.Configurator service work and translated some logback.xml to Java. Now I wonder what would be the best way to translate a <logger/> element, defining Level for sets of loggers? Should I define a Filter and add it to all Appenders, or is there a more straight forward way? Kind Regards Rolf

1 0

Re: [logback-user] No logfile when starting application from a remote host : Problem solved
by Michael.Fankanowsky＠t-systems.com 23 May '19

23 May '19

Hi, I could solve the problem. I didn’t consider that after login via ssh on the remote host the ‘execution’ environment is the user’s home directory. But our application is in a different directory and we configured the logs to be there (we detected the logs by accident in the home directory). Thus I had to combine two commands in ssh call with ProxyCommand – first a change directory and then the call of the start script. Now it works. Sorry for the confusion. Best regards, Michael Fankanowsky Von: logback-user <logback-user-bounces(a)qos.ch> Im Auftrag von Oleksandr Gavenko Gesendet: Montag, 13. Mai 2019 15:53 An: logback users list <logback-user(a)qos.ch> Betreff: Re: [logback-user] No logfile when starting application from a remote host Spring Boot is a magic. They probably expose some JMX endpoints but I know a way with Actuator endpoints, check in that order of importance: curl http://localhost:8080/actuator/env curl http://localhost:8080/actuator/loggers curl http://localhost:8080/actuator/ configprops On Mon, May 13, 2019 at 12:34 PM <Michael.Fankanowsky(a)t-systems.com<mailto:Michael.Fankanowsky@t-systems.com>> wrote: Hi, we are using logback v1.2.3 in a Springboot application which is running on Linux. When starting the application locally on the Linux host, logfile is created and application logs to it. When starting the application from a remote host via ssh then no logfile is created. When restarting the application (logfile is present and application has been logging to it) from a remote host, then no log messages will be logged to the existing logfile. It is working when restarting the application locally on the Linux host. Does anyone have an idea concerning this behavior? Best regards, Michael Fankanowsky _______________________________________________ logback-user mailing list logback-user(a)qos.ch<mailto:logback-user@qos.ch> http://mailman.qos.ch/mailman/listinfo/logback-user

1 0

Why my logs contain null characters(holes)
by Tianjiao Liu 15 May '19

15 May '19

Hi all, I am using logback(SiftingAppender and RollingFileAppender) in my application. Whenever requests come in, they will be logged to different files according to the id from url query. This is working really well and I get the expected result. However, I noticed occasionally, there are some null characters in the middle of logs. I am not sure why this happens and how to reduce it. I did some research and the closest thing I found is https://serverfault.com/questions/71341/why-do-jboss-and-logrotate-create-l… They are using logrotate with log4j and that results in the null character. However, in my case, the whole log rotate and lifecycle is handled by logback. This is partial of my logback xml configuration: <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"><discriminator> <key>id</key> <defaultValue>main</defaultValue></discriminator><sift> <appender name="${id}Rolling" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> <fileNamePattern>${logRoot}/${id}.%d{"yyyy-MM-dd-HH", UTC}.%i.json</fileNamePattern> <maxFileSize>${logSizeLimit}</maxFileSize> <maxHistory>100</maxHistory> <totalSizeCap>20GB</totalSizeCap> </rollingPolicy> <encoder> <pattern>%msg%n</pattern> </encoder> </appender></sift> And in the java code: String jsonOutput = gson.toJson(ping); MDC.put("id", id)); logger.info(jsonOutput); MDC.remove("id"); The output log looks like : {"timestamp":{"seconds":1557048143,"nanos":028000000},"httpRequest":{"status":200,"remoteIp":"111.11.111.111","requestMethod":"GET","requestUrl":" https://my.example.com/?id=testid","userAgent":"Mozilla/5.0 "}} ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@{"timestamp":{"seconds":1557041043,"nanos":318000000},"httpRequest":{"status":200,"remoteIp":"111.11.111.111","requestMethod":"GET","requestUrl":" https://my.example.com/?id=testid","userAgent":"Mozilla/5.0 "}} I am using vim to open it, so it displays null character as ^@. These null characters are appended at the beginning of a real log message. I haven't found a pattern when this will happen. Does anyone have any idea why this happens? Best regards, TJ Liu

1 0

No logfile when starting application from a remote host
by Michael.Fankanowsky＠t-systems.com 13 May '19

13 May '19

Hi, we are using logback v1.2.3 in a Springboot application which is running on Linux. When starting the application locally on the Linux host, logfile is created and application logs to it. When starting the application from a remote host via ssh then no logfile is created. When restarting the application (logfile is present and application has been logging to it) from a remote host, then no log messages will be logged to the existing logfile. It is working when restarting the application locally on the Linux host. Does anyone have an idea concerning this behavior? Best regards, Michael Fankanowsky

2 1

Re: [logback-user] No logfile when starting application from a remote host
by Ceki Gülcü 13 May '19

13 May '19

access right issue? -------- Original message --------From: Michael.Fankanowsky(a)t-systems.com Date: 5/13/19 11:32 (GMT+01:00) To: logback-user(a)qos.ch Subject: [logback-user] No logfile when starting application from a remote host Hi, we are using logback v1.2.3 in a Springboot application which is running on Linux. When starting the application locally on the Linux host, logfile is created and application logs to it. When starting the application from a remote host via ssh then no logfile is created. When restarting the application (logfile is present and application has been logging to it) from a remote host, then no log messages will be logged to the existing logfile. It is working when restarting the application locally on the Linux host. Does anyone have an idea concerning this behavior? Best regards, Michael Fankanowsky

3 7