The Grafana back-end has a number of configuration options that can be specified in a .ini configuration file or specified using environment variables.

Note. Grafana needs to be restarted for any configuration changes to take effect.

Comments In .ini Files

Semicolons (the ; char) are the standard way to comment out lines in a .ini file.

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.

Config file locations

  • 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

Note. If you have installed Grafana using the deb or rpm packages, then your configuration file is located at /etc/grafana/grafana.ini. This path is specified in the Grafana init.d script using --config file parameter.

Using environment variables

All options in the configuration file (listed below) can be overridden using environment variables using the syntax:


Where the section name is the text within the brackets. Everything should be upper case, . should be replaced by _. For example, given these configuration settings:

# default section
instance_name = ${HOSTNAME}

admin_user = admin

client_secret = 0ldS3cretKey

Then you can override them using:

export GF_DEFAULT_INSTANCE_NAME=my-instance


Set the name of the grafana-server instance. Used in logging and internal metrics and in 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.



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.


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.


Path to where Grafana will store logs. This path is usually specified via command line in the init.d script or the systemd service file. It can be overridden in the configuration file or in the default environment variable file.


Directory where grafana will automatically scan and look for plugins


Folder that contains provisioning config files that grafana will apply on startup. Dashboards will be reloaded when the json files changes



The IP address to bind to. If empty will bind to all interfaces


The port to bind to, defaults to 3000. To use port 80 you need to either give the Grafana binary permission for example:

$ sudo setcap 'cap_net_bind_service=+ep' /usr/sbin/grafana-server

Or redirect port 80 to the Grafana port using:

$ 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.


http,https,h2 or socket

Note Grafana versions earlier than 3.0 are vulnerable to POODLE. So we strongly recommend to upgrade to 3.x or use a reverse proxy for ssl termination.


Path where the socket should be created when protocol=socket. Please make sure that Grafana has appropriate permissions.


This setting is only used in as a part of the root_url setting (see below). Important if you use GitHub or Google OAuth.


Redirect to correct domain if host header does not match domain. Prevents DNS rebinding attacks. Default is false.


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.


Available in 6.3 and above

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 will be accessible on http://localhost:3000/grafana.


The path to the directory where the front end files (HTML, JS, and CSS files). Default to public which is why the Grafana binary needs to be executed with working directory set to the installation path.


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.


Path to the certificate file (if protocol is set to https or h2).


Path to the certificate key file (if protocol is set to https or h2).


Set to true for Grafana to log all HTTP requests (not just errors). These are logged as Info level events to grafana log.


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).


Use either URL or the other fields below to configure the database Example: mysql://user:secret@host:port/database


Either mysql, postgres or sqlite3, it’s your choice.


Only applicable for sqlite3 database. The file path where the database will be stored.


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 = or with Unix sockets: host = /var/run/mysqld/mysqld.sock


The name of the Grafana database. Leave it set to grafana or some other name.


