-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Export metric_server_response like other VPA recommender metrics #5111
Export metric_server_response like other VPA recommender metrics #5111
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jbartosik 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 |
/hold |
2cd7324
to
ecc9f01
Compare
/hold cancel |
ecc9f01
to
322be71
Compare
5569ea9
to
7cde47e
Compare
In case we instantiate multiple clients and want to distinguish responses they're getting
7cde47e
to
abcbe8f
Compare
/lgtm |
…nses Export metric_server_response like other VPA recommender metrics
There is no reason for the metric to be exported differently than other metrics
Hyphens in name of the metric caused prometheus errors
Which component this PR applies to?
VPA recommmender
What type of PR is this?
/kind bug
What this PR does / why we need it:
VPA recommender fails to initialize because we call MustRegister on a metric with an invalid name and the registration fails.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: