Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kafka_consumergroup_current_offset and kafka_consumergroup_lag cannot be seen #407

Open
Alexios-cd opened this issue Sep 7, 2023 · 2 comments

Comments

@Alexios-cd
Copy link

About Version

kafka_exporter 1.7.0 / 2023-05-24
kafka_version 2.2.1

About Start Shell

./kafka_exporter \
--kafka.version=2.2.1 \
--web.listen-address=:19308 \
--kafka.server=bigdata01:9092 \
--kafka.server=bigdata02:9092 \
--kafka.server=bigdata03:9092

ALL Log

I0907 10:51:14.995928   14923 kafka_exporter.go:800] Starting kafka_exporter (version=1.7.0, branch=HEAD, revision=7e840e81a0170375214e2c1e1dc7ce94aeff8712)
I0907 10:51:15.000278   14923 kafka_exporter.go:971] Listening on HTTP :19308

image

The offset value of kafka used should be stored in __consumer_offsets, independent of zookeeper,

Any suggestions?

@Mallikarjunradware
Copy link

Same issue here, I am also unable to get any metrics of consumergroup. It was working fine till 13th Sep, suddenly it is stopped working.

  • Kafka exporter version: 1.6.0 (tried 1.7.0 also)
  • kafka version: 1.1.1

So far I have take below actions:

  • Added args "--group.filter='.+' " (without this getting error "was collected before with the same name and label values")
  • Did preferred replica election
  • Re partition of consumer_offset topic

Please help if anyone has come across the same issue and able to overcome.

@glerma
Copy link

glerma commented Oct 20, 2024

@danielqsj - And I cannot get any consumergroup metrics from my kafka cluster, using this exporter. Anectdotally ,this seems to be an overall problem, even with latest: v1.8.0. I've found numerous reports of this. Can someone give some insight into possible causes or perhaps look into this as a possible bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants