[
https://issues.apache.org/jira/browse/NIFI-15687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18064204#comment-18064204
]
ASF subversion and git services commented on NIFI-15687:
--------------------------------------------------------
Commit 6be2570b2ebeec60a946e50343d6de779f8576db in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6be2570b2eb ]
NIFI-15687 Reverted Current Lag gauge recording in ConsumeKafka (#10984)
This reverts commit b43be1d0e462ead0c593d65c1a15107fb70e3ae0
> 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
> 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)
