[
https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076095#comment-15076095
]
Robin Coe commented on LOG4J2-908:
----------------------------------
I disagree with creating a new layout just for logstash. Any parser willing to
accept json should likewise conform to the spec, which this fix does for
log4j2. From limited experience I am confident that this fix will now allow
batching events from log4j2 to elasticsearch.
I side-railed this issue by introducing the question of whether there's any
difference between a single array with multiple elements and multiple arrays
with a single element, in the context of an external parser. Having not yet
tested whether logstash and/or fluentd can process a stream of json arrays,
with/without comma and/or EOL delimeters, then suggesting a different format is
premature.
> JSONLayout doesn't add a comma between log events
> -------------------------------------------------
>
> Key: LOG4J2-908
> URL: https://issues.apache.org/jira/browse/LOG4J2-908
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.1
> Reporter: Konstantinos Liakos
> Assignee: Gary Gregory
> Fix For: 2.5.1
>
>
> JSONLayout doesn't output a comma (,) between the log events. This makes it
> quite difficult to read and deserialize the log files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
