# This is an experimental feature, this behaviour could # An uncompressed response body larger than this many bytes will cause the # Reloading the configuration will reopen the file. # File to which PromQL queries are logged. # external systems (federation, remote storage, Alertmanager). # The labels to add to any time series or alerts when communicating with # How long until a scrape request times out. # How frequently to scrape targets by default. They also serve as defaults for other configuration sections. The global configuration specifies parameters that are valid in all other configurationĬontexts. The other placeholders are specified separately.
: a valid path in the current working directory.: a boolean that can take the values true or false.Generic placeholders are defined as follows: To specify which configuration file to load, use the -config.file flag.īrackets indicate that a parameter is optional. This will also reload any configured rule files. Sending a HTTP POST request to the /-/reload endpoint (when the -web.enable-lifecycle flag is enabled). Is not well-formed, the changes will not be applied.Ī configuration reload is triggered by sending a SIGHUP to the Prometheus process or Prometheus can reload its configuration at runtime. To view all available command-line flags, run. Locations, amount of data to keep on disk and in memory, etc.), theĬonfiguration file defines everything related to scraping jobs and their The command-line flags configure immutable system parameters (such as storage Prometheus is configured via command-line flags and a configuration file.
0 kommentar(er)
