- logback-user - mailman3.qos.ch

Re: [logback-user] Looking for details about AsyncAppender properties
by David Roussel 16 Jun '21

16 Jun '21

Hi David, As documented in http://logback.qos.ch/manual/appenders.html The queue in async appender is a blocking queue. So if it fills up, then the application code will block until there is space in the queue. Burg that blocking will only occur for error messages as mentioned in the above linked page; > Note that by default,AsyncAppender will drop events of level TRACE, DEBUG and INFO if its queue is 80% full. This strategy has an amazingly favorable effect on performance at the cost of event loss. So this is a reason to use a large queue size, if you want to avoid loosing info messages under high load. As for ‘ includeCallerData’, this including information about the caller of the logger, like line number and file. This takes us more memory, and not all for matters use it. David > On 22 May 2021, at 04:21, KARR, DAVID <dk068x(a)att.com> wrote: > I'm investigating what the consequences will be of changing some of our high volume logging calls to use an AsyncAppender instead of a synchronous appender. Our services run in a k8s container, so they are ultimately writing to stdout, although other processes are aggregating that log output to Splunk or ELK. > > I understand the basic idea of what the AsyncAppender will do, but I have some questions about the impact of some property settings which I cannot find details about in the documentation. > > I'm mostly interested in the "queueSize" and "includeCallerData" properties. > > Concerning "queueSize", I know it is the limit to the size of the input queue, but how exactly is that parameter utilized? Is any memory allocated based on that queue size at startup, or is it simply the limit of a dynamically expanding list? The default queue size is apparently 256. A team in our organization is planning to set this to a very large number, like 100000. Obviously, there would be considerable impact if the queue really reached that size, and I understand that. > > Concerning "includeCallerData", I understand this even less. How is this "caller data" used? What does it really represent? What is the impact of this being included or not included? I tried running tests with one service with the main high volume appender being set to use the sync appender, and then the async appender. I didn't really notice any changes in the output. > _______________________________________________ > logback-user mailing list > logback-user(a)qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-user

3 8

How can I monitor the actual size of the asyncappender queue?
by KARR, DAVID 29 May '21

29 May '21

I believe I now understand the basic mechanics of the AsyncAppender queue, and the tradeoffs of having it small or large. What's not obvious to me is how I can monitor the utilization of the queue, perhaps in a load test. I did notice there is a "listener" mechanism, and one example I believe illustrates how I can detect when logs are dropped because the queue is full, but I want to get an idea of how well the queue size is being utilized, or how close it's getting to being full.

2 6

Looking for details about AsyncAppender properties
by KARR, DAVID 21 May '21

21 May '21

I'm investigating what the consequences will be of changing some of our high volume logging calls to use an AsyncAppender instead of a synchronous appender. Our services run in a k8s container, so they are ultimately writing to stdout, although other processes are aggregating that log output to Splunk or ELK. I understand the basic idea of what the AsyncAppender will do, but I have some questions about the impact of some property settings which I cannot find details about in the documentation. I'm mostly interested in the "queueSize" and "includeCallerData" properties. Concerning "queueSize", I know it is the limit to the size of the input queue, but how exactly is that parameter utilized? Is any memory allocated based on that queue size at startup, or is it simply the limit of a dynamically expanding list? The default queue size is apparently 256. A team in our organization is planning to set this to a very large number, like 100000. Obviously, there would be considerable impact if the queue really reached that size, and I understand that. Concerning "includeCallerData", I understand this even less. How is this "caller data" used? What does it really represent? What is the impact of this being included or not included? I tried running tests with one service with the main high volume appender being set to use the sync appender, and then the async appender. I didn't really notice any changes in the output.

1 0

TimeBasedRollingPolicy not removing all old files
by Oddoy, Manuel (KVB - München) 12 Apr '21

12 Apr '21

Hello logback community, I stumbled over following situation with the TimeBasedRollingPolicy: - I have a short running application with following appender configuration <appender name="R" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>logfiles.%d{yyyy-MM-dd}.log</fileNamePattern> <maxHistory>9</maxHistory> </rollingPolicy> [some other config] </appender> - The log rotation never occured as the application is only short-running and never over midnight. I had missed adding the <cleanHistoryOnStart>true</cleanHistoryOnStart> to the configuration - would probably worth a bit more documentation as this clean flag is described last and therefore could easily be missed on http://logback.qos.ch/manual/appenders.html - Now I already have a lot of logfiles in my directory and the TimeBasedArchiveRemover seems only to remove one file - Is this intended and why? Regards Manuel Oddoy Disclaimer: Bitte beachten Sie: die obige Mitteilung ist ausschließlich für die in den Adresszeilen benannten Personen bestimmt und enthält möglicherweise vertrauliche Informationen. Sollten Sie diese Nachricht fälschlicherweise erhalten haben, informieren Sie bitte den Absender. Bitte löschen Sie die Nachricht und sehen Sie davon ab, die Inhalte zu nutzen, aufzubewahren, weiterzuleiten oder zu reproduzieren. Virenschutz: Unser Unternehmen verfügt über eine funktionierende Anti-Viren- Software und prüft jede abgesendete E-Mail und deren Anhänge auf Viren. Trotzdem können wir nicht garantieren, dass die E-Mail virenfrei ist und übernehmen keine Haftung für Schäden, die aus Viren entstehen. Hinweis zum Datenschutz: Die Informationen nach Art. 13 und 14 DSGVO finden Sie unter "www.kvb.de/datenschutz"

1 0

Logback Joran Custom Conversion Rule
by Jennifer Donahoe 05 Apr '21

