[jira] [Commented] (LOG4J2-2179) The MongoDB Appender should use keys and values from a Log4j MapMessage

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321617#comment-16321617 ] 

ASF subversion and git services commented on LOG4J2-2179:
---------------------------------------------------------

Commit 5ae7d09cc633ef3397e01ef558e8465ef7e07ba5 in logging-log4j2's branch refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=5ae7d09 ]

[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().
Try to fix Jenkins compile error.

> 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)