-
Notifications
You must be signed in to change notification settings - Fork 489
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
Decouple configuration store from scraping service #445
Conversation
edb116f
to
a01ab53
Compare
Taking this out of draft. I think we can merge it in this state and follow up with a few more PRs to hook it in. |
if otherConfig.Name == cfg.Name { | ||
continue | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not in love with this, but I cant think of a better way to do it with the default set of golang collections.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like the uniqueness checking at all honestly. We have #398 in the backlog to try to avoid this altogether
* initial commit of a configstore * review feedback
PR Description
This PR starts the work of decoupling the configuration store from the scraping service. This will eventually be needed to make the KV-based configuration store optional, but is more immediately useful to
/-/reload
(#147) where we may want to dynamically update the configuration for a store.Which issue(s) this PR fixes
Related to #147.
Notes to the Reviewer
Not hooked in yet. I didn't want to delete too much code from
pkg/prom/ha
so this didn't become too hard to review.The HTTP API for the config store would move to this new package too.
Tagging @mattdurham and @56quarters to get some early thoughts. This will be a pretty drastic change from how the scraping service was handled before.