nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFI-985) Custom log prefix for LogAttribute processor
Date Thu, 24 Sep 2015 14:22:04 GMT


ASF GitHub Bot commented on NIFI-985:

Github user apiri commented on a diff in the pull request:
    --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/
    @@ -123,12 +133,26 @@ protected void init(final ProcessorInitializationContext context)
         protected String processFlowFile(final ProcessorLog logger, final DebugLevels logLevel,
final FlowFile flowFile, final ProcessSession session, final ProcessContext context) {
             final Set<String> attributeKeys = getAttributesToLog(flowFile.getAttributes().keySet(),
             final ProcessorLog LOG = getLogger();
    +        final String dashedLine;
    +        String logPrefix = context.getProperty(LOG_PREFIX).evaluateAttributeExpressions().getValue();
    --- End diff --
    Indeed! :)  Thanks for fixing that up. Everything looks good to go from this side and
I shall merge it in shortly.  Thanks again for your contribution and efforts!

> Custom log prefix for LogAttribute processor
> --------------------------------------------
>                 Key: NIFI-985
>                 URL:
>             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

View raw message