The database user (not applicable for sqlite3).


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;"""


For Postgres, use either disable, require or verify-full. For MySQL, use either true, false, or skip-verify.


The path to the CA certificate to use. On many Linux systems, certs can be found in /etc/ssl/certs.


The path to the client key. Only if server requires client authentication.


The path to the client cert. Only if server requires client authentication.


The common name field of the certificate used by the mysql or postgres server. Not necessary if ssl_mode is set to skip-verify.


The maximum number of connections in the idle connection pool.


The maximum number of open connections to the database.


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 variable.


Set to true to log the sql calls and execution times.


For “sqlite3” only. Shared cache setting used for connecting to the database. (private, shared) Defaults to private.



Either redis, memcached or database. Defaults to database


The remote cache connection string. The format depends on the type of the remote cache.


Leave empty when using database since it will use the primary database.


Example connstr: addr=,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 indentifer 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.


Example connstr:



The name of the default Grafana admin user (who has full permissions). Defaults to admin.


The password of the default Grafana admin. Set once on first-run. Defaults to admin.


The number of days the keep me logged in / remember me cookie lasts.


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.


Set to true to disable the use of Gravatar for user profile images. Default is false.


Define a white list of allowed ips/domains to use in data sources. Format: ip_or_domain:port separated by spaces.

Set to true if you host Grafana behind HTTPS. Default is false.

Sets the SameSite cookie attribute and prevents the browser from sending this cookie along with cross-site requests. The main goal is mitigate the risk of cross-origin information leakage. It also provides some protection against cross-site request forgery attacks (CSRF), read more here. Valid values are lax, strict and none. Default is lax.


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 <frame>, <iframe>, <embed> or <object>. The main goal is to mitigate the risk of Clickjacking. Default is false.


Set to true if you want to enable HTTP Strict-Transport-Security (HSTS) response header. This is only sent when HTTPS is enabled in this configuration. HSTS tells browsers that the site should only be accessed using HTTPS. The default value is false until the next minor release, 6.3.


Sets how long a browser should cache HSTS in seconds. Only applied if strict_transport_security is enabled. The default value is 86400.


Set to true if to enable HSTS preloading option. Only applied if strict_transport_security is enabled. The default value is false.


Set to true if to enable the HSTS includeSubDomains option. Only applied if strict_transport_security is enabled. The default value is false.


Set to true to enable the X-Content-Type-Options response header. The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the MIME types advertised in the Content-Type headers should not be changed and be followed. The default value is false until the next minor release, 6.3.


Set to false to disable the X-XSS-Protection header, which tells browsers to stop pages from loading when they detect reflected cross-site scripting (XSS) attacks. The default value is false until the next minor release, 6.3.



Set to false to prohibit users from being able to sign up / create user accounts. Defaults to false. The admin user can still create users from the Grafana Admin Pages


Set to false to prohibit users from creating new organizations. Defaults to false.


Set to true to automatically add new users to the main organization (id 1). When set to false, new users will automatically cause a new organization to be created for that new user.


Set this value to automatically add new users to the provided org. This requires auto_assign_org to be set to true. Please make sure that this organization does already exists.


The role new users will be assigned for the main organization (if the above setting is set to true). Defaults to Viewer, other valid options are Admin and Editor. e.g. :

auto_assign_org_role = Viewer


Viewers can edit/inspect dashboard settings in the browser, but not save the dashboard. Defaults to false.


Editors can administrate dashboards, folders and teams they create. Defaults to false.


Text used as placeholder text on login page for login/username input.


Text used as placeholder text on login page for password input.


Grafana provides many ways to authenticate users. The docs for authentication has been split in to many different pages below.



This enables data proxy logging, default is false.


How long the data proxy should wait before timing out. Default is 30 (seconds)


If enabled and user is not anonymous, data proxy will add X-Grafana-User header with username into the request. Default is false.



When enabled Grafana will send anonymous usage statistics to 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.


If you want to track Grafana usage via Google analytics specify your Universal Analytics ID here. By default this feature is disabled.


Set to false to disable all checks to 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.



Number dashboard versions to keep (per dashboard). Default: 20, Minimum: 1.


This have been replaced with dashboards provisioning in 5.0+


true or false. Is disabled by default.


The full path to a directory containing your json dashboards.


Email server settings.


defaults to false


defaults to localhost:25


In case of SMTP auth, defaults to empty


In case of SMTP auth, defaults to empty


File path to a cert file, defaults to empty


File path to a key file, defaults to empty


Verify SSL for smtp server? defaults to false


Address used when sending out emails, defaults to admin@grafana.localhost


Name to be used when sending out emails, defaults to Grafana


Name to be used as client identity for EHLO in SMTP dialog, defaults to instance_name.



Either “console”, “file”, “syslog”. Default is “console” and “file”. Use spaces to separate multiple modes, e.g. console file


Either “debug”, “info”, “warn”, “error”, “critical”, default is info


optional settings to set different levels for specific loggers. For example filters = sqlstore:debug



Enable metrics reporting. defaults true. Available via HTTP API /metrics.


If set configures the username to use for basic authentication on the metrics endpoint.


If set configures the password to use for basic authentication on the metrics endpoint.


If set to true, then total stats generation (stat_totals_* metrics) is disabled. The default is false.


Flush/Write interval when sending metrics to external TSDB. Defaults to 10s.


Include this section if you want to send internal Grafana metrics to Graphite.


Format <Hostname or ip>:port


Graphite metric prefix. Defaults to prod.grafana.%(instance_name)s.



Set to false to disable external snapshot publish endpoint (default true)


Set root URL to a Grafana instance where you want to publish external snapshots (defaults to


Set name for external snapshot button. Defaults to Publish to


Enabled to automatically remove expired snapshots


These options control how images should be made public so they can be shared on services like slack.


You can choose between (s3, webdav, gcs, azure_blob, local). If left empty Grafana will ignore the upload action.



Bucket name for S3. e.g. grafana.snapshot


Region name for S3. e.g. ‘us-east-1’, ‘cn-north-1’, etc


Optional extra path inside bucket, useful to apply expiration policies


(for backward compatibility, only works when no bucket or region are configured) Bucket URL for S3. AWS region can be specified within URL or defaults to ‘us-east-1’, e.g. - -



Access key requires permissions to the S3 bucket for the ‘s3:PutObject’ and ‘s3:PutObjectAcl’ actions.





Url to where Grafana will send PUT request with images


Optional parameter. Url to send to users in notifications. If the string contains the sequence ${file}, it will be replaced with the uploaded filename. Otherwise, the file name will be appended to the path part of the url, leaving any query string unchanged.


basic auth username


basic auth password



Path to JSON key file associated with a Google service account to authenticate and authorize. Service Account keys can be created and downloaded from

Service Account should have “Storage Object Writer” role. The access control model of the bucket needs to be “Set object-level and bucket-level permissions”. Grafana itself will make the images public readable.


Bucket Name on Google Cloud Storage.


Optional extra path inside bucket



Storage account name


Storage account key


Container name where to store “Blob” images with random names. Creating the blob container beforehand is required. Only public containers are supported.



Defaults to true. Set to false to disable alerting engine and hide Alerting from UI.


Makes it possible to turn off alert rule execution.


Available in 5.3 and above

Default setting for new alert rules. Defaults to categorize error and timeouts as alerting. (alerting, keep_state)


Available in 5.3 and above

Default setting for how Grafana handles nodata or null values in alerting. (alerting, no_data, keep_state, ok)


Available in 5.3 and above

Alert notifications can include images, but rendering many images at the same time can overload the server. This limit will protect the server from render overloading and make sure notifications are sent out quickly. Default value is 5.


Default setting for alert calculation timeout. Default value is 30


Default setting for alert notification timeout. Default value is 30


Default setting for max attempts to sending alert notifications. Default value is 3


Options to configure a remote HTTP image rendering service, e.g. using


URL to a remote HTTP image renderer service, e.g. http://localhost:8081/render, will enable Grafana to render panels and dashboards to PNG-images using HTTP requests to an external service.


If the remote HTTP image renderer service runs on a different server than the Grafana server you may have to configure this to a URL where Grafana is reachable, e.g. http://grafana.domain/.



If set to true Grafana will allow script tags in text panels. Not recommended as it enable XSS vulnerabilities. Default is false. This settings was introduced in Grafana v6.0.



Set to true if you want to test alpha plugins that are not yet ready for general usage.



Keys of alpha features to enable, separated by space. Available alpha features are: transformations

Removed options

Please note that these options have been removed.


Removed starting from Grafana v6.2. Please use remote_cache option instead.


Valid values are memory, file, mysql, postgres, memcache or redis. Default is file.


This option should be configured differently depending on what type of session provider you have configured.

  • file: session file path, e.g. data/sessions
  • mysql: go-sql-driver/mysql dsn config string, e.g. user:password@tcp(
  • postgres: ex: user=a password=b host=localhost port=5432 dbname=c sslmode=verify-full
  • memcache: ex:
  • redis: ex: addr=,pool_size=100,prefix=grafana. For Unix socket, use for example: network=unix,addr=/var/run/redis/redis.sock,pool_size=100,db=grafana

Postgres valid sslmode are disable, require, verify-ca, and verify-full (default).

The name of the Grafana session cookie.

Set to true if you host Grafana behind HTTPS only. Defaults to false.


How long sessions lasts in seconds. Defaults to 86400 (24 hours).