December 2017 - logback-user

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

Delaying debug logs until an error occurs
by Håvard Ottestad 31 Dec '17

31 Dec '17

Hi, Happy new year :D I have a question that I’m having trouble formulating. My goal is to reduce the amount of logging in my application, but still log debug messages when there has been an error. I’m wondering if there is a way to have logback “save” debug messages and only log them if an error is logged at some point later on in the same transaction. Eg. A spring web application. The user uploads a file, and at some point in the processing of the file an error occurs. Would be great now if the application would print out all debug messages associated with the file upload (including messages logged before the error), so that it would be possible to trace what happened leading up to the error. Having debug, info, warn and error on in production produces too many logs, which means we can’t keep them as long as we would like. So being able to trigger logging of previous debug messages on an error would give us a high level of detail in our logs when we need it the most. Cheers, Håvard

2 1

getting logback to scale on multitenant app
by Jamie 15 Dec '17

15 Dec '17

Hi I'd appreciate guidance on how to get Logback to use less resources in our multitenant app. It seems every time we add a new tenant, log back creates a few more async appender threads. This affects the scalability of our software. In our app, each tenant has an audit and a debug log. Async apppender is being used to write to each log respectively. Our problem is that whenever a new tenant is added, many more threads get created. it seems a new worker thread is assigned to each appender. Is there a way to get Logback to rather use a shared thread pool? Stacks at 2017-12-14 10:33:57 PM (uptime 22m 24s) AsyncAppender-Worker-audit-template [WAITING] [DAEMON] sun.misc.Unsafe.park(boolean, long) Unsafe.java (native) java.util.concurrent.locks.LockSupport.park(Object) LockSupport.java:175 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() AbstractQueuedSynchronizer.java:2039 java.util.concurrent.ArrayBlockingQueue.take() ArrayBlockingQueue.java:403 ch.qos.logback.core.AsyncAppenderBase$Worker.run() AsyncAppenderBase.java:289 Thanks in advance Jamie

2 3

Redirecting JDK 9's JVM logs to Logback?
by Osvaldo Doederlein 05 Dec '17

05 Dec '17

Hi, I want to redirect the JVM's internal logs to Logback, is this possible? More specifically, I have all my app logs going to a single appender and I want JVM logs such as GC to be writing to the same appender, interleaved with app logs. I have Logback configured with slf4j and jul-to-slf4j, also I wrote a System.LoggerFinder service to redirect System.Logger to SLF4J->Logback, which I can see working for core lib logs such as java.base / sun.net.www.protocol.http.HttpURLConnection. (See http://openjdk.java.net/jeps/158) However, the GC logs are still going to stdout. The documentation for JEP 158 seems to imply that the JVM logs are something separate from java.util.logging, can only be sent to stderr, stdout or a log file, but not to a JUL logger. I know that I can hook the System.out/err streams and redirect writes to a logger, but this is not ideal, for one thing I cannot configure Logback to send logs back to stdout (which I often do in test/interactive runs) without risking a stack overflow. I could write code that walks the stack to decide if the call to System.err/out is coming from a logger, but this is expensive. Anyone knows a magic trick here? :-) -- Osvaldo Doederlein | https://twitter.com/opinali | https://plus.google.com/+OsvaldoDoederlein

3 3