[
https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416721#comment-15416721
]
Dave Howes commented on LOG4J2-667:
-----------------------------------
Thinking about this a little further, if you're working in a multi-language
micro-services world where you want to enforce standardised logging across all
services, the ability to configure what data is logged, and how it is named
becomes more important.
It could be argued that it's the job of a log aggregator to wrangle all the
logging data in to the standardised form, but in smaller shops it's conceivable
that this aggregation might be done manually, and it'd be much easier to get
the individual micro-services to just conform to a defined message format.
> Add customization for JSON Layout keys and values
> -------------------------------------------------
>
> Key: LOG4J2-667
> URL: https://issues.apache.org/jira/browse/LOG4J2-667
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Danny Sullivan
> Labels: JSON
>
> I really like the JSON Layout feature as it's easily parsed by splunk. I
> would like to see more customization on the type of information that's
> included in each json message, similar to the Pattern Layout such as MDC and
> NDC, the locations etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
