You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "endzeit (Jira)" <ji...@apache.org> on 2021/01/09 09:13:00 UTC

[jira] [Commented] (NIFI-8126) Include Total Queued Duration in metrics reported via ConnectionStatus

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

endzeit commented on NIFI-8126:
-------------------------------

I would also advocate for a the maximum queued duration, to watch for files residing in the flow for very long times. 

 

Maybe this metric should be based on the lineage duration instead of the queued duration. Also this might be useful to see for the whole flow and not just a single queue. Thinking about it,aybe this should be filed in a separate JIRA issue instead?

> Include Total Queued Duration in metrics reported via ConnectionStatus
> ----------------------------------------------------------------------
>
>                 Key: NIFI-8126
>                 URL: https://issues.apache.org/jira/browse/NIFI-8126
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.12.1
>            Reporter: Jon Kessler
>            Assignee: Jon Kessler
>            Priority: Minor
>              Labels: Metrics, reporting_task
>
> On the graph, when listing a queue, you are able to see the queued duration for individual flowfiles. I believe that either a total queued duration or an average queued duration for the connection as a whole would be a valuable metric to include in the ConnectionStatus object that is available to ReportingTasks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)