[
https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585321#comment-13585321
]
Ralph Goers commented on LOG4J2-168:
------------------------------------
While I support the concept of what this patch is trying to do I have some
issues with the actual patch:
1. There aren't any tests for it.
2. There isn't any doc for it.
3. The way the patch works is to use the converter name as the key in the map.
This doesn't work well in a lot of cases. For example, specifying %X{key1}
%X{key2} would not be nice (and, of course, would also be stupid to specify).
I'm wondering if it wouldn't be nicer to specify KeyValuePairs under an MDC or
ThreadContext element instead. Then the user could specify the name of the key
and the value would be a pattern or expression.
> Include arbitrary message fields in RFC-5424 structured data
> ------------------------------------------------------------
>
> Key: LOG4J2-168
> URL: https://issues.apache.org/jira/browse/LOG4J2-168
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.0-beta5
> Environment: N/A
> Reporter: Scott Severtson
> Priority: Minor
> Attachments: include-arbitrary-fields-in-mdc.patch
>
>
> We'd really like to see the logger and/or location be included in RFC-5424
> structured data. As such, we've developed a small patch to allow arbitrary
> PatternLayout names to be configured on the SyslogAppender, which are then
> included in the structured data.
> Patch to follow shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
