[
https://issues.apache.org/jira/browse/LOG4J2-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321667#comment-16321667
]
ASF subversion and git services commented on LOG4J2-2179:
---------------------------------------------------------
Commit 59c465dc2a14bf607c65db22f70f5aa0552e0658 in logging-log4j2's branch
refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=59c465d ]
[LOG4J2-2179] The MongoDB Appender should use a keys and values for a
Log4j MapMessage.
[LOG4J2-2180] Add a MongoDbProvider builder for and deprecate
org.apache.logging.log4j.mongodb.MongoDbProvider.createNoSqlProvider().
Oops, missed this one. Fix up mocks.
> The MongoDB Appender should use keys and values from a Log4j MapMessage
> -----------------------------------------------------------------------
>
> Key: LOG4J2-2179
> URL: https://issues.apache.org/jira/browse/LOG4J2-2179
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.10.1
>
>
> The MongoDB Appender should use a keys and values for a Log4j MapMessage.
> When a {{MapMessage}} is passed to a logger API and that {{Message}} makes it
> all the way to the MongoDB provider of a NoSQL {{Appender}}, then the
> resulting object sent to MongoDB will have the {{MapMessage}} keys and values
> instead of the fields of the {{LogEvent}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
