[
https://issues.apache.org/jira/browse/LOG4J2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028549#comment-16028549
]
Mikael Ståldal commented on LOG4J2-1923:
----------------------------------------
The documentation has already been updated to reflect current implementation
(not yet released):
https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/manual/layouts.xml.vm
> JSONLayout should allow stacktrace as string
> --------------------------------------------
>
> Key: LOG4J2-1923
> URL: https://issues.apache.org/jira/browse/LOG4J2-1923
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
> Reporter: Imri Zvik
> Priority: Trivial
>
> In previous versions, log4j's JSONLayout used to output stacktraces as
> strings. Some places in the configuration still mention it:
> https://logging.apache.org/log4j/2.x/manual/layouts.html#JSONLayout
> The motivation behind restoring this functionality, is that sometimes the
> logs are used to be viewed by humans, via UIs like Kibana or docker logs with
> jq, and the nested JSON object that log4j2 currently produces is mostly
> unreadable.
> Various workaround exists, like using logstash to flatten this, but IMO
> log4j2 should have a configuration knob to do this out of the box and save
> the unneeded transformation, so the logs could be easily viewed at the source
> (e.g. docker logs command).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
