Mailing-List: contact commits-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Tue, 22 Sep 2015 13:19:05 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: commits@nifi.apache.org
Message-ID: <JIRA.12895440.1442926875000.38549.1442927945479@Atlassian.JIRA>
In-Reply-To: <JIRA.12895440.1442926875000@Atlassian.JIRA>
References: <JIRA.12895440.1442926875000@Atlassian.JIRA>
 <JIRA.12895440.1442926875486@arcas>
Subject: [jira] [Commented] (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.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D149025=
89#comment-14902589 ]=20

ASF GitHub Bot commented on NIFI-985:
-------------------------------------

GitHub user joemeszaros opened a pull request:

    https://github.com/apache/nifi/pull/90

    NIFI-985: Custom log prefix for LogAttribute processor

    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 a=
nd distinguish the output of different LogAttribute processors.
   =20
    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. Log prefix appears in the first and the l=
ast log line, followed by the original 50 dashes. If you configure log pref=
ix '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 :  --------------------------------------------------
   =20
    flow file content...
    ```
    The following screen shot shows the configuration and the output of the=
 processor:
   =20
    ![log_prefix](https://cloud.githubusercontent.com/assets/1064211/100193=
36/09019940-613d-11e5-9ca1-d5c51b6be362.png)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ImpressTV/nifi NIFI-985

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/90.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #90
   =20
----
commit 90741868a8b7d42f5949fd741e2276c024a5866a
Author: Joe <joe.meszaros@impresstv.com>
Date:   2015-09-22T13:04:37Z

    NIFI-985: Custom log prefix for LogAttribute processor
   =20
    Log prefix helps to distinguish the log output of multiple LogAttribute=
 processors and identify the right processor. Log prefix appears in the fir=
st and the last log line, followed by the original 50 dashes. If you config=
ure log prefix 'STEP 1: ' the log output looks like this:
   =20
    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 :  --------------------------------------------------
   =20
    flow file content...

----


> 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: log_prefix.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)