- logback-user - mailman3.qos.ch

Java programmatic configurations
by Martinus Martinus 05 Jul '12

05 Jul '12

Hi, What is the equivalent programmatical java code for below logback.xml configuration : <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger - %msg%n</pattern> </encoder> </appender> <appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> * <syslogHost>myhost</syslogHost>* * <facility>USER</facility>* * <suffixPattern>[%thread] %logger *%msg</suffixPattern> </appender> <root level="debug"> <appender-ref ref="SYSLOG"/> <appender-ref ref="STDOUT"/> </root> </configuration> Thanks.

1 0

Log method name and line number only for exceptions
by lopardo . 04 Jul '12

04 Jul '12

Hi. Is it possible to log method name and line number only for exceptions? Or set a different pattern, but only for exceptions? That way I could log more info, even if it's slower to process, for some exceptions. Thanks. Regards, lopardo.

2 1

Java programmatic configurations
by Martinus Martinus 04 Jul '12

04 Jul '12

Hi, What is the equivalent programmatical java code for below logback.xml configuration : <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger - %msg%n</pattern> </encoder> </appender> <appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> * <syslogHost>myhost</syslogHost>* * <facility>USER</facility>* * <suffixPattern>[%thread] %logger *%msg</suffixPattern> </appender> <root level="debug"> <appender-ref ref="SYSLOG"/> <appender-ref ref="STDOUT"/> </root> </configuration> Thanks.

1 0

DuplicateMessageFilter
by the KD 02 Jul '12

02 Jul '12

I have a situation where we need to limit the number of errors logged and sent to production support. I first thought this filter might be useful, but after analyzing our need, we feel it is not useful. For example, if I limit it to 3 times of repetition, how do we now if the error was fixed or it simply was not thrown due to the filtering? My suggestion is, it can be more useful for practical purpose if there can be some "time duration" parameter in it where one specifies, for example, 1 hr, or 1 minute, to indicate that the error cannot be repeated this many times within certain duration. Kevin -- View this message in context: http://old.nabble.com/DuplicateMessageFilter-tp34083524p34083524.html Sent from the Logback User mailing list archive at Nabble.com.

1 0

additional feature for DuplicateMessageFilter desired
by the KD 27 Jun '12

27 Jun '12

I tried to use this filter for limiting number of errors sent to production support. but, without a time duration, it is not practical, because if i set the repetition limit to 3, for example, it will be never logged again. this is not good since i won't be able to tell whether this is caused by the problem being gone or by the filtering. it would be more useful, for my purpose at least, to have some property specifiying some time window. For example, drop logging if within 1 hour a message have been repeated more than 3 times. this will limit the number of repeated messages, but also keep throwing them to indicate the continued existence of the error. -- View this message in context: http://old.nabble.com/additional-feature-for-DuplicateMessageFilter-desired… Sent from the Logback User mailing list archive at Nabble.com.

2 1

Problems with jaino evaluator
by George, Kenneth V [NTK] 22 Jun '12

22 Jun '12

Good afternoon. I have a situation where I need to log information to 2 separate files, but under different conditions, for the same context/class files. Basically, I have 2 files: 1 log, 1 alarm_log. I need to set the level for reporting to INFO, but only log WARN/ERROR messages to alarm_log when a MDC value of "SEND_ALARM" is set. I have tried to place a <filter> of type "ch.qos.logback.core.filter.EvaluatorFilter" and cannot seem to get it to work, messages of Level INFO show-up in the alarm_log. Can this even be done (maybe I am just using it wrong)? Here is the section of my logback.xml file specifying the appender: <appender name="ALARM" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression> if (mdc == null || mdc.get("SEND_ALARM") == null) return false; return true; </expression> </evaluator> </filter> <file>logs/alarms.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>logs/archive/logFile.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date{MMM dd, yyyy hh:mm:ss} %-5level %msg%n</pattern> </encoder> </appender> Thanks. ________________________________ This e-mail may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.

3 11

Re: [logback-user] Problems with jaino evaluator
by George, Kenneth V [NTK] 22 Jun '12

22 Jun '12

Can anyone speak to this issue? From: George, Kenneth V [NTK] Sent: Wednesday, June 20, 2012 12:34 PM To: 'logback users list' Subject: Problems with jaino evaluator Good afternoon. I have a situation where I need to log information to 2 separate files, but under different conditions, for the same context/class files. Basically, I have 2 files: 1 log, 1 alarm_log. I need to set the level for reporting to INFO, but only log WARN/ERROR messages to alarm_log when a MDC value of "SEND_ALARM" is set. I have tried to place a <filter> of type "ch.qos.logback.core.filter.EvaluatorFilter" and cannot seem to get it to work, messages of Level INFO show-up in the alarm_log. Can this even be done (maybe I am just using it wrong)? Here is the section of my logback.xml file specifying the appender: <appender name="ALARM" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression> if (mdc == null || mdc.get("SEND_ALARM") == null) return false; return true; </expression> </evaluator> </filter> <file>logs/alarms.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>logs/archive/logFile.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date{MMM dd, yyyy hh:mm:ss} %-5level %msg%n</pattern> </encoder> </appender> Thanks. ________________________________ This e-mail may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.

1 0

Getting class packaging information with IThrowableRenderer
by Thilo-Alexander Ginkel 20 Jun '12

20 Jun '12

Hi there, I very much like the class packaging information displayed for a stacktrace with the %xEx{depth} pattern. Due to its IThrowableRenderer mechanism, using %xEx{depth} with an HTMLLayout does not seem to make much sense, though. OTOH, the DefaultThrowableRenderer does not seem to emit this information by default (nor does it seem to be configurable). Is there a way to get this class packaging information for information rendered by a HTMLLayout's IThrowableRenderer without reinventing the wheel? If the latter is needed, where is the code implemeting the class packaging information retrieval for %xEx{depth} located? Thanks, Thilo

2 1

Approaches to implement RFC5424 structured data support
by Thilo-Alexander Ginkel 20 Jun '12

20 Jun '12

Hi there, I was wondering whether anyone has so far been successful in implementing RFC5424 [1] structured data syslog support using logback (despite it probably being DOA [2] - the alternatives are IMHO currently in a too early stage). In the archives I see one attempt at a pretty invasive approach that altered the logback implementation itself (unfortunately, the fork over at Github seems to be no longer maintained) as well as a proposal [3] to use a custom encoder along with a special "RFC5424Aware" interface. Would the latter still be the preferred way to go? Reading through the code, I guess a custom Layout (that knows how to deal with RFC5424Aware instances) should also do the trick... I guess one would also need to replace SyslogStartConverter due to the changed message header... Any input is appreciated! Thanks, Thilo [1] http://tools.ietf.org/html/rfc5424 [2] http://www.gossamer-threads.com/lists/rsyslog/users/6361 [3] http://mailman.qos.ch/pipermail/slf4j-dev/2010-March/002878.html

3 3

how to get all configured appenders over api
by ralph 19 Jun '12

19 Jun '12

hello I need for a dynamic configuration of a logger, the list of all configured appenders (e.g all FileAppender) even if some appenders are initially not attached to any loggers ch.qos.logback.classic.Logger log = (ch.qos.logback.classic.Logger) LoggerFactory.getLogger("de.foo" ); log.setLevel( Level.DEBUG ); log.setAdditive( false ); log.addAppender( ????? ) how can I get this list of appenders over the logback api? Regards Ralph

1 0