-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Remove GC ratelimiter metrics #52867
Conversation
I would prefer to disable GC metrics altogether rather than continue to do this as "metric per group version" vs "label and series per group version" which is the correct way. We threw some of these metrics in and we didn't actually follow the appropriate patterns. |
91bac17
to
ad1009c
Compare
updated to remove GC ratelimiter metric registration |
cc @cheftako |
ad1009c
to
a0f8a36
Compare
@deads @caesarxuchao @ironcladlou for GC |
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
We do need to start protecting ourselves from the prometheseus.MustRegister() call but I have filed a separate issue for that.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheftako, liggitt, smarterclayton Associated issue: 52801 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@liggitt: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here.. |
Fixes #52801
The metrics were causing panics because the names weren't formatted correctly, there were concerns around the number of metrics series that resulted from registration per group/version, and the saturation metric being reported was of questionable use