Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Implement quorum reads and response merging for /v1/alerts. #4126
Implement quorum reads and response merging for /v1/alerts. #4126
Changes from 1 commit
3a9f166
d72a357
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Super-Nit: Not sure this package carries its own weight. I know there will be v2 implementation too, but it's still looks pretty thin. Same goes for
Merger
interface.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 agree and wasn't 100% sure what to do. The
pkg/alertmanager
package is getting very busy, was my reasoning here.Would a
pkg/alertmanager/distributor
perhaps be better?Also regarding the interface, I'd be equally happy with functions, if that's what you meant? (I was mainly taking inspiration from here
cortex/pkg/querier/queryrange/query_range.go
Line 67 in 94b0137
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.
Personally I would just use
pkg/alertmanager
, I think it's still a small package.Yes, I was thinking about just using functions here. My reasoning is that 1) we're only going to have 2 implementations (v1, v2 api) and 2) client doesn't need to supply its own implementation. But I am first to admit this is just a personal preference for this specific case, and don't mind keeping it as-is.
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 have a strong opinion here. I personally did like the
merger
package, given it's content is self contained but moving topkg/alertmanager
looks good to me as well. Let's just not block on this. V2 merging PR is awaiting for this PR! 😉I wouldn't name the package distributor because we already have
pkg/distributor
and in the past (when we triedpkg/alertmanager/distributor
at some point) we realised it was causing much confusion when reading the code.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.
Leaving as-is to unblock, happy to refactor after the fact.