Julien Pivotto 9adad8ad30 Remove MaxConcurrent from the PromQL engine opts (#6712) ... Since we use ActiveQueryTracker to check for concurrency in d992c36b3a it does not make sense to keep the MaxConcurrent value as an option of the PromQL engine. This pull request removes it from the PromQL engine options, sets the max concurrent metric to -1 if there is no active query tracker, and use the value of the active query tracker otherwise. It removes dead code and also will inform people who import the promql package that we made that change, as it breaks the EngineOpts struct. Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>		2020-01-28 20:38:49 +00:00
..
fixtures	Delete prometheus_rule_group metrics when groups are removed (#6693)	2020-01-27 12:41:32 +00:00
alerting_test.go	Remove MaxConcurrent from the PromQL engine opts (#6712)	2020-01-28 20:38:49 +00:00
alerting.go	Check that rules don't contain metrics with the same labelset (#6469)	2019-12-18 12:29:35 +00:00
manager_test.go	Remove MaxConcurrent from the PromQL engine opts (#6712)	2020-01-28 20:38:49 +00:00
manager.go	Delete prometheus_rule_group metrics when groups are removed (#6693)	2020-01-27 12:41:32 +00:00
recording_test.go	Remove MaxConcurrent from the PromQL engine opts (#6712)	2020-01-28 20:38:49 +00:00
recording.go	Check that rules don't contain metrics with the same labelset (#6469)	2019-12-18 12:29:35 +00:00