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
Query without timestamp sometimes returns empty result #212
Labels
Comments
jacksontj
added a commit
that referenced
this issue
Aug 29, 2019
Workaround to #212 Upstream issue: prometheus/prometheus#5972
Thanks for the bug report! Sure enough I can reproduce this issue with ease. I was able to debug the issue and found that it is actually a prometheus issue (prometheus/prometheus#5972) TLDR the While that gets sorted out I have implemented a workaround in #213 |
jacksontj
added a commit
that referenced
this issue
Aug 29, 2019
Workaround to #212 Upstream issue: prometheus/prometheus#5972
jacksontj
added a commit
that referenced
this issue
Sep 3, 2019
jacksontj
added a commit
that referenced
this issue
Sep 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With promxy version v0.0.44 and up I sometimes get an empty result when querying promxy like this:
As soon as I set the
time
request parameter the issue disappears. I was unable to gather anything interesting from the promxy debug logs, here we have two requests, the first one worked and the second one produced an empty result (see the differences in the response size)I'm running promxy in front of two prometheus v2.11.1 instances on kubernetes. If I downgrade to v0.0.43 I cannot reproduce the issue. Anything later produces empty results in about half of the requests.
The text was updated successfully, but these errors were encountered: