[jira] [Commented] (NIFI-1805) Expose BackPressure status in ConnectionStatus for ReportingTask access

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user jdye64 opened a pull request:

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

    NIFI-1805

    Expose BackPressureObjectThreshold and BackPressureDataSizeThreshold to
    ConnectionStatus

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

    $ git pull https://github.com/jdye64/nifi NIFI-1805

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

    https://github.com/apache/nifi/pull/377.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 #377
    
----
commit 51505bd34f46ea55f0e807ab1d4e764977421aa6
Author: Jeremy Dyer <jd...@gmail.com>
Date:   2016-04-22T17:28:29Z

    NIFI-1805
    
    Expose BackPressureObjectThreshold and BackPressureDataSizeThreshold to
    ConnectionStatus

----


> Expose BackPressure status in ConnectionStatus for ReportingTask access
> -----------------------------------------------------------------------
>
>                 Key: NIFI-1805
>                 URL: https://issues.apache.org/jira/browse/NIFI-1805
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Jeremy Dyer
>            Assignee: Jeremy Dyer
>
> It is currently not possible to determine if a connection within a workflow is experiencing backpressure. While metrics are provided in the ConnectionStatus object around objectsQueued and bytesQueued this alone isn't enough to determine if any user defined backpressure is being applied. The idea is to make that information about the backpressure available inside the existing ConnectionStatus so that custom ReportingTasks can look for things like slow connections and alert appropriately. 
> Mark Payne nifi dev list email excerpt - "It should be relatively easy. In FlowController, we would have to update getGroupStatus() to set the values on ConnectionStatus
> and of course update ConnectionStatus to have getters & setters for the new values. That should be about it, I think."



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