![]() ![]() # CLI flag: -http.alertmanager-http-prefix # (advanced) HTTP URL path under which the Alertmanager ui and api will be # CLI flag: -api.skip-label-name-validation-header-enabled ![]() # specific HTTP header set to true will not have label names validated. Allowing this for external clients allows any # X-Mimir-SkipLabelNameValidation header on the http write path. # (advanced) Allows to skip label name validation via # (advanced) Set to true to enable all Go runtime metrics, such as go_sched_* # CLI flag: -max-separate-metrics-groups-per-user # distributor and ingester metrics can be further separated. # (experimental) Maximum number of groups allowed per user by which specified ![]() # SIGTERM, Mimir will report not-ready status via /ready endpoint. # (experimental) How long to wait between SIGTERM and shutdown. # (advanced) Tenant ID to use when multitenancy is disabled. When set to false, tenant ID from -auth.no-auth-tenant # When set to true, incoming HTTP requests must specify tenant ID in HTTP # command line flag to get a list of available components, and to see which # functional Grafana Mimir instance in single-binary mode. # default value 'all' includes all components that are required to form a Configuration parameters # Comma-separated list of components to include in the instantiated process. Where default_value is the value to use if the environment variable is undefined. References to undefined variables are replaced by empty strings unless you specify a default value or custom error text. The replacement is case-sensitive and occurs before the YAML file is parsed. Where VAR is the name of the environment variable.Įach variable reference is replaced at startup by the value of the environment variable. To do this, pass -config.expand-env=true on the command line and use To set values that need to be configurable during deployment. You can use environment variable references in the YAML configuration file Use environment variables in the configuration If you configure Mimir with a removed parameter, Mimir will fail to start. Use the metric deprecated_flags_inuse_total to determine whether you’re using deprecated flags.Ī configuration parameter is in maintenance and usable as expected between its deprecation and removal. After two more minor releases, a deprecated flag will be removed entirely. If we decide to eliminate a basic or advanced parameter, we will first mark it deprecated. We aim to make this decision on an experimental parameter within 6 months of its initial release, but this decision may take longer depending on what we discover during testing, or if upstream dependencies (e.g., Prometheus) of our code changes. Parameters that are made stable will be classified as either basic or advanced. When new parameters are added, they can be introduced as basic, advanced, or experimental.Įxperimental parameters will remain experimental until they are either made stable or removed. In this reference, experimental-category parameters include (experimental) at In this reference, advanced-category parameters include (advanced) atĮxperimental parameters are for new and experimental features.Įarly adopters and Mimir developers to gain confidence with new There are strong use cases for altered values. ![]() (experimental) are in the basic category.Īdvanced parameters are ones that few users will change In this reference, any parameters that are not marked as (advanced) or These parameters will generally remain stable for long periods of time, In order to simplify Mimir configuration, we categorize parameters byīasic parameters are ones that we expect the majority of users to modify.Įxamples of basic parameters are object store credentials and : a Prometheus relabeling configuration.: a CLI flag prefix based on the context (look at the parent configuration block to see which CLI flags prefix should be used).: a string containing an absolute or relative path and filename to a file on disk.: a duration matching the regular expression +(ns|us|µs|ms|s|m|h|d|w|y) where y = 365 days.: any integer matching the regular expression +*.: a boolean that can take the values true or false.Passwords are filtered out of this endpoint.īrackets indicate that a parameter is optional. To see the current configuration of any component, The command-line flags take precedence over values in a YAML file. If you specify both the command-line flags and YAML configuration parameters, To specify the YAML file, use the -config.file command-line option. You can configure Grafana Mimir by using a YAML file or via command-line flags Open source Grafana Mimir configuration parameters ![]()
0 Comments
Leave a Reply. |