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
Deployed on rke cluster, the scaphandre pod is deployed using helm as described and the prometheus and grafana pods are deployed using kube-prometheus-stack. All three are deployed in monitoring namespace. When I go to grafana dashboard, I can only see monitoring namespace. Other namespaces are missing.
To Reproduce
Install prometheus and grafana on the cluster: helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack --namespace monitoring
In order for scaphandre to "see" the prometheus, add release: kube-prometheus-stack in helm/scaphandre/templates/servicemonitor.yaml
otherwise, scaph metrics are not visible on grafana
Bug description
Deployed on rke cluster, the scaphandre pod is deployed using helm as described and the prometheus and grafana pods are deployed using kube-prometheus-stack. All three are deployed in monitoring namespace. When I go to grafana dashboard, I can only see monitoring namespace. Other namespaces are missing.
To Reproduce
Install prometheus and grafana on the cluster:
helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack --namespace monitoring
In order for scaphandre to "see" the prometheus, add
release: kube-prometheus-stack
in helm/scaphandre/templates/servicemonitor.yamlotherwise, scaph metrics are not visible on grafana
deploy scaphandre
helm install scaphandre helm/scaphandre --set serviceMonitor.enabled=true --set serviceMonitor.namespace=xyz --set serviceMonitor.interval=30s --namespace monitoring
go to grafana, select
scaph_process_power_consumption_microwatts{namespace="xyz"}
No data
Expected behavior
expected scaph process metrics for pods/containers in the "xyz" namespace
Environment
Linux 5.15.0-119-generic #129~20.04.1-Ubuntu SMP Wed Aug 7 13:07:13 UTC 2024 x86_64 x86_64 x86_64
GNU/Linux
The text was updated successfully, but these errors were encountered: