Open akelge opened 1 year ago
Hello everyone, January 26, 2024 and I am in exactly the same situation. Same problem - unable to change scraping interval in Prometheus without losing CPU usage in Lens panel. If you ask me it should be one of the basic functionalities.
Yes same issue not working CPU Usage metrics for example for Node
What would you like to be added: Currently when I configure metrics reading on a cluster I have 5 options plus autodetect. Each option has its own hardcoded value for
rateAccuracy
, I would like if this can become a setting parameter.Why is this needed: I use
kube-prometheus-stack
helm chart to deploy the full stack on K8S clusters, but I would like to change thescrapeInterval
to 1 minute instead of the default 30 seconds. If I do so this breaks CPU reporting in Lens, cause the detected prometheus (operator) has a defaultrateAccuracy
of 1 minute that makes some CPU metrics query report empty results.Environment you are Lens application on: