-
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
storeAPI: Extend ExternalLabels Selector for LabelsNames and LabelValues #3351
Comments
I think this would be best solved with a combination of prometheus/prometheus#6178 (and implementing the equivalent in Thanos) and support for enforcing a matcher for this API in prom-label-proxy. |
Nice, the only problem - or rather a potential improvement I can see here is that we can do it much faster IF the selectors match external label. But we can implement that easily indeed. |
Yeah sounds pretty much equivalent to labelset in series queries ("definitely not in set"). |
👍 👍 |
Hi, I am looking at the implementation at prometheus/prometheus#7496. |
@yeya24 have we validated that it is indeed a problem performance wise? I can see what you mean of course, just want to make sure we base this on measurements and not fear :) |
You are right and I haven't benchmarked it. |
This would be really awesome for further multi-tenancy support with https://github.com/prometheus-community/prom-label-proxy
Since tenants never share the same TSDB block or DB we can easily allow LabelValues and LabelNames API selection support for tenant's data.
The only open question is compatibility. Do we want extra check to ensure if server supports this or not? Without such check we know nothing: The lack of selection might be transparent causing tenant data leak.
cc @pracucci @brancz @yeya24 @kakkoyun
The text was updated successfully, but these errors were encountered: