[
https://issues.apache.org/jira/browse/NIFI-16375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18118283#comment-18118283
]
ASF subversion and git services commented on NIFI-16375:
--------------------------------------------------------
Commit 856e5fd0a9da89d3efdc2d2cab447c7d9d23df5c in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=856e5fd0a9d ]
NIFI-16375 Add Lag and Record Metrics to ConsumeKafka (#11702)
> Add Lag and Records Metrics to ConsumeKafka
> -------------------------------------------
>
> Key: NIFI-16375
> URL: https://issues.apache.org/jira/browse/NIFI-16375
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The {{ConsumeKafka}} Processor should be updated to record the following lag
> and record metrics for each invocation, supporting topic and partition-level
> tracking using the recently-attributes Map of attributes for Counters and
> Gauges.
> * kafka.bytes.consumed
> ** Type: Counter
> * kafka.records.consumed
> ** Type: Counter
> * kafka.records.consumer.lag
> ** Type: Gauge
> * kafka.records.parsed.errors
> ** Type: Counter
> Although the Kafka MetricsReporter provides some capabilities, it does not
> support all of these types of instrumentation details, so implementing the
> Counters and Gauges using ProcessSession methods appears to be the best
> approach.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
