-
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
Query filter does not work #72
Comments
Hi @Neko-Follower ! I have checked this question on my local, and it works. See examples below
Could you please share the version of the grafana? Also, as far as I can see you have the space between the field and value. Could you remove the space, please? |
I removed the space. It didn't work My Grafana version - 11.1.4 I'll try to downgrade Grafana to 10 and test. |
You are right. It is error 504 gateway timeout. I looked and there is no proxy between grafana and victorialogs.
I have a big amount of logs (~200 million). Maybe the problem is related to this. But I have a loki-stack on another Kubernetes cluster with bigger amount of logs. And there is no such problem. |
Yeah, I think the problem is with that. We need to discuss with our team about the problem |
Could you try to increase the |
Sure |
Thank you very much. I'll be waiting |
The correct query param names for /field_values are `start` `end`. See https://docs.victoriametrics.com/victorialogs/querying/#querying-field-values Sending `from` and `to` params meant time range filter wasn't applied at all. This made VictoriaLogs make the full data scan. Which probably caused the following issues: * #71 * #72
The correct query param names for /field_values are `start` `end`. See https://docs.victoriametrics.com/victorialogs/querying/#querying-field-values Sending `from` and `to` params meant time range filter wasn't applied at all. This made VictoriaLogs make the full data scan. Which probably caused the following issues: * #71 * #72
Hi @Neko-Follower ! The issue was resolved in the release. Please, reopen the issue if you find any problems |
Hi @Neko-Follower! I have investigated the issue. As far as I can see, there is a problem with Victorialogs API. Datasource works well. We will discuss it, and I will be back soon. |
The issue with returning unexpected field values has been fixed at VictoriaLogs server side in the commit VictoriaMetrics/VictoriaMetrics@0c0f013 . This commit will be included in the next release of VictoriaLogs. |
FYI, the issue with unexpected field values should be fixed in v0.32.1-victorialogs release. |
Hi @Neko-Follower ! Can you update the VictoriaLogs to the v0.32.1-victorialogs release and check the issue? |
Hi. I had the same issue with unexpected values, returned by 'uniq'. It is fixed now in the v0.32.1. |
Could you please create an issue in the VictoriaMetrics repository? Because this issue is mostly related to VictoriaLogs API |
Hi @dmitryk-dk ! I'll try it during the day and tell you about the results |
Hi! I updated to v0.32.1-victorilogs. Tested it, works great. Issue can be closed :) |
Hi. I want to use query filter, but it doesn't seem to work
The text was updated successfully, but these errors were encountered: