[
https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276180#comment-16276180
]
Daniel Kirkdorffer edited comment on LOG4J2-667 at 12/4/17 12:47 AM:
---------------------------------------------------------------------
[[email protected]] made a comment that is similar to our need/issue
(LOG4J2-2139), in that where various microservices are being aggregated in a
single form for use with Kibana. locationInfo emits a "source" key that
conflicts with application logging that attributes "source" to an originating
system, not a line of source code. Therefore we would like to rename the
"source" key from locationInfo. Am I to assume from this thread that this is
not a feature request that the maintainers would consider?
was (Author: dankirkd):
[[email protected]] made a comment that is similar to our need/issue, in
that where various microservices are being aggregated in a single form for use
with Kibana. locationInfo emits a "source" key that conflicts with application
logging that attributes "source" to an originating system, not a line of source
code. Therefore we would like to rename the "source" key from locationInfo.
Am I to assume from this thread that this is not a feature request that the
maintainers would consider?
> 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.4.14#64029)
