[jira] [Closed] (LOG4J2-1923) JSONLayout should allow stacktrace as string

["Mikael Ståldal (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikael Ståldal closed LOG4J2-1923.
----------------------------------

> 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
>    Affects Versions: 2.8.2
>            Reporter: Imri Zvik
>            Assignee: Mikael Ståldal
>            Priority: Trivial
>             Fix For: 2.9.0
>
>
> 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.4.14#64029)