Skip to content
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

querier: Allow passing allow-list of store (IPs?) that should be used for query for debug purposes; Add multiselect on UI #2919

Closed
bwplotka opened this issue Jul 22, 2020 · 7 comments

Comments

@bwplotka
Copy link
Member

It would be awesome to add the ability to query only a subset of stores to detect which one is slow/ problematic etc (: It should be hidden option only for ad-hoc query.

@geobeau
Copy link
Contributor

geobeau commented Jul 22, 2020

I am interested in doing it.

After looking at how to implement it, I have a design question: the query api uses the proxy as a storepb.StoreServer and the logic behind the store selection is done after calling storepb.StoreServer.Series(), however there is no way of passing an allowlist without extending the interface. Would be okay to change querier.proxy to use directly ProxyStore in place of storepb.StoreServer?

@bwplotka
Copy link
Member Author

Awesome. I think it would be nice to avoid passing this in protobuf, but we could technically create some hints.

I would also avoid running just ProxyStore and changing methods.

We have two options:

  1. Pass through context as a best-effort thing
  2. Extend protobuf

I would start for now with 1 and then 2 long term. WDYT? (:

@geobeau
Copy link
Contributor

geobeau commented Jul 23, 2020

Pass through context seems good for me. 👍

@geobeau
Copy link
Contributor

geobeau commented Jul 23, 2020

Hello, can you take a look at #2931 ? It's still in WIP as I need to finish the testing but I would like your input first.

@bwplotka
Copy link
Member Author

bwplotka commented Jul 23, 2020 via email

@stale
Copy link

stale bot commented Aug 22, 2020

Hello 👋 Looks like there was no activity on this issue for last 30 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for next week, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

@stale stale bot added the stale label Aug 22, 2020
@bwplotka
Copy link
Member Author

It's now done in #2931 and documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants