Metric not present in prometheus #4455
-
Hi guys, I have deployed the chart example here (strimzi-kafka.json) to grafana, querying our prometheus. I couldn't see a few metrics used in the chart above, one example is the kafka_controller_kafkacontroller_offlinepartitionscount metric. Digging a bit into it, I found a metric called kafka_controller_kafkacontroller_value, that has a label name, with one the values being OfflinePartitionsCount. We do have a different JMX pattern then the one used in the example kafka-metrics.yaml, but i could not see any pattern rule that could generate the kafka_controller_kafkacontroller_offlinepartitionscount metric, only a few patterns with count, but putting a "*_count" at the end of the metric name, and the metric above has no "_" before the count. Another example of metrics i could not find is the kafka_server_replicamanager_leadercount, used in some charts and filters in the same chart, and at the same time i can find another metric called "_value", like kafka_server_replicafetchermanager_value, but at this time i could not find any metric with a label name with "LeaderCount" not nothing. So my questions are:
Cheers, Fernando |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
The Dashboard is written to work with the metrics example (you should always take both from the same Strimzi version - preferably from the version you use). So if you configure the Prometheus export as in our examples, all metrics the dashboard is using should be exposed. If you have your own configuration of the JMX Exporter, it is possible that some of the metrics will not work because of different labels, names etc. I think it is also possible that some metrics which do not have a value do not exist => for example when there are no topics, no clients etc. But TBH I'm not 100% about it ... I would need to try it with the example YAMLs to know for sure. |
Beta Was this translation helpful? Give feedback.
The Dashboard is written to work with the metrics example (you should always take both from the same Strimzi version - preferably from the version you use). So if you configure the Prometheus export as in our examples, all metrics the dashboard is using should be exposed. If you have your own configuration of the JMX Exporter, it is possible that some of the metrics will not work because of different labels, names etc.
I think it is also possible that some metrics which do not have a value do not exist => for example when there are no topics, no clients etc. But TBH I'm not 100% about it ... I would need to try it with the example YAMLs to know for sure.