[
https://issues.apache.org/jira/browse/LOG4J2-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Kumar updated LOG4J2-2879:
--------------------------------
Summary: Large extendedStackTrace in JsonLayout (I assume XMLLayout and
YamlLayout as well) (was: Large extendedStackTrace in JsonLayout)
> Large extendedStackTrace in JsonLayout (I assume XMLLayout and YamlLayout as
> well)
> ----------------------------------------------------------------------------------
>
> Key: LOG4J2-2879
> URL: https://issues.apache.org/jira/browse/LOG4J2-2879
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.11.2
> Reporter: Ayush Kumar
> Priority: Minor
>
> The extended stack trace value in jsonlayout can be extremely long,
> especially if stackTraceAsString is false (the default). There should be a
> way to cap the size of the extended stack trace. Maybe something that is the
> Pattern equivalent of %ex\{n}? Posted a real example in the comments (we run
> pretty standard spring boot applications). 20k characters is pretty
> excessive, and this interferes with our [scalyr|https://www.scalyr.com/] log
> uploads.
> In fact, is there any way to make it significantly more configurable? Like
> removing the jar from the stacktrace and maybe shortening logger names?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
