March 2016 - logback-user - mailman3.qos.ch

Logback => TLS/SSL => Syslog ?
by Otis Gospodnetić 21 Feb '19

21 Feb '19

Hi, Does Logback support sending logs to Syslog servers via TLS/SSL? I have a feeling Logback doesn't have a SyslogAppender that can send data using TLS. I say that because I don't see a mention of "syslog" on http://logback.qos.ch/manual/usingSSL.html and I see http://jira.qos.ch/browse/LOGBACK-890 that mentions TLSSyslogAppender, but it looks like this never ended up in Logback. I've only found it committed here: https://github.com/balabit/logback/commit/e0d89de2536e0925a6c816a50793f6a74… Could anyone please clarify? Thanks, Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/

2 1

produce configuration file from current configuration?
by Norbert Kiesel 07 Apr '16

07 Apr '16

Hi, we finally switched from a home-grown logging system to slf4j/logback and are overall happy. However, the old solution (which was much more limited) offered a web GUI for setting the root log level. We could of course implement that using the logback API. However, this will of not be reflected in our logback.xml. I'm also worried that any other change in that file will simply reset the log level given that we use the `scanPeriod` option. Is there a way to convert a current logback configuration back into an XML (or Groovy) configuration file? </nk> --- Norbert Kiesel Systems Architect | Engineering MetricStream 2600 E. Bayshore Road | Palo Alto, CA - 94303 +1-650-620-2954 | nkiesel(a)metricstream.com | www.metricstream.com Confidentiality Notice:This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited

2 3

[ConfigurationDelegate.groovy] LogstashTcpSocketAppender
by Daniel Pacak 31 Mar '16

31 Mar '16

Hi, In a Grails app for my customer I'm using the LogstashTcpSocketAppender provided by this project https://github.com/logstash/logstash-logback-encoder. It works perfectly fine with the logback.xml configuration which looks as follows: <?xml version="1.0" encoding="UTF-8"?> <configuration> <shutdownHook class="ch.qos.logback.core.hook.DelayingShutdownHook"/> <appender name="console" class="ch.qos.logback.core.ConsoleAppender"/> <appender name="tcp" class="net.logstash.logback.appender.LogstashTcpSocketAppender"> <destination>localhost:4560</destination> <encoder class="net.logstash.logback.encoder.LoggingEventCompositeJsonEncoder"> <providers> <message/> <mdc/> <arguments/> </providers> </encoder> </appender> <root level="all"> <appender-ref ref="console"/> <appender-ref ref="tcp"/> </root> </configuration> However I had hard time configuring the same in logback.groovy; Do you have any idea how to configure LogstashTcpSocketAppender in groovy style? So far I came up with the following snippet which sucks a bit because it depends on Logback internals (mixed in ConfigurationDelegate properties/methods): import ch.qos.logback.core.Appender import net.logstash.logback.appender.LogstashTcpSocketAppender import net.logstash.logback.composite.JsonProviders import net.logstash.logback.composite.loggingevent.ArgumentsJsonProvider import net.logstash.logback.composite.loggingevent.MdcJsonProvider import net.logstash.logback.composite.loggingevent.MessageJsonProvider import net.logstash.logback.encoder.LoggingEventCompositeJsonEncoder appender('STDOUT', ConsoleAppender) { encoder(PatternLayoutEncoder) { pattern = '%-4relative [%thread] %msg%n' } } addAppender('LOGSTASH_TCP', createLogstashTcpSocketAppender('localhost:4560')) root(DEBUG, ['STDOUT', 'LOGSTASH_TCP']) println appenderList Appender createLogstashTcpSocketAppender(String destination) { LoggingEventCompositeJsonEncoder encoder = new LoggingEventCompositeJsonEncoder() JsonProviders providers = new JsonProviders() providers.addProvider(new MessageJsonProvider()) providers.addProvider(new MdcJsonProvider()) providers.addProvider(new ArgumentsJsonProvider()) encoder.setProviders(providers) Appender appender = new LogstashTcpSocketAppender() appender.addDestination(destination) appender.setEncoder(encoder) appender } void addAppender(String name, Appender appender) { appender.name = name appender.context = context appenderList.add(appender) appender.start() } Regards, Daniel Pacak

2 2

