-
Notifications
You must be signed in to change notification settings - Fork 799
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
Switch Cortex Ruler to query Query Frontend #5105
Comments
Hi @yeya24! |
Hi @xuyangwang0825, thanks for expressing interest in this project. Feel free to apply through the LFX website! |
Hello @yeya24 |
Hi @mallikpramod, please apply in the LFX mentorship website but I don't think I am mentoring this project. We have @alvinlin123 and @qinxx108 mentoring it. |
Hi @yeya24 |
@xuyangwang0825 Yes, selected mentee name should be in the LFX project page. |
🥹 |
I remain deeply interested in open-source projects in cloud native. However, I recognize that there may be areas in which I need to improve in order to become a better candidate. Could you please provide me with some feedback on my application? I would appreciate any insights you can offer on which aspects of my background or experience, or skills I should focus on improving. Thank you so much! |
@yeya24 |
Hi @SungJin1212, it would be great if you could start a proposal outlining possible approaches and alternatives. |
@yeya24
Sincerely |
@yeya24 |
Is your feature request related to a problem? Please describe.
As we can see from the Cortex architecture https://cortexmetrics.io/docs/architecture/, Ruler queries ingesters (and store gateways) to get data for rules evaluation. This works fine currently but it hard to reuse some features supported in query frontend like vertical query sharding to make rule evaluation faster.
By switching Ruler to query Query Frontend, it simplifies the current architecture to make Query Frontend the entrypoint for both external and internal queries. Ruler components can use less resources as it doesn't need to embed a querier anymore.
Describe the solution you'd like
This feature should be behind a feature flag. If the flag is specified, Ruler will query Query Frontend instead. The implementation should be similar to how Thanos does https://github.com/thanos-io/thanos/blob/main/cmd/thanos/rule.go#L795, by having a custom query func and send HTTP requests to query frontend.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: