vy commented on issue #3873: URL: https://github.com/apache/logging-log4j2/issues/3873#issuecomment-3170418199
@rschmitt, thanks so much for reaching out to us. I'm sorry to hear that your log scans are affected. As you indicated, #3045 changed all exception messages to get prefixed with a newline. This work was a follow-up of #2691 – see [this conversation](https://github.com/apache/logging-log4j2/pull/2691#pullrequestreview-2336863782). Both changes were delivered in `2.25.0`. > Since this layout change affects log scans, I'd like it if there were a way to specify a pattern that reproduces the pre-2.25 layout for anyone who depends on it. There are no configuration knobs to switch to pre-`2.25.0` behavior. You can create a custom layout extending from `ThrowablePatternConverter`, but I guess you already know that. As it is explicitly stated in the very first paragraph of [the Pattern Layout manual](https://logging.apache.org/log4j/2.x/manual/pattern-layout.html) > **Pattern Layout is not intended for _structural logging_ purposes.** For production environments, you are strongly advised to use [JSON Template Layout](https://logging.apache.org/log4j/2.x/manual/json-template-layout.html) producing JSON output ready to be delivered to log ingestion systems ... I understand, given this feature has been there for decades without a good offer for structured logging (i.e., JSON Template Layout is decades younger than Pattern Layout), there are tooling in the wild depending on this behavior. During `2.25.0`, we had internal consensus among active maintainers to settle on the current behavior. Unless there is a pressing need to do otherwise, I don't see the current layout changing. -- 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
