[ 
https://issues.apache.org/jira/browse/NIFI-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903348#comment-14903348
 ] 

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_r40137272
  
    --- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/LogAttribute.java
 ---
    @@ -79,6 +81,14 @@
                 .allowableValues("true", "false")
                 .build();
     
    +    public static final PropertyDescriptor LOG_PREFIX = new 
PropertyDescriptor.Builder()
    +            .name("Log prefix")
    +            .required(false)
    +            .description("Log prefix appended to the log lines. It helps 
to distinguish the output of multiple LogAttribute processors.")
    +            .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
    +            .expressionLanguageSupported(true)
    --- End diff --
    
    This is good to note that the property supports EL (this is the indicator 
via the UI)


> 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)

Reply via email to