[
https://issues.apache.org/jira/browse/NIFI-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903351#comment-14903351
]
ASF GitHub Bot commented on NIFI-985:
-------------------------------------
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi/pull/90#discussion_r40137422
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/LogAttribute.java
---
@@ -45,6 +45,8 @@
import org.apache.commons.io.IOUtils;
import org.apache.commons.lang3.StringUtils;
+import org.bouncycastle.util.Strings;
--- End diff --
This is unused and is causing errors in the checkstyle. (Checkstyle can be
evaluated via Maven Profile contrib-check, e.g. mvn <goals> -P contrib-check)
> 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)
