[
https://issues.apache.org/jira/browse/LOG4J2-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Kumar updated LOG4J2-2879:
--------------------------------
Description:
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. 20k characters is
pretty excessive.
In fact, is there any way to make it significantly more configurable? Like
removing the jar from the stacktrace and maybe shortening logger names?
was:
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}?
In fact, is there any way to make it significantly more configurable? Like
removing the jar from the stacktrace and maybe shortening logger names?
> Large extendedStackTrace in JsonLayout
> --------------------------------------
>
> 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. 20k
> characters is pretty excessive.
> 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)
