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 a clear and concise description of what the bug is.
Apologies if this is something stupid or obvious. I'm deploying the prometheus kube stack alongside our company's application on a local rancher desktop installation, on Ubuntu LTS 22.
I did not override any values. My assumption is that I would get standard metrics like pod CPU and memory consumption without manual adjustments.
Describe the bug a clear and concise description of what the bug is.
Apologies if this is something stupid or obvious. I'm deploying the prometheus kube stack alongside our company's application on a local rancher desktop installation, on Ubuntu LTS 22.
I did not override any values. My assumption is that I would get standard metrics like pod CPU and memory consumption without manual adjustments.
What's your helm version?
version.BuildInfo{Version:"v3.16.4", GitCommit:"7877b45b63f95635153b29a42c0c2f4273ec45ca", GitTreeState:"clean", GoVersion:"go1.22.7"}
What's your kubectl version?
Client Version: v1.29.11 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.29.11+k3s1
Which chart?
kube-prometheus-stack
What's the chart version?
67.9.0
What happened?
Many of the grafana dashboards are empty (i.e. displaying no data), especially related to Compute Resources or Networking
The few that contain data are (not necessarily exhaustive)
For the pod-related dashboards, the pod names, number of running pods, requests and limits are available, but no usage data.
What you expected to happen?
I would expect metrics like pod cpu and memory usage are available in grafana
How to reproduce it?
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
helm upgrade --install prometheus prometheus-community/kube-prometheus-stack --namespace monitoring --create-namespace
Anything else we need to know?
Rancher desktop version: 1.17.0
Ubuntu version: 22.04.1
Kernel: 6.8.0-51-generic
The text was updated successfully, but these errors were encountered: