-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Inconsistency of the behaviors of handling labelValues requests and external labels #3639
Comments
So for |
I think we should pick up external labels only for blocks within the query time range. In your example, if the |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Fixed in #6816 |
We are using different ways to handle
LabelValues
requests for each store.For
PrometheusStore
which is the sidecar, it checks whether the label we want exists in external labels, if so just return the value.For
BucketStore
, we get the label values from the block's index and attach the external label value if it matches.For
TSDBStore
, we just ignore the external labels. https://github.com/thanos-io/thanos/blob/master/pkg/store/tsdb.go#L221-L235.I think we need to define the correct logic of the external labels handling for Labels API to make the whole thing more clear. As we plan to support matchers #3637 so it would be more complex.
The text was updated successfully, but these errors were encountered: