Skip to content

Decouple ConfigDB & Ruler #1547

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

Closed

Conversation

jtlisi
Copy link
Contributor

@jtlisi jtlisi commented Jul 31, 2019

This is the first of several PRs that will decouple the ruler from the configdb and allow for the updated API and flexible storage options as outlined in this design document

This PR is a subset of the changes in #1513, and is meant to break the referenced PR into smaller more manageable components

  • Decouple the scheduler from the polling mechanism used to query the configdb
  • Update the scheduler to use a user-based context to allow for cancellations after updates or deletions
  • Pass a prometheus register with the users ID to the prometheus rule group to get user level prom eval metrics

Signed-off-by: Jacob Lisi jacob.t.lisi@gmail.com

Signed-off-by: Jacob Lisi <jacob.t.lisi@gmail.com>
@jtlisi jtlisi closed this Aug 9, 2019
@jtlisi jtlisi deleted the 20190731_decouple_configdb_ruler branch August 9, 2019 18:47
@jtlisi jtlisi mentioned this pull request Mar 12, 2020
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant