+++ title = "Configuration" description = "Configuration documentation" keywords = ["grafana", "configuration", "documentation"] type = "docs" aliases = ["/docs/grafana/latest/installation/configuration/"] [menu.docs] name = "Configuration" identifier = "config" parent = "admin" weight = 1 +++ # Configuration Grafana has a number of configuration options that you can specify in a `.ini` configuration file or specified using environment variables. > **Note:** You must restart Grafana for any configuration changes to take effect. ## Config file locations _Do not_ change `defaults.ini`! Grafana defaults are stored in this file. Depending on your OS, make all configuration changes in either `custom.ini` or `grafana.ini`. - Default configuration from `$WORKING_DIR/conf/defaults.ini` - Custom configuration from `$WORKING_DIR/conf/custom.ini` - The custom configuration file path can be overridden using the `--config` parameter ### Linux If you installed Grafana using the `deb` or `rpm` packages, then your configuration file is located at `/etc/grafana/grafana.ini` and a separate `custom.ini` is not used. This path is specified in the Grafana init.d script using `--config` file parameter. ### Docker Refer to [Configure a Grafana Docker image]({{< relref "../installation/configure-docker.md" >}}) for information about environmental variables, persistent storage, and building custom Docker images. ### Windows `sample.ini` is in the same directory as `defaults.ini` and contains all the settings commented out. Copy `sample.ini` and name it `custom.ini`. ### macOS By default, the configuration file is located at `/usr/local/etc/grafana/grafana.ini`. To configure Grafana, add a configuration file named `custom.ini` to the `conf` folder to override any of the settings defined in `conf/defaults.ini`. ## Comments in .ini Files Semicolons (the `;` char) are the standard way to comment out lines in a `.ini` file. If you want to change a setting, you must delete the semicolon (`;`) in front of the setting before it will work. **Example** ``` # The HTTP port to use ;http_port = 3000 ``` A common problem is forgetting to uncomment a line in the `custom.ini` (or `grafana.ini`) file which causes the configuration option to be ignored. ## Configure with environment variables All options in the configuration file can be overridden using environment variables using the syntax: ```bash GF__ ``` Where the section name is the text within the brackets. Everything should be uppercase, `.` and `-` should be replaced by `_`. For example, if you have these configuration settings: ```bash # default section instance_name = ${HOSTNAME} [security] admin_user = admin [auth.google] client_secret = 0ldS3cretKey [plugin.grafana-image-renderer] rendering_ignore_https_errors = true ``` You can override them on Linux machines with: ```bash export GF_DEFAULT_INSTANCE_NAME=my-instance export GF_SECURITY_ADMIN_USER=owner export GF_AUTH_GOOGLE_CLIENT_SECRET=newS3cretKey export GF_PLUGIN_GRAFANA_IMAGE_RENDERER_RENDERING_IGNORE_HTTPS_ERRORS=true ``` ## Variable expansion > Only available in Grafana 7.1+. > For any changes to `conf/grafana.ini` (or corresponding environment variables) to take effect, you must restart Grafana. If any of your options contains the expression `$__{}` or `${}`, then they will be processed by Grafana's variable expander. The expander runs the provider with the provided argument to get the final value of the option. There are three providers: `env`, `file`, and `vault`. ### Env provider The `env` provider can be used to expand an environment variable. If you set an option to `$__env{PORT}` the `PORT` environment variable will be used in its place. For environment variables you can also use the short-hand syntax `${PORT}`. Grafana's log directory would be set to the `grafana` directory in the directory behind the `LOGDIR` environment variable in the following example. ```ini [paths] logs = $__env{LOGDIR}/grafana ``` ### File provider `file` reads a file from the filesystem. It trims whitespace from the beginning and the end of files. The database password in the following example would be replaced by the content of the `/etc/secrets/gf_sql_password` file: ```ini [database] password = $__file{/etc/secrets/gf_sql_password} ``` ### Vault provider The `vault` provider allows you to manage your secrets with [Hashicorp Vault](https://www.hashicorp.com/products/vault). > Vault provider is only available in Grafana Enterprise v7.1+. For more information, refer to [Vault integration]({{< relref "../enterprise/vault.md" >}}) in [Grafana Enterprise]({{< relref "../enterprise" >}}).
## app_mode Options are `production` and `development`. Default is `production`. _Do not_ change this option unless you are working on Grafana development. ## instance_name Set the name of the grafana-server instance. Used in logging, internal metrics, and clustering info. Defaults to: `${HOSTNAME}`, which will be replaced with environment variable `HOSTNAME`, if that is empty or does not exist Grafana will try to use system calls to get the machine name.
## [paths] ### data Path to where Grafana stores the sqlite3 database (if used), file-based sessions (if used), and other data. This path is usually specified via command line in the init.d script or the systemd service file. **macOS:** The default SQLite database is located at `/usr/local/var/lib/grafana` ### temp_data_lifetime How long temporary images in `data` directory should be kept. Defaults to: `24h`. Supported modifiers: `h` (hours), `m` (minutes), for example: `168h`, `30m`, `10h30m`. Use `0` to never clean up temporary files. ### logs Path to where Grafana stores logs. This path is usually specified via command line in the init.d script or the systemd service file. You can override it in the configuration file or in the default environment variable file. However, please note that by overriding this the default log path will be used temporarily until Grafana has fully initialized/started. Override log path using the command line argument `cfg:default.paths.log`: ```bash ./grafana-server --config /custom/config.ini --homepath /custom/homepath cfg:default.paths.logs=/custom/path ``` **macOS:** By default, the log file should be located at `/usr/local/var/log/grafana/grafana.log`. ### plugins Directory where Grafana automatically scans and looks for plugins. Manually or automatically install any plugins here. **macOS:** By default, the Mac plugin location is: `/usr/local/var/lib/grafana/plugins`. ### provisioning Folder that contains [provisioning]({{< relref "provisioning.md" >}}) config files that grafana will apply on startup. Dashboards will be reloaded when the json files changes
## [server] ### protocol `http`,`https`,`h2` or `socket` > **Note:** Grafana versions earlier than 3.0 are vulnerable to [POODLE](https://en.wikipedia.org/wiki/POODLE). So we strongly recommend to upgrade to 3.x or use a reverse proxy for SSL termination. ### http_addr The IP address to bind to. If empty will bind to all interfaces ### http_port The port to bind to, defaults to `3000`. To use port 80 you need to either give the Grafana binary permission for example: ```bash $ sudo setcap 'cap_net_bind_service=+ep' /usr/sbin/grafana-server ``` Or redirect port 80 to the Grafana port using: ```bash $ sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 3000 ``` Another way is put a webserver like Nginx or Apache in front of Grafana and have them proxy requests to Grafana. ### domain This setting is only used in as a part of the `root_url` setting (see below). Important if you use GitHub or Google OAuth. ### enforce_domain Redirect to correct domain if host header does not match domain. Prevents DNS rebinding attacks. Default is `false`. ### root_url This is the full URL used to access Grafana from a web browser. This is important if you use Google or GitHub OAuth authentication (for the callback URL to be correct). > **Note:** This setting is also important if you have a reverse proxy > in front of Grafana that exposes it through a subpath. In that > case add the subpath to the end of this URL setting. ### serve_from_sub_path > Available in Grafana 6.3+. Serve Grafana from subpath specified in `root_url` setting. By default it is set to `false` for compatibility reasons. By enabling this setting and using a subpath in `root_url` above, e.g. `root_url = http://localhost:3000/grafana`, Grafana is accessible on `http://localhost:3000/grafana`. ### router_logging Set to `true` for Grafana to log all HTTP requests (not just errors). These are logged as Info level events to the Grafana log. ### static_root_path The path to the directory where the front end files (HTML, JS, and CSS files). Defaults to `public` which is why the Grafana binary needs to be executed with working directory set to the installation path. ### enable_gzip Set this option to `true` to enable HTTP compression, this can improve transfer speed and bandwidth utilization. It is recommended that most users set it to `true`. By default it is set to `false` for compatibility reasons. ### cert_file Path to the certificate file (if `protocol` is set to `https` or `h2`). ### cert_key Path to the certificate key file (if `protocol` is set to `https` or `h2`). ### socket Path where the socket should be created when `protocol=socket`. Make sure that Grafana has appropriate permissions before you change this setting.
## [database] Grafana needs a database to store users and dashboards (and other things). By default it is configured to use `sqlite3` which is an embedded database (included in the main Grafana binary). ### type Either `mysql`, `postgres` or `sqlite3`, it's your choice. ### host Only applicable to MySQL or Postgres. Includes IP or hostname and port or in case of Unix sockets the path to it. For example, for MySQL running on the same host as Grafana: `host = 127.0.0.1:3306` or with Unix sockets: `host = /var/run/mysqld/mysqld.sock` ### name The name of the Grafana database. Leave it set to `grafana` or some other name. ### user The database user (not applicable for `sqlite3`). ### password The database user's password (not applicable for `sqlite3`). If the password contains `#` or `;` you have to wrap it with triple quotes. For example `"""#password;"""` ### url Use either URL or the other fields below to configure the database Example: `mysql://user:secret@host:port/database` ### max_idle_conn The maximum number of connections in the idle connection pool. ### max_open_conn The maximum number of open connections to the database. ### conn_max_lifetime Sets the maximum amount of time a connection may be reused. The default is 14400 (which means 14400 seconds or 4 hours). For MySQL, this setting should be shorter than the [`wait_timeout`](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_wait_timeout) variable. ### log_queries Set to `true` to log the sql calls and execution times. ### ssl_mode For Postgres, use either `disable`, `require` or `verify-full`. For MySQL, use either `true`, `false`, or `skip-verify`. ### ca_cert_path The path to the CA certificate to use. On many Linux systems, certs can be found in `/etc/ssl/certs`. ### client_key_path The path to the client key. Only if server requires client authentication. ### client_cert_path The path to the client cert. Only if server requires client authentication. ### server_cert_name The common name field of the certificate used by the `mysql` or `postgres` server. Not necessary if `ssl_mode` is set to `skip-verify`. ### path Only applicable for `sqlite3` database. The file path where the database will be stored. ### cache_mode For "sqlite3" only. [Shared cache](https://www.sqlite.org/sharedcache.html) setting used for connecting to the database. (private, shared) Defaults to `private`.
## [remote_cache] ### type Either `redis`, `memcached`, or `database`. Defaults to `database` ### connstr The remote cache connection string. The format depends on the `type` of the remote cache. Options are `database`, `redis`, and `memcache`. #### database Leave empty when using `database` since it will use the primary database. #### redis Example connstr: `addr=127.0.0.1:6379,pool_size=100,db=0,ssl=false` - `addr` is the host `:` port of the redis server. - `pool_size` (optional) is the number of underlying connections that can be made to redis. - `db` (optional) is the number identifier of the redis database you want to use. - `ssl` (optional) is if SSL should be used to connect to redis server. The value may be `true`, `false`, or `insecure`. Setting the value to `insecure` skips verification of the certificate chain and hostname when making the connection. #### memcache Example connstr: `127.0.0.1:11211`
## [dataproxy] ### logging This enables data proxy logging, default is `false`. ### timeout How long the data proxy should wait before timing out. Default is 30 seconds. This setting also applies to core backend HTTP data sources where query requests use an HTTP client with timeout set. ### send_user_header If enabled and user is not anonymous, data proxy will add X-Grafana-User header with username into the request. Default is `false`.
## [analytics] ### reporting_enabled When enabled Grafana will send anonymous usage statistics to `stats.grafana.org`. No IP addresses are being tracked, only simple counters to track running instances, versions, dashboard and error counts. It is very helpful to us, so please leave this enabled. Counters are sent every 24 hours. Default value is `true`. ### check_for_updates Set to false to disable all checks to https://grafana.com for new versions of installed plugins and to the Grafana GitHub repository to check for a newer version of Grafana. The version information is used in some UI views to notify that a new Grafana update or a plugin update exists. This option does not cause any auto updates, nor send any sensitive information. The check is run every 10 minutes. ### google_analytics_ua_id If you want to track Grafana usage via Google analytics specify _your_ Universal Analytics ID here. By default this feature is disabled. ### google_tag_manager_id Google Tag Manager ID, only enabled if you enter an ID here.
## [security] ### disable_initial_admin_creation > Only available in Grafana v6.5+. Disable creation of admin user on first start of Grafana. Default is `false`. ### admin_user The name of the default Grafana Admin user, who has full permissions. Default is `admin`. ### admin_password The password of the default Grafana Admin. Set once on first-run. Default is `admin`. ### secret_key Used for signing some data source settings like secrets and passwords, the encryption format used is AES-256 in CFB mode. Cannot be changed without requiring an update to data source settings to re-encode them. ### disable_gravatar Set to `true` to disable the use of Gravatar for user profile images. Default is `false`. ### data_source_proxy_whitelist Define a whitelist of allowed IP addresses or domains, with ports, to be used in data source URLs with the Grafana data source proxy. Format: `ip_or_domain:port` separated by spaces. PostgreSQL, MySQL, and MSSQL data sources do not use the proxy and are therefore unaffected by this setting. ### disable_brute_force_login_protection Set to `true` to disable [brute force login protection](https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#account-lockout). Default is `false`. ### cookie_secure Set to `true` if you host Grafana behind HTTPS. Default is `false`. ### cookie_samesite Sets the `SameSite` cookie attribute and prevents the browser from sending this cookie along with cross-site requests. The main goal is to mitigate the risk of cross-origin information leakage. This setting also provides some protection against cross-site request forgery attacks (CSRF), [read more about SameSite here](https://www.owasp.org/index.php/SameSite). Valid values are `lax`, `strict`, `none`, and `disabled`. Default is `lax`. Using value `disabled` does not add any `SameSite` attribute to cookies. ### allow_embedding When `false`, the HTTP header `X-Frame-Options: deny` will be set in Grafana HTTP responses which will instruct browsers to not allow rendering Grafana in a ``, `