-
Notifications
You must be signed in to change notification settings - Fork 818
Update prometheus #802
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
Update prometheus #802
Conversation
e276615
to
e184829
Compare
Move from one brittle assumption about Prometheus to another.
e184829
to
9e41258
Compare
Gopkg.toml
Outdated
@@ -19,6 +19,10 @@ | |||
name = "github.com/prometheus/prometheus" | |||
branch = "master" | |||
|
|||
[[constraint]] |
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.
Didn't we want to have comments for newly added constraints?
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.
good spot
pkg/querier/querier.go
Outdated
func NewEngine(distributor Querier, chunkStore ChunkStore) *promql.Engine { | ||
queryable := NewQueryable(distributor, chunkStore, false) | ||
return promql.NewEngine(queryable, nil) | ||
func NewEngine(distributor Querier, chunkStore ChunkStore, reg prometheus.Registerer, maxConcurrent int, timeout time.Duration) (*promql.Engine, storage.Queryable) { |
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.
Having NewEngine()
return both an engine and a queryable seems messy, or at least not appropriate naming anymore. Maybe just get rid of this tiny wrapper and have the caller call both NewQueryable()
and promql.NewEngine
?
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.
Agreed; I've done this.
We don't need more specific parameters as ruler already knows the number of workers and has a timeout.
I've also re-applied the change described at #763 (comment) which I hadn't noticed before #763 was merged. |
This is a re-run of #763, updated to address the broken assumption about which queriers are used where.