fabian-braun commented on issue #3792: URL: https://github.com/apache/logging-log4j2/issues/3792#issuecomment-3027276204
Since we re-deployed the app with `LOG4J_INSTANT_FORMATTER=legacy` the problem is gone. In the last 24 hours since the deployment all logs could be parsed. So, I'm quite convinced now that the problem is indeed related to the latest Log4J release -- 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
