[
https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588475#comment-13588475
]
Scott Severtson commented on LOG4J2-168:
----------------------------------------
Two questions:
1. Where do the docs live? More than happy to contribute.
2. Would the following example key/value format be acceptable: "ClassName
%class Sequence %sequenceNumber"? I would have loved to use delimiters for
clarity, but PatternParser lumps anything that's not a converter pattern into a
single literal, and I had concerns about pre-parsing/splitting the
PatternParser string without duplicating a lot of code.
I've added a simple test case locally, and reworked the code to support the
key/value format described above. Let me know if this is acceptable, and I'll
re-generate the patch.
> 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: [email protected]
For additional commands, e-mail: [email protected]
