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

David Handermann updated NIFI-15644:
------------------------------------
    Affects Version/s:     (was: 2.8.0)

> 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)

Reply via email to