[
https://issues.apache.org/jira/browse/LOG4J2-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419583#comment-15419583
]
Ralph Goers commented on LOG4J2-1512:
-------------------------------------
Log4j 1 and Logback both always swallowed exceptions in Appenders and there was
no way an application could deal with them. The ignoreExceptions attribute was
added to allow the exceptions to percolate back to the application (or to a
wrapping appender such as the failover appender). That is a bit different than
using the attribute to indicate that the Layout shouldn't print an exception.
My only fear here is that users might get confused and think that by putting
ignoreExceptions="true" on an appender that somehow exceptions won't be printed.
> Option to exclude stack trace from some layouts
> -----------------------------------------------
>
> Key: LOG4J2-1512
> URL: https://issues.apache.org/jira/browse/LOG4J2-1512
> Project: Log4j 2
> Issue Type: Improvement
> Components: Layouts
> Affects Versions: 2.6.2
> Reporter: Mikael Ståldal
> Assignee: Mikael Ståldal
> Priority: Minor
> Fix For: 2.7
>
>
> GelfLayout have an option {{includeStacktrace}} to make it possible to
> exclude the stacktrace. This is useful since the stacktrace can be very large.
> This could be useful for other layouts as well: JsonLayout, XmlLayout,
> YamlLayout. Maybe CsvLogEventLayout and HtmlLayout?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
