-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Change in selector behaviour for != #3575
Comments
Yep, this is confirmed and doesn't look like a trivial change. Will work on this whenever I get time, but cannot commit to anything. So, essentially this here is not selecting stuff which doesn't have a label set: https://github.com/prometheus/tsdb/blob/master/querier.go#L257-L306 One of the proposals is that we could materialise a view which has the postings for all series where We could also not bleed this into tsdb and rather make Prometheus make 2 queries, one with "absent" matcher, one with "!=" and then merge the results of the two. /cc @krasi-georgiev |
I don't think this should leak, and there could be multiple such selectors. |
Fixes prometheus#3575 Comes with a slight performance penalty which is better off addressed in tsdb Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>
Fixes prometheus/prometheus#3575 Signed-off-by: Goutham Veeramachaneni <cs14btech11014@iith.ac.in>
Fixes prometheus/prometheus#3575 Signed-off-by: Goutham Veeramachaneni <cs14btech11014@iith.ac.in> Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What did you do?
query:
metrics{label != "thing"}
where label is not set.
What did you expect to see?
In prometheus 1.6.3 this will return all the items where label != "thing", including items where label is not set at all.
What did you see instead? Under which circumstances?
In prometheus 2.0 items without label set are not returned.
The text was updated successfully, but these errors were encountered: