-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: Add new metric kube_pod_scheduler #2222
feat: Add new metric kube_pod_scheduler #2222
Conversation
Welcome @adinhodovic! |
/assign @dgrisonnet |
Signed-off-by: adinhodovic <hodovicadin@gmail.com>
0d9a9df
to
c5c6c9a
Compare
internal/store/pod.go
Outdated
"", | ||
wrapPodFunc(func(p *v1.Pod) *metric.Family { | ||
m := metric.Metric{ | ||
LabelKeys: []string{"scheduler_name"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am wondering if having something like kube_pod_scheduler{name="foo"}
could be better to remove the redundancy with the metric name its label.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think that makes sense. Updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adinhodovic, dgrisonnet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Adds a new pod metric
kube_pod_scheduler_name
that allows seeing which scheduler scheduled the pod. Allows aggregation by scheduler.How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
Increases.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #2207