[
https://issues.apache.org/jira/browse/NIFI-14991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021890#comment-18021890
]
ASF subversion and git services commented on NIFI-14991:
--------------------------------------------------------
Commit 6db99ad7816f170a9282173db31d4d64347dab3f in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6db99ad781 ]
NIFI-14991 Added Process Group Attributes to Component Log
- Added Process Group properties as attributes to Standard Logging Context
- Updated standard Component Log implementation to include Process Group
attributes as MDC attributes
- Added MDC section to Admin Guide
Signed-off-by: Pierre Villard <[email protected]>
This closes #10330.
> Add Process Group Context Attributes to Component Logs
> ------------------------------------------------------
>
> Key: NIFI-14991
> URL: https://issues.apache.org/jira/browse/NIFI-14991
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The standard implementation of the {{ComponentLog}} wraps an SLF4J Logger and
> provides Component Identifier information for each message. The associated
> Logging Context has access to the Grouped Component instance with Process
> Group to support optional logging selection at the Process Group level. For
> structured logging encoders such as JSON, additional context information can
> be provided to logging events using Key Value Pairs or Message Diagnostic
> Context. With the Process Group available in the Logging Context, the
> standard Component Log implementation should be updated to add context
> information associated with the Process Group:
> * Process Group Identifier
> * Process Group Name
> * Process Group Path
> This providing this information makes it available to output encoders,
> without necessarily adding it to the default logging pattern layout. This
> approach should retain existing log message output, but support additional
> options for including this context information in custom pattern layouts or
> encoder configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
