rschmitt commented on PR #3880: URL: https://github.com/apache/logging-log4j2/pull/3880#issuecomment-3198375174
> With your change, when the queue is full, the status logger will emit a warning, but since its default level is `ERROR`, that warning won’t be shown. Does the status logger go through all the same async appender machinery? I thought it was just a simple console logger used by `log4j-api`. > I also find the semantics of `log4j2.discardThreshold` a bit unintuitive. Naively, I’d expect it to mean “log events at this level or higher will be retained.” Yeah, because that's how all other logging configuration works. I was also confused by this and had to carefully read source code to make sure I wasn't crazy. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
