-
Notifications
You must be signed in to change notification settings - Fork 31
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
System metrics support #87
Comments
+1 this should be pretty useful. How about "latency for pod be scheduled and become ready"? |
Or do you mean Replica? Pod seems not that important. |
yep, Replica makes sense |
/assign |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
"Hey, do we still need this feature? I'm not sure why the PR got closed back then and nothing happened afterwards. If it is still needed, I can take a shot at it." @kerthcet @liurupeng @Edwinhr716 |
The PR got closed due to lack of clarity on what each metric was measuring. If we want to continue with the issue, it would be good to agree on what metrics we want to be added and what each metric entails |
Yes, we do. I'll categorize them once I had time and submit a pr as a demo. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
What would you like to be added:
We should add some metrics for tracking the health of the system, some of them like:
Please add more if you think so.
Why is this needed:
Providing insight of the system
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: