You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Grafana Dashboards and Prometheus AlertManager rules use the kubernetes_pod_name and container_name labels which were deprecated (see kubernetes/kubernetes#80376).
I am currently updating the naming for the strimzi-zookeeper, strimzi-kafka, strimzi-kafka-connect Grafana Dashboards while also migrating the stats panel to Grafana v7's newest version. Let me know if there's interest in a PR.
To Reproduce
Steps to reproduce the behavior:
Create a kind Kubernetes v1.18.2 cluster: kind create cluster
Install the prometheus operator: helm install prometheus stable/prometheus-operator
Note that I have commented out the __meta_kubernetes_endpoints_name re-labeling as it would -for some reason- prevent metrics from being scraped at all.
Open the Prometheus Operator's default Grafana Installation
@chgl thanks for raising this, I was just opening an issue and a PR for this.
Actually, the removed label is pod_name (now it's pod) and not kubernetes_pod_name (this is the result of the relabelling of our Prometheus additional scrape configuration).
It's also related to a wrong metrics path. Now, cadvisor exposes metrics on /metrics/cadvisor.
Anyway, I am going to open the PR with changes on the additional scrape configuration and on all the dashboards using it.
Awesome! What's the motivation behind re-labelling the pod_name/pod to kubernetes_pod_name anyway? - I can see that robustness towards upstream metric changes is one, as you only have to modify the relabelling in one place.
Describe the bug
The Grafana Dashboards and Prometheus AlertManager rules use the
kubernetes_pod_name
andcontainer_name
labels which were deprecated (see kubernetes/kubernetes#80376).I am currently updating the naming for the strimzi-zookeeper, strimzi-kafka, strimzi-kafka-connect Grafana Dashboards while also migrating the stats panel to Grafana v7's newest version. Let me know if there's interest in a PR.
To Reproduce
Steps to reproduce the behavior:
Create a kind Kubernetes v1.18.2 cluster:
kind create cluster
Install the prometheus operator:
helm install prometheus stable/prometheus-operator
Install Strimzi:
helm install strimzi strimzi/strimzi-kafka-operator
Create a Kafka Cluster via kafka.yaml
Create a service monitor via kafka-sm.yaml
Expected behavior
The charts included in the dashboard should display the expected metrics.
Environment (please complete the following information):
YAML files and logs
kafka.yaml
:kafka-sm.yaml
:The text was updated successfully, but these errors were encountered: