[
https://issues.apache.org/jira/browse/LOG4J2-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486014#comment-17486014
]
Michael Kendle commented on LOG4J2-3082:
----------------------------------------
[~vy] Thanks, I'll take a look and discuss with my team whether we'd like to
add a custom resolver like that or not. I will say, it does seem like a fair
bit of code to add to all of our projects when it works "out of the box" for
JsonLayout. So we'd much prefer both layouts behave the same way in this regard.
> Support external serializers (e.g., Jackson) JsonTemplateLayout
> ---------------------------------------------------------------
>
> Key: LOG4J2-3082
> URL: https://issues.apache.org/jira/browse/LOG4J2-3082
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
> Affects Versions: 2.14.1
> Reporter: Schubert Fernandes
> Assignee: Volkan Yazici
> Priority: Minor
> Attachments: log4j.json.event.layout.zip
>
>
> When using JsonTemplateLayout is there a way to output composite objects as
> JSON?
> It looks like any composite objects are output as simple strings with the
> value generated by the .toString() method of the Java object.
> Is there an option to output JSON instead, possibly using
> _org.apache.logging.log4j.core.jackson.Log4jJsonObjectMapper_ ?
> It is currently possible to do this by converting the object into a
> java.util.Map before supplying it to the logging framework but it would be
> nice if the logging framework did this out of the box if an option is turned
> on as it is not always possible to do this (e.g. with objects on the MDC/NDC).
> This should apply to composite objects logged from...
> # The thread context map (MDC).
> # The thread context stack (NDC).
> # Message parameters
> # anywhere else that I may have missed.
> See the differences between the two log messages generated in the attached
> project.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