05 Apr '21

I'm trying to create a console appender that uses a custom pattern and a custom conversion rule to run the logback logs through the DataConverter class. I can see in the logs that the new conversion rule gets created but the logs get dropped after that point. I assume some setup in the below code is not correct but I'm not sure where I'm going wrong. ConsoleAppender<ILoggingEvent> appender = new ConsoleAppender<>() appender.setName("consoleAppender") RuleStore rs = new SimpleRuleStore(context) Interpreter interpreter = new Interpreter(context, rs, new ElementPath()) InterpretationContext interpretationContext = interpreter.getInterpretationContext() interpretationContext.setContext(context) AttributesImpl attributes = new AttributesImpl() attributes.addAttribute("","","conversionWord", "", "msgMask") attributes.addAttribute("","","converterClass", "", "com.x.logging.library.DataConverter") ConversionRuleAction conversionRule = new ConversionRuleAction() conversionRule.setContext(context) conversionRule.begin(interpretationContext, conversionWord, attributes) PatternLayoutEncoder encoder = new PatternLayoutEncoder() encoder.setContext(context) encoder.setPattern('-%clr(%d{-yyyy-MM-dd HH:mm:ss.SSS}){faint} %clr(-%5p) %clr(-){magenta} %clr(---){faint} %clr([%t]){faint} %clr(%-40.40logger{39}){cyan} %clr(:){faint} %msgMask(%msg) %n') encoder.start() appender.setEncoder(encoder) appender.setContext(context) appender.start() //the appender is later added to the logger I created a question in StackOverflow about this as well: https://stackoverflow.com/q/66768278/7371030?sem=2 Please let me know if you have any examples of this setup or if you can pinpoint where I’m going wrong. Thank you, Jennifer This e-mail and any files transmitted with it are confidential and are solely for the use of the addressee. It may contain material that is legally privileged, proprietary or subject to copyright belonging to the sender and its affiliates, and it may be subject to protection under federal or state law. If you are not the intended recipient, you are notified that any use of this material is strictly prohibited. If you received this transmission in error, please contact the sender immediately by replying to this e-mail and delete the material from your system. The sender may archive e-mails, which may be accessed by authorized persons and may be produced to other parties, including public authorities, in compliance with applicable laws.

1 0

Logback via JNDI in jboss
by xalloc 19 Mar '21

19 Mar '21

Hi all, I have a jboss .war application using SLF4j/Logback that per instructions its logging can be configured setting a JNDI in Jboss. This JNDI should contain a folder path string with java:/comp/env/xyz. I'm using Jboss EAP 7 standalone, but I don't understand where I should put this JNDI and what syntax should be used. The official Logback docs don't help me with Jboss. Thanks

1 0

logback 1.2.3 java11 compatibility
by Baranes, Ofer 11 Mar '21

11 Mar '21

Hi there, When checking compatibility to java11 using jdep, that was the output: jdeps.exe -jdkinternals logback-classic-1.2.3.jar logback-classic-1.2.3.jar -> JDK removed internal API ch.qos.logback.classic.spi.PackagingDataCalculator -> sun.reflect.Reflection JDK internal API (JDK removed internal API) Warning: JDK internal APIs are unsupported and private to JDK implementation that are subject to be removed or changed incompatibly and could break your application. Please modify your code to eliminate dependence on any JDK internal APIs. For the most recent update on JDK internal API replacements, please check: https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool JDK Internal API Suggested Replacement ---------------- --------------------- sun.reflect.Reflection Use java.lang.StackWalker @since 9 Would there be a compatible version to java 11? If so then When? Is there any way to evaluate if this code would not be reachable on specific project? Thanks Ofer "FINASTRA" is the trade name of the FINASTRA group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and FINASTRA. Please refer to the executed contract between you and the relevant member of the FINASTRA group for the identity of the contracting party with which you are dealing.

2 1

Monitor Dropped Events using Spring Actuator
by Cameron Prinsloo 25 Feb '21

25 Feb '21

Hi everyone, I've run into a bit of a problem. We want to monitor the total amount of events that have been *dropped *by Logback using the Spring Boot Actuator. However, it seems that Actuator only allows us to monitor all the events that have been processed by Logback, and not the amount of dropped events. I know that Logback logs warnings regarding dropped events (if the amount matches the droppedWarnFrequency). However I'd prefer to monitor this via Spring Actuator instead of Logback logs. I took a look into the source code where this log is created ( https://github.com/logstash/logstash-logback-encoder/blob/master/src/main/j…, line 464 as of now ), and the amount of dropped events used in the log is stored in a private variable that isn't exposed via some getter. Is this a use case that any of you guys have had? I'd love to hear your thoughts on this :) If this is a relatively common use case (and there is not currently a way to do this), I would suggest exposing "consecutiveDroppedCount" in some way, perhaps by including this total as a value in the WarnStatus class ( https://github.com/qos-ch/logback/blob/61ffd3aba042bbb22f588599ff5574d3b966…) - unless there's a reason that should not be done of course. Please let me know if you need any more info. Thanks a lot --

1 0

a problem about SpringBoot and logback
by 龚宣璋 04 Feb '21

04 Feb '21

Hello, I want't use annotation replace logback-spring-xml What should I do? The question bothers me.🤧

1 0

Logging with custom code to provide the time
by Geng Li 29 Jan '21

29 Jan '21

Hi, I have a program which runs simulations in historic times. I would like the logging line to have the historic time instead of now so it is easier to debug. Is this possible? Is there some hook I can use to inject my custom time into the logging framework? Thanks a lot. Regards Geng

2 1