You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Prashanth Joseph Babu (Jira)" <ji...@apache.org> on 2022/05/25 08:28:00 UTC

[jira] [Updated] (KAFKA-13936) Invalid consumer lag when monitoring from a kafka streams application

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

Prashanth Joseph Babu updated KAFKA-13936:
------------------------------------------
    Description: 
I have a kafka streams application and I'm trying to monitor the consumer lag via stream metrics.

Here's some code snippet

```
metrics = streams.metrics(); lag = 0; for (Metric m : metrics.values()) { tags = m.metricName().tags(); if ( m.metricName().name().equals(MONITOR_CONSUMER_LAG) && tags.containsKey(MONTOR_TAG_TOPIC) && tags.get(MONTOR_TAG_TOPIC).equals(inputTopic) ) { partitionLag = Float.valueOf(m.metricValue().toString()).floatValue(); if ( !partitionLag.isNaN() )

{ lag += partitionLag; }

} }



```

Here MONITOR_CONSUMER_LAG is {{{}records-lag-max{}}}.

However these numbers dont match with the consumer lag we see in the kafka UI . is records-lag-max the right metric to track for a kafka streams application when the objective is to get consumer lag?

  was:
I have a kafka streams application and I'm trying to monitor the consumer lag via stream metrics.

Here's some code snippet

```
 metrics = streams.metrics();            lag = 0;            for (Metric m : metrics.values()) {                tags = m.metricName().tags();                if ( m.metricName().name().equals(MONITOR_CONSUMER_LAG) && tags.containsKey(MONTOR_TAG_TOPIC) &&                     tags.get(MONTOR_TAG_TOPIC).equals(inputTopic) ) {                    partitionLag = Float.valueOf(m.metricValue().toString()).floatValue();                    if ( !partitionLag.isNaN() ) {                        lag += partitionLag;                    }                }            }
```

Here MONITOR_CONSUMER_LAG is {{{}records-lag-max{}}}.

However these numbers dont match with the consumer lag we see in the kafka UI . is records-lag-max the right metric to track for a kafka streams application when the objective is to get consumer lag?


> Invalid consumer lag when monitoring from a kafka streams application
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-13936
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13936
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Prashanth Joseph Babu
>            Priority: Major
>
> I have a kafka streams application and I'm trying to monitor the consumer lag via stream metrics.
> Here's some code snippet
> ```
> metrics = streams.metrics(); lag = 0; for (Metric m : metrics.values()) { tags = m.metricName().tags(); if ( m.metricName().name().equals(MONITOR_CONSUMER_LAG) && tags.containsKey(MONTOR_TAG_TOPIC) && tags.get(MONTOR_TAG_TOPIC).equals(inputTopic) ) { partitionLag = Float.valueOf(m.metricValue().toString()).floatValue(); if ( !partitionLag.isNaN() )
> { lag += partitionLag; }
> } }
> ```
> Here MONITOR_CONSUMER_LAG is {{{}records-lag-max{}}}.
> However these numbers dont match with the consumer lag we see in the kafka UI . is records-lag-max the right metric to track for a kafka streams application when the objective is to get consumer lag?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)