-
Notifications
You must be signed in to change notification settings - Fork 6
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
Queries with stats
don't work
#30
Comments
Ack, thanks for the quick reply! |
Hi @dmitryk-dk ! I have the same problem with query |
What version of the victorialogs do you use? |
@vakabayashy i have checked the request |
Bu i checked the request like |
Could you please update your query to Please pay attention that i changed |
Hi @ykrasik ! You can remove _time and use only Also, you can use the next expression, In the previous version of the victorialogs there was a bug with timestamp parsing, but in the newest version, it should be fixed |
Hi @dmitryk-dk ! I have updated to the latest version of Victorialogs v0.23.0, the errors remain. |
Hi @vakabayashy ! I have tested it on my local environment, and it works as expected. Also, we used our data source in the production. and I have checked it there The error that you got was before the fix. Try to upgrade the data source again and check the issue. Try to restart your Grafana server. It should update the backend part of the Grafana |
@vakabayashy Make sure you have the latest version of the datasource and try in incognito mode (it could be a cache issue). |
I fixed it. With the plugins installed in the directory |
Hi @ykrasik , @vakabayashy ! Can we close the issue? |
Fixed in 0.2.2, thanks! |
Still doesn't work with VL 0.24 and grafana datasource 0.2.2 for me. I'm checking some of the comments in this thread to see if I'm doing something wrong. VL no longer shows an error for queries with
The above happens for any query with |
I see - it's #34 Just updated to 0.2.3 and now everything works. Thanks! |
When running any query from Grafana with a stats pipe I get
got unexpected response status code: 400
. The same query without the stats pipe works and returns data.Smallest query which reproduces this error:
test | stats count()
I see this error for the above query in the VM logs:
So it seems that in the presence of a stats pipe in the query, the timestamp (which I guess the plugin adds by itself) is added through an
AND
which makes the whole query invalid.The text was updated successfully, but these errors were encountered: