[
https://issues.apache.org/jira/browse/NIFI-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906414#comment-14906414
]
ASF subversion and git services commented on NIFI-985:
------------------------------------------------------
Commit e12da7c9a332e6f318ee3eb313b55aa0f4ddf822 in nifi's branch
refs/heads/master from Joe
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e12da7c ]
NIFI-985: Custom log prefix for LogAttribute processor
The LogAttribute processor evaluates the log prefix EL using the current flow
file.
Log prefix helps to distinguish the log output of multiple LogAttribute
processors and identify the right processor. Log prefix appears in the first
and the last log line, followed by the original 50 dashes. If you configure log
prefix 'STEP 1: ' the log output looks like this:
STEP 1 : --------------------------------------------------
Standard FlowFile Attributes
Key: 'entryDate'
Value: 'Tue Sep 22 15:13:02 CEST 2015'
Key: 'lineageStartDate'
Value: 'Tue Sep 22 15:13:02 CEST 2015'
Key: 'fileSize'
Value: '9'
FlowFile Attribute Map Content
Key: 'customAttribute'
Value: 'custom value'
STEP 1 : --------------------------------------------------
flow file content...
Signed-off-by: Aldrin Piri <[email protected]>
> Custom log prefix for LogAttribute processor
> --------------------------------------------
>
> Key: NIFI-985
> URL: https://issues.apache.org/jira/browse/NIFI-985
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Joe Mészáros
> Priority: Minor
> Labels: improvement, log
> Attachments: nifi_log_prefix_updated.png
>
>
> When you have a data flow with a bunch of LogAttribute processors it is
> really hard to identify the right LogAttribute processor in the log file and
> distinguish the output of different LogAttribute processors.
> There is a new property, called log prefix, which helps the user to set a
> custom log prefix for each Log Attribute processor, which will appear in the
> log output of the processor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
