[
https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740953#comment-13740953
]
Tibor Benke commented on LOG4J2-168:
------------------------------------
Does the log4j2 support multiple SD-ELEMENTs in an RFC 5424 message? For
example:
<135>1 2013-08-15T11:47:44+02:00 10.30.255.247 APP-NAME PID MSGID [stuff@32473
foo="Foo" bar="Bar"][otherStuff@32473 baz="Baz" qux="Qux"] Some message
I think it'd be nice to write something like this:
<LoggerFields enterpriseId="32473" name="stuff">
<KeyValuePair key="foo" value="Foo"/>
<KeyValuePair key="Bar" value = "Bar"/>
</LoggerFields>
<LoggerFields enterpriseId="32473" name="otherStuff">
<KeyValuePair key="baz" value="Baz"/>
<KeyValuePair key="qux" value="Qux"/>
</LoggerFields>
Then we could structure more the log messages. What are your opinions?
> 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: [email protected]
For additional commands, e-mail: [email protected]
