--- title: "Provision Grafana | Grafana documentation" description: "Describes provisioning settings for Grafana using configuration files." --- # Provision Grafana Grafana has an active provisioning system that uses configuration files. You can define data sources and dashboards using files that can be version controlled, making GitOps more natural. > Note > > For advanced as code options such as Infrastructure as code, Git Sync or on-prem file provisioning refer to [Deploy, configure and provision Grafana with as-code workflows](/docs/grafana/latest/as-code/). ## Configuration file Refer to [Configuration](/docs/grafana/latest/setup-grafana/configure-grafana/) for more information on what you can configure in `grafana.ini`. ### Configuration file locations Grafana reads its default configuration from `/conf/defaults.ini`. Grafana reads custom configuration from `/conf/custom.ini`. You can override the custom configuration path with the `--config` option. > Note > > The Deb and RPM packages install the configuration file at `/etc/grafana/grafana.ini`. The Grafana init.d script sets the `--config` option to that path. ## Use environment variables You can use environment variable lookups in all provisioning configuration. The syntax for an environment variable is `$ENV_VAR_NAME` or `${ENV_VAR_NAME}`. The following applies: - Only use environment variables for configuration values. Do not use it for keys or bigger parts of the configuration file structure. - Use environment variables in dashboard provisioning configuration, but not in the dashboard definition files themselves. The following example looks up the data source URL port, user, and password using environment variables: YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml datasources: - name: Graphite url: http://localhost:$PORT user: $USER secureJsonData: password: $PASSWORD ``` ### Use of the special character `$` Grafana’s provisioning system considers any set of characters after an `$` a variable name. During the replacement process, Grafana: 1. Replaces the variables that use the syntax `${ENV_VAR_NAME}`. 2. Next, it replaces the variables that use the syntax `$ENV_VAR_NAME`. If your data contains the character `$`, for example `Pa$sw0rd`, and you’re using an environment variable, use the `$ENV_VAR_NAME` syntax to avoid double expansion. If you use the `${ENV_VAR_NAME}` syntax, the value will be first replaced as `Pa$sw0rd` and then again as `Pa` since `$sw0rd` will be considered another variable. If you want to use the literal value `Pa$sw0rd`, you need to escape the character `$` using a double `$$`: `Pa$$sw0rd`. The following example shows how variables are replaced, assuming `PASSWORD=Pa$sw0rd`: YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml datasources: - name: Graphite secureJsonData: password1: $PASSWORD # Resolved as Pa$sw0rd password2: ${PASSWORD} # Resolved as Pa password3: 'Pa$$sw0rd' # Resolved as Pa$sw0rd password4: 'Pa$sw0rd' # Resolved as Pa ``` ## Data sources You can manage data sources in Grafana by adding YAML configuration files in the [`provisioning/datasources`](../../setup-grafana/configure-grafana/#provisioning) directory. Each configuration file contains a list of data sources, under the `datasources` key, to add or update during startup. If the data source already exists, Grafana reconfigures it to match the provisioned configuration file. You can also list data sources to automatically delete, using the key `deleteDatasources`. Grafana deletes the data sources listed in `deleteDatasources` *before* adding or updating those in the `datasources` list. You can configure Grafana to automatically delete provisioned data sources when they’re removed from the provisioning file. To do so, add `prune: true` to the root of your data source provisioning file. With this configuration, Grafana also removes the provisioned data sources if you remove the provisioning file entirely. ### Run multiple Grafana instances If you run multiple instances of Grafana, add a version number to each data source in the configuration and increase it when you update the configuration. Grafana only updates data sources with the same or lower version number than the one set in the configuration file. This prevents old configurations from overwriting newer ones if you have different versions of the `datasource.yaml` file that don’t define version numbers, and then restart instances at the same time. ### Example data source configuration file This example provisions a [Graphite data source](../../datasources/graphite/): YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml # Configuration file version apiVersion: 1 # List of data sources to delete from the database. deleteDatasources: - name: Graphite orgId: 1 # Mark provisioned data sources for deletion if they are no longer in a provisioning file. # It takes no effect if data sources are already listed in the deleteDatasources section. prune: true # List of data sources to insert/update depending on what's # available in the database. datasources: # Sets the name you use to refer to # the data source in panels and queries. - name: Graphite # Sets the data source type. type: graphite # Sets the access mode, either # proxy or direct (Server or Browser in the UI). # Some data sources are incompatible with any setting # but proxy (Server). access: proxy # Sets the organization id. Defaults to orgId 1. orgId: 1 # Sets a custom UID to reference this # data source in other parts of the configuration. # If not specified, Grafana generates one. uid: my_unique_uid # Sets the data source's URL, including the # port. url: http://localhost:8080 # Sets the database user, if necessary. user: # Sets the database name, if necessary. database: # Enables basic authorization. basicAuth: # Sets the basic authorization username. basicAuthUser: # Enables credential headers. withCredentials: # Toggles whether the data source is pre-selected # for new panels. You can set only one default # data source per organization. isDefault: # Fields to convert to JSON and store in jsonData. jsonData: # Defines the Graphite service's version. graphiteVersion: '1.1' # Enables TLS authentication using a client # certificate configured in secureJsonData. tlsAuth: true # Enables TLS authentication using a CA # certificate. tlsAuthWithCACert: true # Fields to encrypt before storing in jsonData. secureJsonData: # Defines the CA cert, client cert, and # client key for encrypted authentication. tlsCACert: '...' tlsClientCert: '...' tlsClientKey: '...' # Sets the database password, if necessary. password: # Sets the basic authorization password. basicAuthPassword: # Sets the version. Used to compare versions when # updating. Ignored when creating a new data source. version: 1 # Allows users to edit data sources from the # Grafana UI. editable: false ``` For provisioning examples of specific data sources, refer to that [data source’s documentation](../../datasources/). #### JSON data Not all data sources have the same configuration settings, only the most common ones are fields in the data source provisioning file. To provision the rest of a data source’s settings, include them as JSON in the `jsonData` field. Common settings in the [built-in core data sources](../../datasources/#built-in-core-data-sources) include: Expand table | Name | Type | Data source | Description | |---------------------------------|---------|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `tlsAuth` | boolean | *HTTP\**, MySQL | Enable TLS authentication using client cert configured in secure JSON data | | `tlsAuthWithCACert` | boolean | *HTTP\**, MySQL, PostgreSQL | Enable TLS authentication using CA cert | | `tlsSkipVerify` | boolean | *HTTP\**, MySQL, PostgreSQL, MSSQL | Controls whether a client verifies the server’s certificate chain and host name. | | `serverName` | string | *HTTP\**, MSSQL | Optional. Controls the server name used for certificate common name/subject alternative name verification. Defaults to using the data source URL. | | `timeout` | string | *HTTP\** | Request timeout in seconds. Overrides `dataproxy.timeout` option | | `graphiteVersion` | string | Graphite | Graphite version | | `timeInterval` | string | Prometheus, Elasticsearch, InfluxDB, MySQL, PostgreSQL and MSSQL | Lowest interval/step value that should be used for this data source. | | `httpMode` | string | InfluxDB | HTTP Method. ‘GET’, ‘POST’, defaults to GET | | `maxSeries` | number | InfluxDB | Max number of series/tables that Grafana processes | | `httpMethod` | string | Prometheus | HTTP Method. ‘GET’, ‘POST’, defaults to POST | | `customQueryParameters` | string | Prometheus | Query parameters to add, as a URL-encoded string. | | `manageAlerts` | boolean | Prometheus and Loki | Manage alerts via Alerting UI | | `alertmanagerUid` | string | Prometheus and Loki | UID of Alertmanager that manages Alert for this data source. | | `timeField` | string | Elasticsearch | Which field that should be used as timestamp | | `interval` | string | Elasticsearch | Index date time format. nil(No Pattern), ‘Hourly’, ‘Daily’, ‘Weekly’, ‘Monthly’ or ‘Yearly’ | | `logMessageField` | string | Elasticsearch | Which field should be used as the log message | | `logLevelField` | string | Elasticsearch | Which field should be used to indicate the priority of the log message | | `maxConcurrentShardRequests` | number | Elasticsearch | Maximum number of concurrent shard requests that each sub-search request executes per node | | `sigV4Auth` | boolean | Elasticsearch and Prometheus | Enable usage of SigV4 | | `sigV4AuthType` | string | Elasticsearch and Prometheus | SigV4 auth provider. default/credentials/keys | | `sigV4ExternalId` | string | Elasticsearch and Prometheus | Optional SigV4 External ID | | `sigV4AssumeRoleArn` | string | Elasticsearch and Prometheus | Optional SigV4 ARN role to assume | | `sigV4Region` | string | Elasticsearch and Prometheus | SigV4 AWS region | | `sigV4Profile` | string | Elasticsearch and Prometheus | Optional SigV4 credentials profile | | `authType` | string | Amazon CloudWatch | Auth provider. default/credentials/keys | | `externalId` | string | Amazon CloudWatch | Optional External ID | | `assumeRoleArn` | string | Amazon CloudWatch | Optional ARN role to assume | | `defaultRegion` | string | Amazon CloudWatch | Optional default AWS region | | `customMetricsNamespaces` | string | Amazon CloudWatch | Namespaces of Custom Metrics | | `profile` | string | Amazon CloudWatch | Optional credentials profile | | `tsdbVersion` | string | OpenTSDB | Version | | `tsdbResolution` | string | OpenTSDB | Resolution | | `sslmode` | string | PostgreSQL | SSL mode. ‘disable’, ‘require’, ‘verify-ca’ or ‘verify-full’ | | `tlsConfigurationMethod` | string | PostgreSQL | SSL certificate configuration, either by ‘file-path’ or ‘file-content’ | | `sslRootCertFile` | string | PostgreSQL, MSSQL | SSL server root certificate file, must be readable by the Grafana user | | `sslCertFile` | string | PostgreSQL | SSL client certificate file, must be readable by the Grafana user | | `sslKeyFile` | string | PostgreSQL | SSL client key file, must be readable by *only* the Grafana user | | `encrypt` | string | MSSQL | Determines SSL encryption handling. Options include: `disable` - data sent between client and server is not encrypted; `false` - data sent between client and server is not encrypted beyond the login packet; `true` - data sent between client and server is encrypted. Default is `false`. | | `postgresVersion` | number | PostgreSQL | Postgres version as a number (903/904/905/906/1000) meaning v9.3, v9.4, …, v10 | | `timescaledb` | boolean | PostgreSQL | Enable usage of TimescaleDB extension | | `maxOpenConns` | number | MySQL, PostgreSQL and MSSQL | Maximum number of open connections to the database (Grafana v5.4+) | | `maxIdleConns` | number | MySQL, PostgreSQL and MSSQL | Maximum number of connections in the idle connection pool (Grafana v5.4+) | | `connMaxLifetime` | number | MySQL, PostgreSQL and MSSQL | Maximum amount of time in seconds a connection may be reused (Grafana v5.4+) | | `keepCookies` | array | *HTTP\** | Cookies that needs to be passed along while communicating with data sources | | `prometheusVersion` | string | Prometheus | The version of the Prometheus data source, such as `2.37.0`, `2.24.0` | | `prometheusType` | string | Prometheus | Prometheus database type. Options are `Prometheus`, `Cortex`, `Mimir` or`Thanos`. | | `cacheLevel` | string | Prometheus | Determines the duration of the browser cache. Valid values include: `Low`, `Medium`, `High`, and `None`. | | `incrementalQuerying` | string | Prometheus | Experimental: Turn on incremental querying to enhance dashboard reload performance with slow data sources | | `incrementalQueryOverlapWindow` | string | Prometheus | Experimental: Configure incremental query overlap window. Requires a valid duration string, for example, `180s` or `15m` Default value is `10m` (10 minutes). | | `disableRecordingRules` | boolean | Prometheus | Experimental: Turn off Prometheus recording rules | | `seriesEndpoint` | boolean | Prometheus | Using Prometheus `/api/v1/series` endpoint | | `implementation` | string | Alertmanager | The implementation of the Alertmanager data source, such as `prometheus`, `cortex` or `mimir` | | `handleGrafanaManagedAlerts` | boolean | Alertmanager | When enabled, Grafana-managed alerts are sent to this Alertmanager | > Note > > Data sources tagged with *HTTP\** communicate using the HTTP protocol, which includes all core data source plugins except MySQL, PostgreSQL, and MSSQL. For examples of specific data sources’ JSON data, refer to that [data source’s documentation](../../datasources/). #### Secure JSON data Secure JSON data is a map of settings encrypted with a [secret key](../../setup-grafana/configure-grafana/#secret_key). The encryption hides the JSON data from the users of Grafana. You should use secure JSON data to store TLS certificates and passwords for data source HTTP requests. All of these settings are optional. Expand table | Name | Type | Data source | Description | |---------------------|--------|------------------------------------|----------------------------------------------------------| | `tlsCACert` | string | *HTTP\**, MySQL, PostgreSQL | CA cert for out going requests | | `tlsClientCert` | string | *HTTP\**, MySQL, PostgreSQL | TLS Client cert for outgoing requests | | `tlsClientKey` | string | *HTTP\**, MySQL, PostgreSQL | TLS Client key for outgoing requests | | `password` | string | *HTTP\**, MySQL, PostgreSQL, MSSQL | password | | `basicAuthPassword` | string | *HTTP\** | password for basic authentication | | `accessKey` | string | Amazon CloudWatch | Access key for connecting to Amazon CloudWatch | | `secretKey` | string | Amazon CloudWatch | Secret key for connecting to Amazon CloudWatch | | `sigV4AccessKey` | string | Elasticsearch and Prometheus | SigV4 access key. Required when using keys auth provider | | `sigV4SecretKey` | string | Elasticsearch and Prometheus | SigV4 secret key. Required when using keys auth provider | > Note > > The *HTTP\** tag denotes data sources that communicate using the HTTP protocol, including all core data source plugins except MySQL, PostgreSQL, and MSSQL. #### Custom HTTP headers for data sources You can add HTTP headers to all requests sent to data sources managed by Grafana provisioning Configure the header name in the `jsonData` field and the header value in `secureJsonData`. The following example sets the `HeaderName` header to have the value `HeaderValue` and the `Authorization` header to have the value `Bearer XXXXXXXXX`: YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 datasources: - name: Graphite jsonData: httpHeaderName1: 'HeaderName' httpHeaderName2: 'Authorization' secureJsonData: httpHeaderValue1: 'HeaderValue' httpHeaderValue2: 'Bearer XXXXXXXXX' ``` ## Plugins You can manage plugin applications in Grafana by adding one or more YAML configuration files in the [`provisioning/plugins`](../../setup-grafana/configure-grafana/#provisioning) directory. Each configuration file contains a list of `apps` that Grafana configures during start up. Grafana configures each app to use the configuration in the file. > Note > > This feature enables you to provision plugin configurations, not the plugins themselves. You must have already installed the plugin to use plugin configuration provisioning. ### Example plugin configuration file YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 apps: # the type of app, plugin identifier. Required - type: raintank-worldping-app # Org ID. Default to 1, unless org_name is specified org_id: 1 # Org name. Overrides org_id unless org_id not specified org_name: Main Org. # disable the app. Default to false. disabled: false # fields that will be converted to json and stored in jsonData. Custom per app. jsonData: # key/value pairs of string to object key: value # fields that will be converted to json, encrypted and stored in secureJsonData. Custom per app. secureJsonData: # key/value pairs of string to string key: value ``` ## Dashboards You can manage dashboards in Grafana by adding one or more YAML configuration files in the [`provisioning/dashboards`](../../setup-grafana/configure-grafana/#dashboards) directory. Each configuration file contains a list of `providers` that Grafana uses to load dashboards from the local filesystem. ### Example dashboard configuration file YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 providers: # an unique provider name. Required - name: 'a unique provider name' # Org id. Default to 1 orgId: 1 # name of the dashboard folder. folder: '' # folder UID. will be automatically generated if not specified folderUid: '' # provider type. Default to 'file' type: file # disable dashboard deletion disableDeletion: false # how often Grafana will scan for changed dashboards updateIntervalSeconds: 10 # allow updating provisioned dashboards from the UI allowUiUpdates: false options: # path to dashboard files on disk. Required when using the 'file' type path: /var/lib/grafana/dashboards # use folder names from filesystem to create folders in Grafana foldersFromFilesStructure: true ``` When Grafana starts, it updates or creates all dashboards found in the configured path. These files can define the dashboard using the dashboard JSON: JSON ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```json { "dashboard": { "id": null, "uid": "example-dashboard", "title": "Production Overview", "tags": ["production", "monitoring"], "timezone": "browser", "schemaVersion": 16, "version": 0, "refresh": "30s" }, "folderUid": "monitoring-folder", "overwrite": true } ``` Or using a Kubernetes format, for example `kubernetes-dashboard.json`: JSON ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```json { "kind": "Dashboard", "apiVersion": "dashboard.grafana.app/v1", "metadata": { "name": "dashboard-uid" }, "spec": { "title": "Dashboard title", "panels": [ { "gridPos": { "h": 13, "w": 24, "x": 0, "y": 0 }, "options": { "content": "

