[
https://issues.apache.org/jira/browse/LOG4J2-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824116#comment-16824116
]
ASF subversion and git services commented on LOG4J2-2337:
---------------------------------------------------------
Commit 303045d1602bd2bd73cf6a1e60026830369389ba in logging-log4j2's branch
refs/heads/release-2.x from Patrice Ferrot
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=303045d ]
[LOG4J2-2337] Allow custom end-of-line with JsonLayout (2.x branch) (#264)
* Allow custom end-of-line with JsonLayout (fix for LOG4J2-2337)
* Added justification for JsonLayout constructor change
> Allow custom end-of-line with JsonLayout
> -----------------------------------------
>
> Key: LOG4J2-2337
> URL: https://issues.apache.org/jira/browse/LOG4J2-2337
> Project: Log4j 2
> Issue Type: Bug
> Environment: Server run on Unix environment.
> Reporter: Arvind Sahare
> Priority: Major
> Attachments: Screen Shot 2018-05-11 at 12.06.51.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Log4j JSONLayout with eventEol="true", prints '\r' at end of log.
> Example:- \{"key":"value", "key":"value"}\r
>
> Problem - Currently we are using Splunk for log analysis, which is not able
> to render Log string as JSON, due to \r getting printed. Can we avoid it
> getting printed?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
