- logback-user - mailman3.qos.ch

Best Practice to Setup Multiple Log Files for Multiple Classes
by Dan Franks 11 Oct '12

11 Oct '12

Hello all, I think my question has been answered before, but I will be damned if I can find it. Basically I have three classes (orangeClass, purpleClass, greenClass) that I want to log to their respective files (orangeFile, purpleFile, and greenFile). I would need to have a default log file that catches everything not coming from those classes as well. The last requirement is that I can change each one to debug/warn/info independently of each other. Can you point me in the right direction? Thanks in advance, Dan

3 11

Add header-lines to each log file
by Schoeftner, Thomas 11 Oct '12

11 Oct '12

Hi everyone, one of our services is currently using a plain RollingFileAppender for logging to the file system. A new requirement just popped up, which demands to add a specific headline in each log file (on top of it) to only add this information once (e.g. if my service gets restarted and logback picks up a pre-existing log-file) not to automatically roll-over to a new log file if my service gets restarted (time windows and log-files need to correlate) - still only 1 headline per file. I think this would be best solved on logback-configuration level, but I am not sure how. I hope this is not an entirely uncommon need. - Maybe you can help. Thanks a ton! -Tom

1 0

How to set dialect for a DBAppender
by Jeffrey B 10 Oct '12

10 Oct '12

I getting the following error, when I try to use a DBAppender: ch.qos.logback.core.db.DriverManagerConnectionSource@7d8a8ce2 - Could not discover the dialect to use. java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection at java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection at at oracle.jdbc.driver.T4CConection.logon(T4CConnection.java:419) How do I manually set the sql dialect to use, in the logback xml configuration file (ie- xml tag name to use, etc...), assuming I am getting a dialect error? Thank you Jeff

1 0

how to append logs to syslog without opening udp ports
by Sumanth MS 05 Oct '12

05 Oct '12

Hello, I am trying to use logback logging functionality on our java code and am trying to use syslog appender. Basically I want all the logs to get logged into the syslog(in my own machine) without syslog opening the udp ports! Is there any way of doing it? In the documentation for syslog appender, it is mentioned to verify whether the remote syslog daemon accepts request from an external source! But I do not want the logging to take place in a remote syslog. I want it to be logged in my own machine's syslog daemon without explicitly having to open up the udp ports for that! Is there a way of doing it? Or should I use syslog4j for doing it? Please do suggest! Thanks & Best Regards Sumanth

1 0

Passing logger level via parameter or determining programmatically?
by Smith, Larry (ECS - Enterprise Cloud Service) 05 Oct '12

05 Oct '12

Hi all, Is there any way to accomplish setting a log level (error, warn, ...) via a parameter, so that I do not have to explicitly code logger.error(...), logger.warn(...)? I would like to be able to code something like logger.log("foo={}", foo); and have it determine the level based on a previously set value. If I could do something like this, then I could change the logging level dynamically in specific classes, rather than changing the level for an entire class as I've seen discussed in the past. Thanks, Larry Smith

2 2

java.net.UnknownHostException in ch.qos.logback.core.util.ContextUtil on startup
by Marshall Pierce 25 Sep '12

25 Sep '12

