Mailing-List: contact commits-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Tue, 22 Sep 2015 18:55:04 +0000 (UTC)
From: =?utf-8?Q?Joe_M=C3=A9sz=C3=A1ros_=28JIRA=29?= <jira@apache.org>
To: commits@nifi.apache.org
Message-ID: <JIRA.12895440.1442926875000.42098.1442948104640@Atlassian.JIRA>
In-Reply-To: <JIRA.12895440.1442926875000@Atlassian.JIRA>
References: <JIRA.12895440.1442926875000@Atlassian.JIRA>
 <JIRA.12895440.1442926875486@arcas>
Subject: [jira] [Updated] (NIFI-985) Custom log prefix for LogAttribute
 processor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/NIFI-985?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe M=C3=A9sz=C3=A1ros updated NIFI-985:
------------------------------
    Attachment:     (was: log_prefix.png)

> 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=C3=A9sz=C3=A1ros
>            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 r=
eally 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 t=
he log output of the processor.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)