[
https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074340#comment-15074340
]
Robin Coe commented on LOG4J2-908:
----------------------------------
Could commas not be appended to each log event and then use the existing footer
implementation to add an empty event and, if set, closing document square
bracket, i.e., {}<]>? It's a bit hacky, insofar as it introduces noise into
the log, but *should* not affect the behaviour of applications that process a
json stream.
Alternatively, would it be incorrect to interpret each log event as a complete
document, in the case of setting complete="true"? Is there any reason the
entire log needs to be wrapped in [ ... ]? What's the semantic difference
between a single event enclosed in square brackets, separated by commas, and a
non-comma separated set of events that are each marked as documents with EOL
delimiters?
> 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
>
> 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]
