-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[feature request] SHOW TAG VALUES should respect fields in the WHERE clause #3040
Comments
Probably one I should fix, as I rework the query engine. |
@otoolep Are you planning to have the parser throw an error or try to make the WHERE clause actually function? The latter would require pulling in all points in the series, which seems very expensive for little gain, but this is also assumed to be an infrequent query. Maybe we require a |
Short-term we should just throw a parser error on the |
I am experiencing the same issue. I would like to be able to filter tag values using time and other tags that share a measurement (if this is possible). e.g. "SHOW TAG VALUES FROM measurement_name WHERE other_measurement_tag = x AND time < y" If I am understanding the information noted in this issue above, we are not able to do either at this point. Is the intent to eventually allow for querying tag values with filtering based on related tags and/or time? Seems like it might be useful in certain instances... |
Tested on 0.9.2. This issue appears to be resolved! |
Confirmed fixed in 0.9.2, but only for WHERE clauses with tags. Doesn't work for WHERE clauses with fields (which makes sense, that necessitates a full scan), but there should be better error handling: This all makes sense:
All good to this point, but
Even garbage passes the parser, returning no results, as long as there's something in the WHERE clause.
|
Should this respect a |
@lexh You can mostly get what you want with an actual SELECT query:
You must include at least one field in the If you do want the |
Ah, I see. Thanks for the suggestion, that will work for me for the time being. I will ruminate on this and possibly open a new issue once I've organized my thoughts. |
Is there any status update of this? I'd like to use something like |
@aheusingfeld this feature request is currently unscheduled. |
@beckettsean hm, that's strange because this query |
@aheusingfeld are you sure the results are scoped by time? There are some Also, this feature request is about using fields in the |
I'm also a Grafana user, and i want to create a Server Resource Dashboard, to monitor also Processes from a given Server. will be usefull to have all processes being monitored for a given host. Then, it can be templated to expand a graph for each process. Do you have some deadline for this feature? |
This feature would make dashboards even more powerful on grafana |
This actually worked in v0.10, but broke in v0.11.1. The WHERE clause on SHOW TAG VALUES still works with =~ operator, but fails with !~ operator. |
I'm closing this since I don't think it's feasible for us to do the original request with allowing comparison against fields for But, you can use |
Or it should throw a parser error, one of the two. Right now it appears to parse but has no effect on the output:
Everything works as expected up to this point. Now add a WHERE clause to the SHOW TAG VALUES query:
It's returning both keys, even though
value > 3
should excludeval1
if it is being respected. If the WHERE clause is not being respected, why does it parse?The text was updated successfully, but these errors were encountered: