June 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

Avoid pre-initialization upon the first LoggerFactory.getILoggerFactory();
by Brice Dutheil 08 Jul '16

08 Jul '16

Hi, I would like share a single log configuration for two web-apps that run on the same container. Yet I want each web-app to log in separate files. I tried different approach the best one is actually very close to some solution I later found on the FAQ : http://logback.qos.ch/faq.html#sharedConfiguration LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator jc = new JoranConfigurator(); jc.setContext(loggerContext); loggerContext.reset(); loggerContext.setName(appName); // use ${CONTEXT_NAME} in logback.xml jc.doConfigure(Objects.requireNonNull(source, "Logback configuration is missing")); However for operation reasons we pass the configuration via the system property logback.configurationFile, so what happens is that the first call to LoggerFactory.getILoggerFactory() initialise the LoggerContext and creates files with non initialised variables. As I’m using the context name, the file names have default in their name (this is the default value of the context name), if using variable I get a filename with my-var-name_IS_UNDEFINED. *The question is :* Is there proper way anyway to avoid this pre-initialisation to avoid creating this empty file ? I didn’t found any way to hook in the org.slf4j.LoggerFactory or org.slf4j.impl.StaticLoggerBinder (of logback-classic). — Brice

3 6

Question regarding appenders
by Jose Monreal Bailey 04 Jul '16

04 Jul '16

Good day everyone, Is it possible to have a Console Appender using an AsyncAppender? Does it make sense? I have an logback configuration that seems not to be working, and perhaps it's because of a misconfiguration. Regards, J

2 1

logback additivity level is not working
by Ted Smith 24 Jun '16

24 Jun '16

Hello: I have the following config <logger name="a.b.c.Klass" level="trace" additivity="true"> <appender-ref ref="aSiftAppenderUsingCustomMarker" /> </logger> <logger name="a.b" level="error" additivity="false"> <appender-ref ref="errorAppender" /> </logger> as you can see, I am trying to capture all "error" level messages (and discard lower levels) from child loggers into the "errorAppender", even though child loggers are at trace level, which would log to their own siftAppenders. But all the trace logs still get into error appenders, even though the level is clearly set to "error" Could it be due to the use of marker or siftappender in my log like log.trace(marker,message) but the error logger should still check the level and disregard any marker info. Thanks in advance for your help

2 2

Dynamically change a variable value for file location
by Douglas Moraes 24 Jun '16

24 Jun '16

Hi, I want to save my log file in a directory accordingly the current day. For example, if today is 0614 (June 14th), all log events will go to a folder 0614, and tomorrow I want the logs to go to 0615. I don´t want use rolling policy. I mean, I want the file to be directly created in the right place, and not saved in a temporary place and in other day to be saved in an archive place. I tryed: <configuration> <timestamp key="DIR" datePattern="MMdd" /> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>./log/${DIR}/gp2b.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>app.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>10</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>5MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36}:%L - %msg%rEx{10}%n</pattern> </encoder> </appender> <logger name="com.ocs.ProxyHttp.gp2b" level="DEBUG" /> <root level="DEBUG"> <appender-ref ref="FILE" /> </root> </configuration> Thanks, Douglas

2 3

GEventEvaluator/JaninoEventEvaluator filter doesn't work
by nagendra 21 Jun '16

21 Jun '16

Hi, I am trying to GEventEvaluator/JaninoEventEvaluator filter but expression is not working...it keeps print messages even condition is false. i am using groovy configuration. and logback 1.0.13 and janino 2.7.8. i am getting the following error in trace. 17:04:07,255 |-ERROR in ch.qos.logback.classic.gaffer.AppenderDelegate@12a94400 - Appender [SELM] of type [ch.qos.logback.core.ConsoleAppender] has no appplicable [EvaluatorFilter] property 17:04:07,265 |-ERROR in ch.qos.logback.classic.gaffer.AppenderDelegate@12a94400 - Unexpected argument type org.codehaus.groovy.runtime.NullObject 17:04:07,265 |-ERROR in ch.qos.logback.classic.gaffer.AppenderDelegate@12a94400 - No 'class' argument specified for [filter] in appender [SELM] of type [ch.qos.logback.core.ConsoleAppender] -------------------------------------------------------------- config file appender("SELM", ConsoleAppender) { filter(EvaluatorFilter) { evaluator(GEventEvaluator) { expression = '(e.mdc?.get("job_name").contains("selm") )' } onMismatch = DENY onMatch = NEUTRAL } encoder(PatternLayoutEncoder) { pattern = "%date %-5level [${pid}-${HOSTNAME} %thread] %logger{30} - %msg %ex{full}%n" } }

2 1

Multiple webapps, one shared external configuration file
by Thomas Meyer 20 Jun '16

20 Jun '16

Hi, I stumbled upon this SO http://stackoverflow.com/questions/10465301/tomcat-war-configure-logback-to… So is it a good idea to have multiple web apps all using the same config file? What is the potential drawback of above solution besides all app using the same default context? The last sentence "Such involuntary sharing of the same configuration by multiple repositories will result in corrupt log output." from http://logback.qos.ch/manual/contextSelector.html implies some problems but doesn't explain why. The underlying idea in log back seems to be this: Always package the config file in your app, if you need a different test config also put test log back config file into your test class path. Having multiple target environments with potentially different logging requirements doesn't fit above model and it would be good to externalise the log back config file. But sadly only one config file is supported with a system property. So what is the best solution for having multiple web apps on a tomcat and having multiple target environment with potential different logging requirements. What is a good solution pattern for this? PS: using the JNDI ContextSelector only seems to search in the web app itself for the config file. With kind regards Thomas Meyer

2 1