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/02/25 18:22:00 UTC

[jira] [Resolved] (NIFI-15644) Record Kafka consumer lag as gauge metric in ConsumeKafka processor

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

David Handermann resolved NIFI-15644.
-------------------------------------
    Resolution: Duplicate

Closing as duplicate of NIFI-15563.

> Record Kafka consumer lag as gauge metric in ConsumeKafka processor
> -------------------------------------------------------------------
>
>                 Key: NIFI-15644
>                 URL: https://issues.apache.org/jira/browse/NIFI-15644
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Dariusz Seweryn
>            Assignee: Dariusz Seweryn
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> As of [NIFI-15545|https://issues.apache.org/jira/browse/NIFI-15545], the KafkaConsumerService exposes a currentLag(TopicPartitionSummary) method that returns the current consumer lag (in records) for a given topic-partition. However, this information is not currently utilized by the ConsumeKafka processor.
> This ticket adds gauge metric recording to ConsumeKafka so that per-partition consumer lag is reported through the NiFi metrics framework via ProcessSession.recordGauge(). This enables operators to monitor consumer lag through any configured ComponentMetricReporter (e.g., OpenTelemetry).



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