Skip to content
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

Provide more details about cpu and memory prometheus metric. #51

Open
WLBF opened this issue Jan 4, 2022 · 1 comment
Open

Provide more details about cpu and memory prometheus metric. #51

WLBF opened this issue Jan 4, 2022 · 1 comment
Assignees

Comments

@WLBF
Copy link

WLBF commented Jan 4, 2022

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.

@wangchen615
Copy link
Collaborator

@WLBF , thanks for reporting this. @atantawi got a similar experience by using helm to install prometheus.
The version @atantawi experienced issue is: https://prometheus-community.github.io/helm-charts/

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants