Replies: 3 comments 11 replies
-
It seems you are mixing completely different things:
The blog post you linked to is from 2019, so I'm not sure it it is still valid. But it focuses only on Kafka Exporter metrics. Is that what does not work for you? Or is the Kafka metrics? How does your full configuration look like? What or where are the |
Beta Was this translation helpful? Give feedback.
-
@avdev4j Were you able to progress on this? I am stuck on this as well. |
Beta Was this translation helpful? Give feedback.
-
hi @orbi-ci-bot I can see some "kafka_server_" metrics in prometheus, but it seems not to be the whole metrics we are supposed to have. I suspect the configuration not to be well read by the JMX Prometheus exporter. I mean the one that is created in the configmap loaded in the Kafka FS from the yaml version pushed from my git repo. I'll try to give another try then, and I'll be happy to share progresses here. |
Beta Was this translation helpful? Give feedback.
-
Bug Description
In a Strimzi 0.41.0 installation, it is not possible to display Kafka and Zookeeper JMX metrics when following this blog post: https://strimzi.io/blog/2019/10/14/improving-prometheus-metrics/.
The Grafana dashboard remains empty, even though Prometheus is scraping the metrics using a PodMonitor.
I tried multiple times to ensure that I was using the same version as in the GitHub examples and my installed version, but it always ended the same way: it was impossible to get these metrics.
Steps to reproduce
Enable the metrics in the resource:
Add the configmaps:
Add a podMonitor in the Prometheus (considering it does exist and works)
Ensure that Prometheus scrapping is working as expected (I have enabled Kafka Exporter in my cluster that's why I have 3 targets here).
In grafana, add the provided dashboard in the examples:
Expected behavior
The Dashboards should display the metrics captured by Prometheus.
Strimzi version
0.41.0
Kubernetes version
1.30.2
Installation method
Helm
Infrastructure
Managed OVH Kubernetes
Configuration files and logs
Here is the metrics-config.json from the Kafka configmap (btw, I can see a lot of empty value here such as clientId, topic, partition..., and I'm wondering if it could be the reason of the issue):
Here is a sample of metrics provided by kafka JMX exporter
And the Zookeeper metrics.
Additional context
Thanks for your time to check if it is a bug.
Feel free to ask for more details.
Beta Was this translation helpful? Give feedback.
All reactions