[
https://issues.apache.org/jira/browse/NIFI-16072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-16072:
----------------------------------
Fix Version/s: 2.11.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add FlowFile Event Handling to Component Metric Reporter
> --------------------------------------------------------
>
> Key: NIFI-16072
> URL: https://issues.apache.org/jira/browse/NIFI-16072
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The {{ComponentMetricReporter}} supports extensible integration at the
> framework level for reporting Counters and Gauges.
> Following the initial implementation added to as part of work to support
> Gauges as Processor Metrics, the {{ComponentMetricReporter}} should be
> extended to support optional handling of FlowFile Events, produced in
> {{ProcessSession}} implementations. This addition should be backward
> compatible with existing implementations of {{ComponentMetricReporter}},
> having no impact on behavior when the handling method is not implemented.
> In the current framework design, the {{FlowFileEventRepository}} is not part
> of the {{nifi-framework-api}} and is not open for extension at the framework
> level. The corresponding {{FlowFileEvent}} interface provides the contract,
> indicating counts and bytes processed, among other metrics. The
> {{FlowFileEvent}} interface should be renamed to align with the source and
> character of the events themselves, such as {{ProcessSessionEvent}}. This
> interface should be promoted to {{nifi-framework-api}} as part of
> implementing handling support in {{ComponentMetricReporter}}. With this
> refactoring, the {{ComponentMetricReporter}} will be capable of processing a
> wider set of available framework metrics. This approach promotes exporting
> selected metrics from the framework, as opposed to providing an alternative
> persistence strategy, already available through the
> {{StatusHistoryRepository}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
