[
https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075985#comment-15075985
]
Robin Coe commented on LOG4J2-908:
----------------------------------
True. A clever parse *should* but Logstash can't. Only way to get Logstash to
recognize log events without commas is to flush each one individually. So, no
batching. I haven't tested whether logstash would process a stream of
EOL-delimited documents, which is something I will investigate and report back
if it can deal. Plugging into a logstash/fluentd environment should be
possible with log4j2 in batch mode, imo.
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
