You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2026/07/18 16:43:00 UTC

[jira] [Created] (NIFI-16123) Add Connection Status Event Recording to Component Metric Reporter

David Handermann created NIFI-16123:
---------------------------------------

             Summary: 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


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)