-
Notifications
You must be signed in to change notification settings - Fork 177
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
Unexpected upstream response #397
Comments
Thanks for this report. In the next release, we'll enhance this log entry to include the full inbound (from grafana) client request, and Trickster outbound response (to prom), and the Prometheus full response. So that way, you can provide us with further detail that might point towards a root cause. Separately we will look at reproducing and root causing the behavior. |
Today it happened again (after nearly 1day running). Checking the log I can only see these lines:
I don't see any |
I ended up using the previous version, and it seems working well so far (4 days) |
@chicknsoup thanks for this info on the file descriptors, after fixing your dashboard queries. Looks like this may now be a duplicate of #391, which we'll be issuing a patch version 1.0.3 shortly. Thanks for your information and helping us get to the bottom of it! (p.s. we will still include the additional detail for Unexpected Upstream Response in the 1.1 version) |
we believe this to be resolved during the beta cycle, please reopen if the GA version of 1.1 still brings you to the max file limits. |
I have to restart trickster once every week or so in order to normally query from Grafana. Checking the log file, there are only unexpected upstream response errors, nothing else.
Prometheus queries still ok, restarting trickster fixes the problem.
The text was updated successfully, but these errors were encountered: