-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat(pod): Add new metric for pod unscheduled time tracking #2699
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
base: main
Are you sure you want to change the base?
feat(pod): Add new metric for pod unscheduled time tracking #2699
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: yshngg The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This issue is currently awaiting triage. If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Welcome @yshngg! |
ca3e60a
to
3980c09
Compare
The changes introduce a new metric generator `kube_pod_status_unscheduled_time` to record the Unix timestamp when pods transition to unscheduled status. This enhances monitoring capabilities for scheduling issues by capturing exact transition times during `PodScheduled` condition changes.
3980c09
to
a483701
Compare
Could you share use cases after adding this metric kube_pod_status_unscheduled_time? |
Hi @CatherineF-dev, In my use case, this metric enables proactive scheduling failure monitoring by supporting alerting workflows (e.g., triggering alerts when Pods remain unschedulable > 5 minutes to prevent service degradation). |
What this PR does / why we need it:
The changes introduce a new metric generator
kube_pod_status_unscheduled_time
to record the Unix timestamp when pods transition to unscheduled status.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 #2698