[
https://issues.apache.org/jira/browse/LOG4J2-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602407#comment-13602407
]
Scott Severtson commented on LOG4J2-168:
----------------------------------------
OK, I'm still just not getting the wiring for this case. I've switched from
"MDCFields" to "LoggerFields", as this really doesn't have anything to do with
MDC. However, I'd appreciate suggestions if there's a better name.
Here's snippits of what I have:
LoggerFields.java:
---
@Plugin(name = "LoggerFields", type = "Core")
public final class LoggerFields {
...
public static Map<String, String> createKeyValuePairsMap(
@PluginElement("LoggerFields")
final KeyValuePair[] keyValuePairs) {
---
SyslogAppender.java
---
@PluginFactory
public static SyslogAppender createAppender(
...
@PluginElement("loggerFields")
Map<String, String> loggerFields) {
---
log4j2.xml:
---
<Syslog
name="syslog"
format="RFC5424"
...
>
<LoggerFields>
<KeyValuePair key="Logger" value="%logger"/>
</LoggerFields>
</Syslog>
---
Console output:
---
ERROR appender Syslog has no parameter that matches element LoggerFields
---
What am I missing? Sorry for all the back-and-forth, but I'm not sure what's
going on. I've also tried <loggerFields> (versus <LoggerFields>) in the config,
but it still complained about the mismatched element name.
> 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
