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

ASF subversion and git services commented on NIFI-16123:
--------------------------------------------------------

Commit 8372ecbe0968892fe0317ccebc351c1ea1c55acc in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8372ecbe096 ]

NIFI-16123 Added Connection Status reporting to Process Session (#11441)

- Added ConnectionStatusEvent interface to framework-api
- Updated StandardProcessSession with optional recording of Connection Status

> Add Connection Status Event Recording to Component Metric Reporter
> ------------------------------------------------------------------
>
>                 Key: NIFI-16123
>                 URL: https://issues.apache.org/jira/browse/NIFI-16123
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The {{ComponentMetricReporter}} framework extension interface should be 
> updated to support processing Connection Status Events, produced after 
> committing transactions in the {{StandardProcessSession}} class. Similar to 
> {{ProcessSessionEvents}}, a new Connection Status Event should include the 
> count and size of FlowFiles queued for Connections handled during 
> {{ProcessSession}} operations. The purpose of recording Connection Status 
> Events is to provide direct support for exporting the current status of 
> processed Connections, as opposed to the periodic tracking implemented for 
> the {{StatusHistoryRepository}}.
> Recording Connection Status Events should be an optional feature of the 
> {{ComponentMetricReporter}} with a default interface method that does not 
> perform an operations. With Connection Status Events requiring object 
> creation, the {{ComponentMetricReporter}} should also include a method that 
> provides enabled status for recording Connection Status, allowing the calling 
> {{StandardProcessSession}} to avoid unnecessary operations when recording is 
> disabled.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to