error log : one email per request
by Weipeng He 25 Mar '16

25 Mar '16

Hi all, I am using SMTPAppender for error report in a web application. Using default setting, the logger sends one email per log message. However, I was trying make it like this : * All the messages logged during one request handling are grouped into one email, and the email is sent only when error occurs (i.e. at least one of log events is at level ERROR) Is there any easy way to implement this? Thank you. Best, Weipeng

2 5

Try to use an evaluator JaninoEventEvaluator in logback. But does not work to filter out depending on condition
by skasish 24 Mar '16

24 Mar '16

Try to use an evaluator JaninoEventEvaluator in logback. But does not work to filter out depending on condition. My configuration of logback.xml is given below. <appender name="durgaDlyFileSQL" class="ch.qos.logback.core.FileAppender"> <File>${durga.log.file.name.SQL}</File> <encoder> <pattern>${ScreenConversionPattern}</pattern> </encoder> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="loggingTaskEval" class="ch.qos.logback.classic.boolex.JaninoEventEvaluator"> <expression> System.out.println("MDC: " + mdc + " " + mdc.get("screenName")); String screen = (String) mdc.get("screenName"); if ((screen == null) || screen.equals("Server Type Entry/Amend/Cancel")) { return false; } </expression> </evaluator> <onMatch>ACCEPT</onMatch> <onMismatch>DENY</onMismatch> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${durga.log.file.name.SQL}.%d{${finch.log.file.DefaultRolloverFrequency}}</fileNamePattern> </rollingPolicy> </appender> and the output of the log: [17 Mar 2016 13:42:18.437][Server Type Entry/Amend/Cancel][durga_admin] TRACE o.h.type.descriptor.sql.BasicBinder 83 binding parameter [3] as [VARCHAR] - durga_admin [17 Mar 2016 13:42:18.438][Server Type Entry/Amend/Cancel][durga_admin] TRACE o.h.type.descriptor.sql.BasicBinder 83 binding parameter [4] as [TIMESTAMP] - 2016-03-17 08:16:23.0 [17 Mar 2016 13:42:18.439][Server Type Entry/Amend/Cancel][durga_admin] TRACE o.h.type.descriptor.sql.BasicBinder 83 binding parameter [5] as [TIMESTAMP] - 2016-03-17 08:16:23.0 [17 Mar 2016 13:42:18.440][Server Type Entry/Amend/Cancel][durga_admin] TRACE o.h.type.descriptor.sql.BasicBinder 83 binding parameter [6] as [VARCHAR] - durga_admin [17 Mar 2016 13:42:18.441][Server Type Entry/Amend/Cancel][durga_admin] TRACE o.h.type.descriptor.sql.BasicBinder 83 binding parameter [7] as [INTEGER] - 0 I do not want log when screenName = "Server Type Entry/Amend/Cancel" I'm using janino 2.5.10 and logback 1.1.7 and all the stuff is running on a tomcat 7.0.47 -- View this message in context: http://logback.10977.n7.nabble.com/Try-to-use-an-evaluator-JaninoEventEvalu… Sent from the Users mailing list archive at Nabble.com.

2 1

Introducing logback-configuration
by Martin Todorov 16 Mar '16

16 Mar '16

Hi, I hope you are well! Thanks for devising such great logging frameworks over the years! I would like to bring to your attention a small project we put together recently for the need of another project we were working on: https://github.com/carlspring/logback-configuration It provides a way to easily configure/reconfigure Logback and it contains a simple service and restlet around it. When we looked around for something similar, there wasn't something as straight-forward as this to follow. Perhaps it could be further extended in the future, if there is a need. Looking forward to hearing from you! Kind regards, Martin Todorov

2 4

Some questions about DBAppender of the logback
by Yun He 14 Mar '16

14 Mar '16

Hi,everyone, Following is my logback.xml about implement DBAppender just to storage the log message to mysql database. <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>com.mysql.jdbc.Driver</driverClass> <url>jdbc:MySQL://127.0.0.1:3306/EventDataBase</url> <user>root</user> <password>root</password> </connectionSource> </appender> then: The following is the result ,the log message was storage in the mysql database,but the "timestmp" filed in the table named logging_event ,the timestmp's pattern is not as{HH:mm:ss.SSS} just as the consoleAppender,can I transform it's pattern to {HH:mm:ss:SSS} ? Could you please give me some help?I have tried add <encoder> <pattern>%d{HH:mm:ss.SSS} </pattern></encoder> as the ConsoleAppender's logback.xml,but I failed.

