[
https://issues.apache.org/jira/browse/LOG4J2-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-2525.
-----------------------------------
Resolution: Won't Fix
> Add max message size limit to JSON Layout
> -----------------------------------------
>
> Key: LOG4J2-2525
> URL: https://issues.apache.org/jira/browse/LOG4J2-2525
> Project: Log4j 2
> Issue Type: New Feature
> Components: Layouts
> Affects Versions: 2.11.1
> Reporter: Fabian Braun
> Priority: Minor
>
> In edge-cases the json representation of stack-traces can become too large
> for log-consuming systems (>16KB in the specific case).
> Therefore I'd like to propose introducing a new configuration parameter
> {{limitMessageSize}} to keep the log record within certain size boundaries
> under all circumstances. Similar to the {{maxLength}} option available in the
> PatternLayout.
>
> For more context, see this question on stackoverflow:
>
> [https://stackoverflow.com/questions/53335345/limit-log-event-length-in-log4j2-json-layout-to-prevent-hitting-docker-log-drive]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
