[
https://issues.apache.org/jira/browse/NIFI-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Malthe Borch updated NIFI-7837:
-------------------------------
Description:
The LogAttribute processor creates a custom-formatted text message out of the
attribute and optionally content payload.
An optional JSON mode would go some way in making this more accessible to a
consumer, however some logging sinks such as [Azure Application
Insights|https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-trace-logs]
support properties (or _custom dimensions_) that are both more ergonomic and
performant.
SL4J has support [Mapped Diagnostics
Context|http://www.slf4j.org/manual.html#mdc] (MDC) and this is [implemented in
some backends|http://logback.qos.ch/manual/mdc.html] such as Logback.
Finally, some Logback sinks (e.g. the _appender_ for Microsoft Application
Insights) turn that context (a list of key/value entries) into properties.
Supporting MDC as a logging mode in addition to the current custom-formatted
message and possibly a JSON mode as well would go a long way in enabling better
logging from NiFi flows.
was:
The LogAttribute processor creates a custom-formatted text message out of the
attribute and optionally content payload.
An optional JSON mode would go some way in making this more accessible to a
consumer, however some logging sinks such as [Azure Application
Insights|https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-trace-logs]
support properties (or _custom dimensions_) that are both more ergonomic and
performant.
Logback has support for [Mapped Diagnostics
Context|http://logback.qos.ch/manual/mdc.html] (MDC) and again, some logging
sinks turn that context (a list of key/value entries) into properties.
Supporting MDC as a logging mode in addition to the current custom-formatted
message and possibly a JSON mode as well would go a long way in enabling better
logging from NiFi flows.
> Add MDC-mode to LogAttribute
> ----------------------------
>
> Key: NIFI-7837
> URL: https://issues.apache.org/jira/browse/NIFI-7837
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Malthe Borch
> Priority: Minor
>
> The LogAttribute processor creates a custom-formatted text message out of the
> attribute and optionally content payload.
> An optional JSON mode would go some way in making this more accessible to a
> consumer, however some logging sinks such as [Azure Application
> Insights|https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-trace-logs]
> support properties (or _custom dimensions_) that are both more ergonomic and
> performant.
> SL4J has support [Mapped Diagnostics
> Context|http://www.slf4j.org/manual.html#mdc] (MDC) and this is [implemented
> in some backends|http://logback.qos.ch/manual/mdc.html] such as Logback.
> Finally, some Logback sinks (e.g. the _appender_ for Microsoft Application
> Insights) turn that context (a list of key/value entries) into properties.
> Supporting MDC as a logging mode in addition to the current custom-formatted
> message and possibly a JSON mode as well would go a long way in enabling
> better logging from NiFi flows.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
