You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/03/09 17:29:00 UTC

[jira] [Resolved] (NIFI-15687) Revert Current Lag Reporting in ConsumeKafka

     [ https://issues.apache.org/jira/browse/NIFI-15687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-15687.
-----------------------------------
    Fix Version/s: 2.9.0
       Resolution: Fixed

> Revert Current Lag Reporting in ConsumeKafka
> --------------------------------------------
>
>                 Key: NIFI-15687
>                 URL: https://issues.apache.org/jira/browse/NIFI-15687
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 2.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Recent updates to the ConsumeKafka Processor, not yet released, added reporting of current lag using the record gauge method. This approach to metrics tracking for Kafka processing provides some value, but does not cover the extent of available Kafka client metrics. Kafka Client version 3.7.0 introduced the ClientTelemetryReceiver interface as an extension point for exporting metrics and the Kafka MetricsReporter interface provides low-level access to metrics. These interfaces should be evaluated to determine the best strategy for integrated metrics collection and the initial approach in ConsumeKafka should be reverted.



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