-
Notifications
You must be signed in to change notification settings - Fork 2.7k
fix(metrics): make prometheus labels more type safe #5717
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
Conversation
Hi @mwmix. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
Looks nice. We may going to have a higher chances of cyclic dependencies, as TODO: to review when merged prometheus/client_golang#1598 /lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mloiseleur 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 |
@mwmix, @ivankatliarchuk , I think this change triggers race condition:
Exact error I get is: ![]() on b31afb4 |
What does it do ?
Ensure labels are more type safe and applied in the correct order.
Motivation
While working on PR #5665 it was determined that we could use more type safety for prometheus labels.
More