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
@joaquimrocha I'm seeing this in metrics for RAM in deployments and pods too. Probably other places as well?
Grafana and crictl report values correctly but headlamp is showing much more.
Example, the headlamp pod, in the Headlamp UI is showing 40 MB RAM being used but it's actually 20.76 MB according to Grafana and crictl So looks like about double.
CPU and network are correct.
Is this going to get fixed soon, it's confusing our users.
Headlamp 0.25.1
Hi @mariogkds@sarg3nt , thanks for raising these issues! Would you be able to provide the YAML (with any sensitive data redacted) for the problematic resources? Would be super helpful for testing ^^
Hi @mariogkds and @sarg3nt , we really want to address this issue but we haven't been able to reproduce. If you don't mind, please send us some sample YAML based on yours so @skoeva can take a look.
Hello, i am a new user, i really liked the project.
I am having some problems with the cluster wide metrics that are show on the dashboard:
I am using kube-prometheus-stack to handle prometheus and grafana and i am using prometheus-adapter for the metrics API.
To get the headlamp to even show anything i had to add a few settings to the chart's values:
kube-prometheus-stack
prometheus-adapter (which is normal to get the metrics apis)
Individual node's CPU values are correct, the memory value is correct as well but the unit is different:
Is this a headlamp problem or this a prometheus(me) problem?
Thanks for the help and the project have a nice day.
The text was updated successfully, but these errors were encountered: