mirror of
https://github.com/prometheus/prometheus.git
synced 2024-11-09 23:24:05 -08:00
Add feature flag
Signed-off-by: Danny Kopping <danny.kopping@grafana.com>
This commit is contained in:
parent
940f83a540
commit
ed2933ca60
|
@ -158,6 +158,7 @@ type flagConfig struct {
|
||||||
enablePerStepStats bool
|
enablePerStepStats bool
|
||||||
enableAutoGOMAXPROCS bool
|
enableAutoGOMAXPROCS bool
|
||||||
enableAutoGOMEMLIMIT bool
|
enableAutoGOMEMLIMIT bool
|
||||||
|
enableConcurrentRuleEval bool
|
||||||
|
|
||||||
prometheusURL string
|
prometheusURL string
|
||||||
corsRegexString string
|
corsRegexString string
|
||||||
|
@ -204,6 +205,9 @@ func (c *flagConfig) setFeatureListOptions(logger log.Logger) error {
|
||||||
case "auto-gomemlimit":
|
case "auto-gomemlimit":
|
||||||
c.enableAutoGOMEMLIMIT = true
|
c.enableAutoGOMEMLIMIT = true
|
||||||
level.Info(logger).Log("msg", "Automatically set GOMEMLIMIT to match Linux container or system memory limit")
|
level.Info(logger).Log("msg", "Automatically set GOMEMLIMIT to match Linux container or system memory limit")
|
||||||
|
case "concurrent-rule-eval":
|
||||||
|
c.enableConcurrentRuleEval = true
|
||||||
|
level.Info(logger).Log("msg", "Experimental concurrent rule evaluation enabled.")
|
||||||
case "no-default-scrape-port":
|
case "no-default-scrape-port":
|
||||||
c.scrape.NoDefaultPort = true
|
c.scrape.NoDefaultPort = true
|
||||||
level.Info(logger).Log("msg", "No default port will be appended to scrape targets' addresses.")
|
level.Info(logger).Log("msg", "No default port will be appended to scrape targets' addresses.")
|
||||||
|
|
|
@ -212,3 +212,13 @@ Enables ingestion of created timestamp. Created timestamps are injected as 0 val
|
||||||
Currently Prometheus supports created timestamps only on the traditional Prometheus Protobuf protocol (WIP for other protocols). As a result, when enabling this feature, the Prometheus protobuf scrape protocol will be prioritized (See `scrape_config.scrape_protocols` settings for more details).
|
Currently Prometheus supports created timestamps only on the traditional Prometheus Protobuf protocol (WIP for other protocols). As a result, when enabling this feature, the Prometheus protobuf scrape protocol will be prioritized (See `scrape_config.scrape_protocols` settings for more details).
|
||||||
|
|
||||||
Besides enabling this feature in Prometheus, created timestamps need to be exposed by the application being scraped.
|
Besides enabling this feature in Prometheus, created timestamps need to be exposed by the application being scraped.
|
||||||
|
|
||||||
|
## Concurrent evaluation of independent rules
|
||||||
|
|
||||||
|
`--enable-feature=concurrent-rule-eval`
|
||||||
|
|
||||||
|
Rule groups execute concurrently, but the rules within a group execute sequentially; this is because rules can use the
|
||||||
|
output of a preceding rule as its input. However, if there is no detectable relationship between rules then there is no
|
||||||
|
reason to run them sequentially. This can improve rule reliability at the expense of adding more concurrent query
|
||||||
|
load. The number of concurrent rule evaluations can be configured with `--rules.max-concurrent-rule-evals` which is set
|
||||||
|
to `4` by default.
|
||||||
|
|
Loading…
Reference in a new issue