Example panel

", "mode": "html" }, "transparent": true, "type": "text" } ] } } ``` You *must* use the Kubernetes resource format to provision dashboards v2 / dynamic dashboards. > Note > > Grafana installs dashboards at the root level if you don’t set the `folder` field. #### Detect updates to provisioned dashboards files After Grafana provisions your dashboards, it checks the filesystem for changes and updates dashboards as needed. The mechanism Grafana uses to do this depends on your `updateIntervalSeconds` value: - **More than 10 seconds**: Grafana polls the path at that interval. - **10 seconds or less**: Grafana watches the filesystem for changes and updates dashboards when it detects them. > Note > > When `updateIntervalSeconds` is 10 or less, Grafana relies on filesystem watch events to detect changes. Depending on your filesystem and how you mount or sync dashboard files (for example, Docker bind mounts or some network filesystems), those events might not reach Grafana. To work around this, set `updateIntervalSeconds` to more than 10 to force polling, or update your setup so filesystem watch events are propagated. #### Make changes to a provisioned dashboard You can make changes to a provisioned dashboard in the Grafana UI but its not possible to automatically save the changes back to the provisioning source. If `allowUiUpdates` is set to `true` and you make changes to a provisioned dashboard, when you save the dashboard, Grafana persists the changes to its database. > Caution > > If you save a provisioned dashboard in the UI and then later update the provisioning source, Grafana always overwrites the database dashboard with the one from the provisioning file. Grafana ignores the `version` property in the JSON file, even if it’s lower than the dashboard in the database. > Caution > > If you save a provisioned dashboard in the UI and remove the provisioning source, Grafana deletes the dashboard in the database unless you have set the option `disableDeletion` to `true`. If you set `allowUiUpdates` to `false`, you can’t save changes to a provisioned dashboard. When you try to save changes to a provisioned dashboard, Grafana brings up a *Cannot save provisioned dashboard* dialog box. Grafana offers options to export the JSON definition of a dashboard. To export the dashboard JSON definition, follow these steps: 1. Upon save, click **Advanced options** to expand the section, and then make the following selections: - **Model**: Choose from **Classic** or **V2 Resource**. Choose **Classic** if you plan to use the dashboard in Grafana v12.4 or older. - **Format**: For the V2 Resource only, choose from **JSON** or **YAML** 2. Click either **Copy JSON to Clipboard** or **Save JSON to file**. The following screenshot illustrates this behavior. [](/static/img/docs/v51/provisioning_cannot_save_dashboard.png) Grafana removes the `id` field from the dashboard JSON to help the provisioning workflow. Now you sync your dashboard changes back to the provisioning source. ### Reusable dashboard URLs If the dashboard in the JSON file contains an [UID](../../dashboards/build-dashboards/view-dashboard-json-model/), Grafana updates that the dashboard with that UID in the database. This lets you migrate dashboards between Grafana instances and keep consistent dashboard URLs. When Grafana starts, it creates or updates all dashboards available in the configured folders. > Caution > > You can overwrite existing dashboards with provisioning. > > Be careful not to reuse the same `title` multiple times within a folder or `uid` within the same Grafana instance to avoid inconsistent behavior. ### Provision folders structure from filesystem to Grafana If you already store your dashboards using folders in a Git repository or on a filesystem, and want to have the same folder names in the Grafana menu, use `foldersFromFilesStructure` option. For example, to replicate the following dashboards structure from the filesystem to Grafana: ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```none /etc/dashboards ├── /server │ ├── /common_dashboard.json │ └── /network_dashboard.json └── /application ├── /requests_dashboard.json └── /resources_dashboard.json ``` use the following provisioning configuration file: YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 providers: - name: dashboards type: file updateIntervalSeconds: 30 options: path: /etc/dashboards foldersFromFilesStructure: true ``` Grafana creates the `server` and `application` folders in the UI. To use `foldersFromFilesStructure`, you must unset the `folder` and `folderUid` options. To provision dashboards to the root level, store them in the root of your `path`. > Note > > This feature doesn’t let you create nested folder structures, where you have folders within folders. ## Alerting For information on provisioning Grafana Alerting, refer to [Provision Grafana Alerting resources](../../alerting/set-up/provision-alerting-resources/). ### Supported settings The following sections detail the supported settings and secure settings for each alert notification type. In the provisioning YAML use `settings` for settings and `secure_settings` for secure settings. Grafana encrypts secure settings in the database. #### Alert notification `pushover` Expand table | Name | Secure setting | |--------------|----------------| | `apiToken` | yes | | `userKey` | yes | | `device` | | | `priority` | | | `okPriority` | | | `retry` | | | `expire` | | | `sound` | | | `okSound` | | #### Alert notification `discord` Expand table | Name | Secure setting | |------------------------|----------------| | `url` | yes | | `avatar_url` | | | `content` | | | `use_discord_username` | | #### Alert notification `slack` Expand table | Name | Secure setting | |------------------|----------------| | `url` | yes | | `recipient` | | | `username` | | | `icon_emoji` | | | `icon_url` | | | `uploadImage` | | | `mentionUsers` | | | `mentionGroups` | | | `mentionChannel` | | | `token` | yes | | `color` | | #### Alert notification `victorops` Expand table | Name | |---------------| | `url` | | `autoResolve` | #### Alert notification `kafka` Expand table | Name | |------------------| | `kafkaRestProxy` | | `kafkaTopic` | #### Alert notification `LINE` Expand table | Name | Secure setting | |---------|----------------| | `token` | yes | #### Alert notification `MQTT` Expand table | Name | Secure setting | |-----------------|----------------| | `brokerUrl` | | | `clientId` | | | `topic` | | | `messageFormat` | | | `username` | | | `password` | yes | | `retain` | | | `qos` | | | `tlsConfig` | | ##### TLS configuration Expand table | Name | Secure setting | |----------------------|----------------| | `insecureSkipVerify` | | | `clientCertificate` | yes | | `clientKey` | yes | | `caCertificate` | yes | #### Alert notification `pagerduty` Expand table | Name | Secure setting | |------------------|----------------| | `integrationKey` | yes | | `autoResolve` | | #### Alert notification `sensu` Expand table | Name | Secure setting | |------------|----------------| | `url` | | | `source` | | | `handler` | | | `username` | | | `password` | yes | #### Alert notification `sensugo` Expand table | Name | Secure setting | |-------------|----------------| | `url` | | | `apikey` | yes | | `entity` | | | `check` | | | `handler` | | | `namespace` | | #### Alert notification `prometheus-alertmanager` Expand table | Name | Secure setting | |---------------------|----------------| | `url` | | | `basicAuthUser` | | | `basicAuthPassword` | yes | #### Alert notification `teams` Expand table | Name | Secure setting | |-------|----------------| | `url` | | #### Alert notification `dingding` Expand table | Name | Secure setting | |-------|----------------| | `url` | | #### Alert notification `email` Expand table | Name | Secure setting | |---------------|----------------| | `singleEmail` | | | `addresses` | | #### Alert notification `opsgenie` Expand table | Name | Secure setting | |--------------------|----------------| | `apiKey` | yes | | `apiUrl` | | | `autoClose` | | | `overridePriority` | | | `sendTagsAs` | | #### Alert notification `telegram` Expand table | Name | Secure setting | |---------------|----------------| | `bottoken` | yes | | `chatid` | | | `uploadImage` | | #### Alert notification `threema` Expand table | Name | Secure setting | |----------------|----------------| | `gateway_id` | | | `recipient_id` | | | `api_secret` | yes | #### Alert notification `webhook` Expand table | Name | Secure setting | |---------------|----------------| | `url` | | | `http_method` | | | `username` | | | `password` | yes | | `tls_config` | | | `hmac_config` | | ##### TLS configuration Expand table | Name | Secure setting | |----------------------|----------------| | `insecureSkipVerify` | | | `clientCertificate` | yes | | `clientKey` | yes | | `caCertificate` | yes | ##### HMAC signature configuration Expand table | Name | Secure setting | |-------------------|----------------| | `secret` | yes | | `header` | | | `timestampHeader` | | #### Alert notification `googlechat` Expand table | Name | Secure setting | |-------|----------------| | `url` | | #### Alert notification `Cisco Webex Teams` Expand table | Name | Secure setting | |-------------|----------------| | `message` | | | `room_id` | | | `api_url` | | | `bot_token` | yes | ## Grafana Enterprise Grafana Enterprise supports: - [Provisioning role-based access control with Grafana](../roles-and-permissions/access-control/rbac-grafana-provisioning/) - [Provisioning role-based access control with Terraform](../roles-and-permissions/access-control/rbac-terraform-provisioning/) ## Configuration management tools The Grafana community maintains libraries for many popular configuration management tools. Expand table | Tool | Project | |---------|-----------------------------------------------------------------------------------------------------------------------------------| | Puppet | [https://forge.puppet.com/puppet/grafana](https://forge.puppet.com/puppet/grafana) | | Ansible | [https://github.com/grafana/grafana-ansible-collection](https://github.com/grafana/grafana-ansible-collection) | | Chef | [https://github.com/sous-chefs/chef-grafana](https://github.com/sous-chefs/chef-grafana) | | NixOS | [`services.grafana.provision` module](https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/monitoring/grafana.nix) |