I get the following (and other statuses) printed to stdout on startup on a box running inside Amazon VPC. 04:55:44,918 |-ERROR in ch.qos.logback.core.util.ContextUtil@5328f6ee - Failed to get local hostname java.net.UnknownHostException: ip-10-0-4-173: ip-10-0-4-173 at java.net.UnknownHostException: ip-10-0-4-173: ip-10-0-4-173 at at java.net.InetAddress.getLocalHost(InetAddress.java:1426) at at ch.qos.logback.core.util.ContextUtil.getLocalHostName(ContextUtil.java:32) at at ch.qos.logback.core.util.ContextUtil.addHostNameAsProperty(ContextUtil.java:41) at at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:56) at at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:276) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:148) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:130) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:157) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:143) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:106) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:56) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:148) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:54) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281) This is, unfortunately, breaking the tool that is running this code since it uses stdout to pipe data to other processes. (Seehttp://jira.qos.ch/browse/LOGBACK-292 for more on the fact that statuses are output to stdout even in the case of this automatic error-triggered output.) My config file is: <configuration> <appender name="STDERR" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> <target>System.err</target> </appender> <root level="WARN"> <appender-ref ref="STDERR"/> </root> </configuration> This config works, and all of the other statuses are just INFO's. I'm not using the hostname anywhere, and I do not care about it at all, so it's unfortunate that Logback seems to insist on complaining about it when I'm not actually using it. The "HOSTNAME" property is set presumably so that the property can be used during configuration. ContextBase#getProperty(String) already has a special case in it: public String getProperty(String key) { if (CONTEXT_NAME_KEY.equals(key)) return getName(); return (String) this.propertyMap.get(key); } What do you think about having another special case added to getProperty to lazy-load the hostname?

1 0

Filtering "unknown" mdc discriminator events
by Fred Toth 22 Sep '12

22 Sep '12

Hi, This has been written about before in this list, and I thought it would be easy, but I'm getting nowhere. Can anyone suggest what I'm doing wrong? I can confirm that my filter code is running (I see the print statements) but no matter what I return, I still end up with a log like "unknown/batchqc-<timestamp>" containing plenty of log data. I would like to eliminate these logs completely, and write logs using this sifter only when articlePath is set. The status listener is reporting: 12:03:35,652 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@25:37 - no applicable action for [OnMismatch], current pattern is [[configuration][appender][filter][evaluator][OnMismatch]] 12:03:35,652 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@26:34 - no applicable action for [OnMatch], current pattern is [[configuration][appender][filter][evaluator][OnMatch]] What am I missing? Config: <configuration> <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener"/> <timestamp key="bySecond" datePattern="yyyy-MM-dd-HH-mm-ss" /> <timestamp key="byDate" datePattern="yyyy-MM-dd" /> <appender name="ARTICLESIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator> <key>articlePath</key> <defaultValue>unknown</defaultValue> </discriminator> <sift> <appender name="ARTICLESIFT-APPENDER" class="ch.qos.logback.core.FileAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator class="ch.qos.logback.classic.boolex.JaninoEventEvaluator"> <expression> System.out.println("MDC: " + mdc + " " + mdc.get("articlePath")); if (mdc == null || mdc.get("articlePath") == null || ((String)mdc.get("articlePath")).contains("unknown")) return false; return true; </expression> <OnMismatch>NEUTRAL</OnMismatch> <OnMatch>DENY</OnMatch> </evaluator> </filter> <file>${articlePath}/batchqc-${bySecond}.log</file> <append>false</append> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %logger{0} - %msg%n </pattern> </encoder> </appender> </sift> </appender> <appender name="TSFILE" class="ch.qos.logback.core.FileAppender"> <file>logs/batchqc-${byDate}.log</file> <append>true</append> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %logger{0} - %msg%n</pattern> </encoder> </appender> <root level="info"> <appender-ref ref="TSFILE" /> <appender-ref ref="ARTICLESIFT" /> </root> </configuration> Thanks, Fred

2 4

How to use different xml settings file for logback depending on run.mode
by Olek Swirski 20 Sep '12

20 Sep '12

Hi, I'm using logback in a runnable jar containing a lift webapp. logback reads its settings from logback.xml file at the root of the jar. This runnable jar can be run in development mode by just using: java -jar myexecutable.jar but also in production mode: java -Drun.mode=production -jar myexecutable.jar I would like to be able to use different file for logback configuration depending on the run.mode. For example in default (development) mode this could be default.logback.xml (or just logback.xml as it is by default) and in production production.default.logback.xml or in test test.default.logback.xml How do I do that? In my app, there is a runnable object Start, with main method, where I probably could set some init options for logback depending on the run mode, which can be detected with System.getProperty("run.mode"). Here is the topic on lift mailing list, about this executable jar, and some last few messages are about trying to figure this out https://groups.google.com/forum/?fromgroups=#!topic/liftweb/uwwIA8FwmU8

2 2

Manually force the initialization of Logback
by GF 20 Sep '12

20 Sep '12

Hello everyone, I've a very uncommon configuration. I'm on SAP Netweaver AS :-( For some class loading reasons, I need to deploy separately a .ear file containing the Hibernate .jar files and all the .jar dependencies of hibernate (including log4j, slf4j-api and commons-logging) as a so called by SAP, "heavy resource" http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/bf0d57db-0c01-0010-6… Then I deploy separately the application .ear that does NOT contain the .jar already included in the hibernate .ear With log4j it worked. Now if... 1) I include all the logback libraries in the hibernate .ear I don't get any error, but when I deploy the application .ear logback doesn't start working! probably because the logback-* files are not in that .ear and they doesn't look for the logback.xml (that I included correcty, and locally on tomcat works...) And if.. 2) I include all logging related libraries in the application .ear when some of the classes of hibernate (that are in the other .ear) try to use something about logging, they got a class not found exception.. I'm totally confused, I'm trying to divide the libraries in many different combinations, but I didn't find any working solution. I think the case 1) might be ok, but I need to force the initialization of logback from the application.ear (that does not contain its libraries) How can I do that? can someone give me a SVN link to the code that starts all the logback stuff? I can even create just that class in my application to force logback initialization.. Thanks

1 0

LOGBACK-750 Syslogappender: missing stacktrace header lines
by Ingebrigt Berg 19 Sep '12

19 Sep '12

I've created http://jira.qos.ch/browse/LOGBACK-750 (which turned out to be a duplicate of http://jira.qos.ch/browse/LOGBACK-411) Also coded a fix and issued a pull request: https://github.com/qos-ch/logback/pull/61 cheers, Ingebrigt Berg

1 0