-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Stop using the global prometheus registry #1460
Stop using the global prometheus registry #1460
Conversation
This removes the http_* metrics. The instrument handler is deprecated as it needs to be rewritten. Not sure you would like to keep them? |
Depending on the outcome of the discussion in kubernetes/kubernetes#32638 we'll need to change the integration of cAdvsior in the kubelet once this PR is merged. We probably could also just stop using |
👍 I don't mind the loss of http_* metrics. |
@grobie Needs a rebase please. |
@jimmidyson done |
Is this awaiting a maintainer review? |
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
CLAs look good, thanks! |
Anything left for me to do here? If you're not going to accept this, I can also just close it. @jimmidyson @dashpole |
|
Might be related prometheus/client_golang@f0c45ac ? |
I'm sorry for the noise @dashpole. I updated the dependencies (which will bring several improvements to the metrics exported by Prometheus) and that fixed the build. |
sorry, this fell off of my radar. |
Replace usage of the global Prometheus registry with a private registry object which will be exported under the given prometheus path.
@dashpole you sure you want me to squash these two commits together? I'm not sure I see the point, they are independent changes which can be applied in isolation. Given the massive diff caused by vendor updates, I understood it to be best practice to separate them from actual code changes. |
usually, we just squash to make the git tree more readable, but I see your point. We can merge this as is once tests pass. |
@dashpole another week of ping pong ;-) |
Ill see if I can get the test infra stuff fixed today. Then we can merge this. |
Verified that this PR causes #1671 and kubernetes/kubernetes#47744. It seems that Prometheus v0.8.0 added some consistency check prometheus/client_golang#214, which breaks the metrics. Filed #1679 to work around this for now. We should figure out and fix the inconsistent metrics in the future. |
Replace usage of the global Prometheus registry with a private registry
object which will be exported under the given prometheus path.
Fixes #1459.