[
https://issues.apache.org/jira/browse/LOG4J2-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100979#comment-16100979
]
ASF subversion and git services commented on LOG4J2-1986:
---------------------------------------------------------
Commit 32a553e32d39afa2b965d4aa370f2e6e0e7c871a in logging-log4j2's branch
refs/heads/LOG4J2-1986-b from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=32a553e ]
My variaion on [LOG4J2-1986] with cleaner (IMO) exception handling.
> Public API for parsing the output from JsonLayout/XmlLayout/YamlLayout into a
> LogEvent
> --------------------------------------------------------------------------------------
>
> Key: LOG4J2-1986
> URL: https://issues.apache.org/jira/browse/LOG4J2-1986
> Project: Log4j 2
> Issue Type: New Feature
> Components: Layouts
> Affects Versions: 2.8.2
> Reporter: Mikael Ståldal
> Assignee: Mikael Ståldal
>
> Thrid-party tools like [Lilith|http://lilith.huxhorn.de/] need to parse the
> output of JsonLayout into an instance of {{LogEvent}}. Currently there is no
> publicly supported API for doing so.
> Such API could also be used by our SocketServer, and possibly by Chainsaw.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
