GitHub user vy added a comment to the discussion: Provide a Layout to StatusLogger
No, it is not possible and, IMHO, this is a good thing. Status Logger is the logger for the logger – that is, we need to keep its feature set at minimum. Consider it like a `printf()` on steroids. > When I get networking problems with my appender, it prints elaborate error > messages with extensive stack traces If this is an unexpected failure, it is good to point to the user the origin by means of a stack trace. If this is something regular, you might consider either introducing a rate limiter to the error messages you emit, or avoiding passing the same exception to the status logger in subsequent calls. GitHub link: https://github.com/apache/logging-log4j2/discussions/3578#discussioncomment-12638574 ---- This is an automatically sent email for dev@logging.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@logging.apache.org
