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

query-frontend: match[] query parameters not passed to downstream querier #4580

Closed
crsandeep opened this issue Aug 18, 2021 · 2 comments · Fixed by #4585
Closed

query-frontend: match[] query parameters not passed to downstream querier #4580

crsandeep opened this issue Aug 18, 2021 · 2 comments · Fixed by #4585

Comments

@crsandeep
Copy link
Contributor

Thanos version - v0.22.0

What happened:

I made a labels API query to query-frontend ex: /api/v1/label/cluster/values?start=1628762940&end=1628784540&match[]=go_goroutines
But match[] query parameter was not sent to downstream querier

What you expected to happen:
match[] parameter sent to downstream querier

How to reproduce it (as minimally and precisely as possible):
Start prometheus and let it scrape its own metrics and then start query-frontend and use prometheus as downstream url. Make a labels API call with match[] query parameter.

Anything else we need to know:
I believe the matcher param is not being read for labels API here https://github.com/thanos-io/thanos/blob/main/pkg/queryfrontend/labels_codec.go#L276-L289 unlike series API https://github.com/thanos-io/thanos/blob/main/pkg/queryfrontend/labels_codec.go#L320-L323. Any reason to not read match[] param for labels API? I can send a PR to fix this if this is a valid issue.

@yeya24
Copy link
Contributor

yeya24 commented Aug 19, 2021

Valid issue. Thanks for the reporting. The match[] parameter is relatively newly added so we don't have its support in the query frontend. Help wanted.

@crsandeep
Copy link
Contributor Author

Great. I will work on this and send a PR soon.

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

Successfully merging a pull request may close this issue.

2 participants