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
It took me some time to find out what exactly instance:node_cpu:ratio metirc is. It seems cpu and memory metric is come from helm-charts/charts/kube-prometheus-stack/templates/prometheus/rules/kube-prometheus-node-recording.rules.yaml rule which is is removed and seems be repalced by instance:node_load1_per_cpu:ratio rule in later verison. I think it is better to have detail description about cpu and memory metric and provide a way to configure name of cpu and memory metric.
The text was updated successfully, but these errors were encountered:
Currently, the node usage metrics we used are from instance:node_cpu:ratio and instance:node_memory_utilisation:ratio. The successful tested version of prometheus is kube-prometheus, https://github.com/prometheus-operator/kube-prometheus .
We will dig out more details about the helm version and see if there is a need to allow developers to configure the metric name.
It took me some time to find out what exactly
instance:node_cpu:ratio
metirc is. It seems cpu and memory metric is come from helm-charts/charts/kube-prometheus-stack/templates/prometheus/rules/kube-prometheus-node-recording.rules.yaml rule which is is removed and seems be repalced byinstance:node_load1_per_cpu:ratio
rule in later verison. I think it is better to have detail description about cpu and memory metric and provide a way to configure name of cpu and memory metric.The text was updated successfully, but these errors were encountered: