-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lens autodetects my Prometheus installation but doesn't display metrics #8073
Comments
Oh interesting, bit of extract context in the logs if opening up from the CLI.
|
Hello Starttoaster, Thank you for reaching out to Lens support! Thank you for reporting a bug. We are working on your issue. Stand by for further updates. Best Regards, |
Same issue here I have all components installed in the Cluster but cant see CPU usage metric. When using kubectl top node it shows CPU usage , I use kube-prometheus-stack helm chart all metrics available in dashboards but CPU usage for Nodes and Pods isn't available for Lens. |
Same issue using prometheus-operator. Also did this steps: https://github.com/lensapp/lens/blob/master/troubleshooting/custom-prometheus.md |
Describe the bug
Lens autodetects my Prometheus installation but doesn't display metrics. I have kube-state-metrics installed in the cluster and node-exporter running on the hosts. The prometheus instance that Lens detects is scraping those exporters, but Lens isn't able to find them. The Lens documentation doesn't list anything as far as metric relabelings it requires or really any configuration details that may be required to get it to work.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect to be able to see my node/Pod metrics contained by Prometheus.
Screenshots
I can add some if needed but not sure which pictures would be useful to add onto my description.
Environment (please complete the following information):
Additional context
This is an on-prem cluster if that matters. My local user has RBAC permissions to port forward Services. Perhaps not proxy those services though.
The text was updated successfully, but these errors were encountered: