[ https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740983#comment-13740983 ]
Tibor Benke commented on LOG4J2-168: ------------------------------------ I think we should only modify the LoggerFields, RFC5424Layout and SyslogAppender classes (and the TLSRFC5424Layout and TLSSyslogAppender classes after their merge). I'm not sure about one thing: Can we use arrays with @PluginElement? Like this: @PluginElement("LoggerFields") final LoggerFields[] loggerFields And I also suggest that if no name specified in the LoggerFields, we should add its key-value pairs to the default mdc SD-ELEMENT. If nobody has quarrel with it, I'll implement it. > 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 > Fix For: 2.0-beta8 > > Attachments: include-arbitrary-fields-in-mdc-2.patch, > 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