-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 prometheus version check? #1159
Comments
Thanks for reporting. Yea I think sidecar erroring on custom build of Prometheus is wrong. I am pretty sure we should make this check non-blocking OR remove version fetch totally and try to grab flags and if fails with 404 just continue without those extra checks. What do you think? PRs welcome (: |
Removing code is always my preferred solution :) Just logging and continuing might just work here? I.e
|
It's more involved if you see the code. AFAIK we check version ONLY to double check if we can continue with extra validation -> as only from 2.2.X there is new I would say if we can drop version check and just check |
Ah yes, I see in
And then it will try to get the flags from prometheus and perform some validation. From the looks of it, the version stuff can removed and just try to grab the flags; if they are there do the extra validation and otherwise just log something and return This means removing the version related functions from |
Potential PR: #1163 |
Closing as the PR was merged. |
Hi there,
We're using thanos (0.4) but it checks the version of prometheus (I understand why this is done) on startup. Unfortunate we compile our own prometheus and add some fluff to the version. This makes the check fail and prevents thanos (store) from starting.
We've patched out the check for now.
I'm not sure what the right course of action here is. Either allow the check to fail and still start (via some cmdline flag) or some such?
A better, but more involved way, would be to probe for functionality you need want from prometheus and only abort when that is not available.
The text was updated successfully, but these errors were encountered: