vy commented on issue #3435: URL: https://github.com/apache/logging-log4j2/issues/3435#issuecomment-2639652617
> When a log string contains `key=value` format, in modern log search tool, like [Splunk](https://www.splunk.com/) or [ELK](https://www.elastic.co/): @amosshi, it sounds counter intuitive to me to serialize the entire log event into one big string instead of using individual fields wherever necessary. As a matter of fact, both ELK (via its [Elastic Common Schema](https://www.elastic.co/guide/en/ecs/current/ecs-reference.html)) and Splunk (in its [logging best-practices page](https://dev.splunk.com/enterprise/docs/developapps/addsupport/logging/loggingbestpractices/#Use-developer-friendly-formats)) recommend using [structured logging](https://logging.apache.org/log4j/2.x/manual/layouts.html#structured-logging), which is best delivered by [JSON Template Layout](https://logging.apache.org/log4j/2.x/manual/json-template-layout.html). Would you mind helping us to understand your motivation from deviating these standards? Could using a structured layout instead of Pattern Layout be an option for you? -- 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
