[
https://issues.apache.org/jira/browse/NIFI-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347168#comment-17347168
]
ASF subversion and git services commented on NIFI-8126:
-------------------------------------------------------
Commit 2309d75d3d564f51b363820738dd348ec74f31ab in nifi's branch
refs/heads/main from Jon Kessler
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2309d75 ]
NIFI-8126
- Added totalActiveQueuedDuration and maxActiveQueuedDuration to the
ConnectionStatus object
- Updated FlowFileQueue implementations and supporting code to properly
calculate and provide the totalActiveQueuedDuration and maxActiveQueuedDuration
for their active queues
- Fixing failing unit test. In examining this it appears that the unit test
only accidentally passed in the past and that the object mocked to always throw
an exception was not actually being used in the test.
- Adding UI component via ConnectionStatusDescriptor along with updates based
on PR comments.
Signed-off-by: Mark Payne <marka...@hotmail.com>
> 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
> Time Spent: 3h
> Remaining Estimate: 0h
>
> 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)