3 2

System property based Discriminator
by DK 11 Mar '16

11 Mar '16

I'm trying to split logs based on a System property that changes dynamically at runtime.Is the below Discriminator code the way to go?Will this Discriminator get called for every log statement? import ch.qos.logback.classic.spi.ILoggingEvent;import ch.qos.logback.core.sift.AbstractDiscriminator;public class SysPropDiscriminator extends AbstractDiscriminator { private static final String KEY = "PROP"; @Override public String getDiscriminatingValue(ILoggingEvent event) { String propValue = System.getProperty("my.property"); if (propValue == null || propValue.length() == 0) { return "unknown"; } else { return propValue; } } @Override public String getKey() { return KEY; }} -- View this message in context: http://logback.10977.n7.nabble.com/System-property-based-Discriminator-tp14… Sent from the Users mailing list archive at Nabble.com.

3 3

Encoder definition not shareable
by Stevo Slavić 04 Mar '16

04 Mar '16

Hello Logback community, Please correct me if wrong, but it doesn't seem possible to share encoder definition in multiple appenders. I guess there is a reason why encoder instances cannot be shared, but wouldn't it be possible to support at least sharing definition? Now I have to resort to copy-pasting same encoder definition multiple times which is suboptimal, not DRY. Kind regards, Stevo Slavic.

2 2

log4j to logback translation issues - $ char in logger name, and rolling policy
by Stevo Slavić 04 Mar '16

04 Mar '16

Hello Logback community, I converted Apache Kafka log4j.properties to logback.xml using http://logback.qos.ch/translator/ Translator didn't report invalid '$' char in logger name, only when running app, logback threw exception: 16:07:38,628 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@701:80 - RuntimeException in Action for tag [logger] java.lang.IllegalArgumentException: Failed to parse input [kafka.network.RequestChannel$] at java.lang.IllegalArgumentException: Failed to parse input [kafka.network.RequestChannel$] at at ch.qos.logback.core.util.OptionHelper.substVars(OptionHelper.java:114) at at ch.qos.logback.core.joran.spi.InterpretationContext.subst(InterpretationContext.java:157) at at ch.qos.logback.classic.joran.action.LoggerAction.begin(LoggerAction.java:44) at at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:269) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:145) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:128) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:148) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:100) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:50) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:147) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:122) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:378) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:328) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:349) at at org.apache.kafka.common.utils.Utils.<clinit>(Utils.java:54) at at kafka.Kafka$.getPropsFromArgs(Kafka.scala:41) at at kafka.Kafka$.main(Kafka.scala:57) at at kafka.Kafka.main(Kafka.scala) Caused by: ch.qos.logback.core.spi.ScanException: Unexpected end of pattern string at at ch.qos.logback.core.subst.Tokenizer.tokenize(Tokenizer.java:70) at at ch.qos.logback.core.subst.NodeToStringTransformer.tokenizeAndParseString(NodeToStringTransformer.java:53) at at ch.qos.logback.core.subst.NodeToStringTransformer.substituteVariable(NodeToStringTransformer.java:46) at at ch.qos.logback.core.util.OptionHelper.substVars(OptionHelper.java:112) at ... 23 common frames omitted Should $ char be allowed in logger name? In other words is it bug in configuration if one uses it or is it bug in logback that it doesn't handle it well? I'm using logback 1.7.18. Secondly, translator had problems converting data pattern like: log4j.appender.kafkaAppender=org.apache.log4j.DailyRollingFileAppender log4j.appender.kafkaAppender.DatePattern='.'yyyy-MM-dd-HH log4j.appender.kafkaAppender.File=${kafka.logs.dir}/server.log it converted that to ... <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${kafka.logs.dir}/server.log.%d{'.'yyyy-MM-dd-HH}</fileNamePattern> </rollingPolicy> ... where Logback complained about that dot '.' in fileNamePattern as invalid. Lastly, it seems in Logback specification when to roll (e.g. daily) and what should be format and info included in the file name are tightly coupled. Kind regards, Stevo Slavic.

2 2