[
https://issues.apache.org/jira/browse/LOG4J2-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076244#comment-15076244
]
Robin Coe commented on LOG4J2-908:
----------------------------------
No but I did briefly look at it. I actually dropped logstash from my pipe,
because I wasn't confident in it's performance or behaviour. Beyond its
runtime being Jruby, I didn't like that logstash uses a blocking IO pipe and
silently drops events when its buffer is full. A key reason I am using log4j2
is its failover mechanism and I don't trust logstash to upstream the events it
receives, which negates the failover of log4j2. Instad, I am using the
log4j2-elasticsearch plugin, https://github.com/jprante/log4j2-elasticsearch,
to go directly to elasticsearch. What that leaves me, though, is to build my
own parser for json events in the failover log, so I can recover them and send
them upstream on service recovery. For this, i am using jackson, which is what
log4j2 uses to create the json layout. Now is the time I wish log4j2 had a
slightly more public API, to reverse the process, something akin to chainsaw.
Long story, I know, but thought it may help understand my persistence to
understand semantics from a parser's POV. =)
> 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]
