[ 
https://issues.apache.org/jira/browse/LOG4J2-2750?focusedWorklogId=848086&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848086
 ]

ASF GitHub Bot logged work on LOG4J2-2750:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Feb/23 15:02
            Start Date: 28/Feb/23 15:02
    Worklog Time Spent: 10m 
      Work Description: vy closed pull request #326: LOG4J2-2750: Extended 
throwable class loading can be disabled
URL: https://github.com/apache/logging-log4j2/pull/326




Issue Time Tracking
-------------------

    Worklog Id:     (was: 848086)
    Time Spent: 40m  (was: 0.5h)

> Setting to disable extended stack trace for layouts
> ---------------------------------------------------
>
>                 Key: LOG4J2-2750
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2750
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Layouts
>            Reporter: Mikhail Talisov
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> By default almost all layouts use an extended stack trace output format 
> (ExtendedStackTraceElement). Currently I can change the stack trace format in 
> PatternLayout by specifiyng its template (%throwable, %xThrowable, etc). When 
> specified %throwable then no class packaging information is included in 
> output.
> But when I use for example JsonLayout or AsyncAppender with any layout then 
> no way to exclude class packaging information from the stack trace (this mean 
> class loading from classpath for all stack trace elements). For performance 
> reason would be good to have a setting to disable extending the stack trace 
> in layouts.
> It's possible to add new attribute "extendedStackTrace" (for example, which 
> is true by default) in layout elements (except PatternLayout and some other 
> layouts where no ThrowableProxyHelper#toExtendedStackTrace is using). When I 
> set extendedStackTrace="false" then stack trace must be serialized without 
> class loading for all stack trace elements. AsyncAppender must use refs 
> appender layout's attribute.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to