Note: This feature is only available in Loki 2.1+.

Use environment variables in the configuration

If no -config.file argument is specified, Loki will look up the config.yaml in theĬurrent working directory and the config/ subdirectory and try to use that.īrackets indicate that a parameter is optional. The value can be a list of comma separated paths, then the first To specify which configuration file to load, pass the -config.file flag at theĬommand line. Sending a HTTP POST request to the /reload endpoint (when the -server.enable-runtime-reload flag is enabled). Is not well-formed, the changes will not be applied.Ī configuration reload is triggered by sending a SIGHUP to the Promtail process or Promtail can reload its configuration at runtime. That the order of configs reads correctly top to bottom when viewed in Grafana’s Explore. log-config-reverse-order is the flag we run Loki with in all our environments, the config entries are reversed so print-config-stderr is nice when running Loki directly e.g./loki as you can get a quick output of the entire Loki config. Is especially useful in making sure your config files and flags are being read and loaded properly. This config is what Loki will use to run, it can be invaluable for debugging issues related to configuration and This is expected as every option has a default value if it is being used or not. Many values will not be relevant to your install such as storage configs which you are not using and which you did not define, The result is the value for every config object in the Loki config struct, which is very large… Overrides from config file, and second by overrides from flags.

Loki will dump the entire config object it has created from the built-in defaults combined first with If you pass Loki the flag -print-config-stderr or -log-config-reverse-order, (or -print-config-stderr=true) Which contains information on the Loki server and its individual components,ĭepending on which mode Loki is launched in.Ĭonfiguration examples can be found in the Configuration Examples document. Grafana Loki is configured in a YAML file (usually referred to as loki.yaml ) Create a free account to get started, which includes free forever access to 10k metrics, 50GB logs, 50GB traces, 500VUh k6 testing & more. You can use Grafana Cloud to avoid installing, maintaining, and scaling your own instance of Grafana Loki. Open source Grafana Loki configuration parameters

Folder size 2.6