Provision resources and sync dasards

Using Provisioning, you can configure how to store your dasard JSON files in either repositories using Git Sync or a local path.

Of the two experimental options, Git Sync is the recommended method for provisioning your dasards. You can synchronize any new dasards and changes to existing dasards to your configured repository. If you push a change in the repository, those changes are mirrored in your Grafana instance. For more information on configuring Git Sync, refer to Set up Git Sync.

Refer to Set up file provisioning to learn more about the version of local file provisioning in Grafana 12.

Provisioned folders and connections

Dasards and folders saved to the local path are referred to as “provisioned” resources and are labeled as such in the Grafana UI.

Dasards saved in your repository or local folder configured appear in a provisioned folder in Grafana.

You can set a single folder, or multiple folders to a different repository, with up to 10 connections. Alternatively, your entire Grafana instance can be the provisioned folder.

How it works

A user decides to update a provisioned dasard that is either stored within a repository (Git Sync workflow) or in a local file (local file workflow).

Git Sync workflow

Resources provisioned with Git Sync can be modified from within the Grafana UI or within the repository. Changes made in either the repository or the Grafana UI are bidirectional.

For example, when a user updates dasards within the Grafana UI, they choose Save to preserve the changes. Grafana notifies them that the dasard is provisioned in a repository. They choose how to preserve their changes: either saved directly to a branch or pushed to a new branch using a pull request in . If they chose a new branch, then they open the pull request and follow their normal workflow.

Grafana polls at a regular interval. The connection is established using a personal access token for authorization. With the webhooks feature enabled, repository notifications appear almost immediately. Without webhooks, Grafana polls for changes at the specified interval. The default polling interval is 60 seconds.

Any changes made in the provisioned files stored in the repository are reflected in the Grafana database. The Grafana UI reads the database and updates the UI to reflect these changes.

Local file workflow

In the local file workflow, all provisioned resources are changed in the local files. The user can’t use the Grafana UI to edit or delete provisioned resources.

Any changes made in the provisioned files are reflected in the Grafana database. The Grafana UI reads the database and updates the UI to reflect these changes.

Explore provisioning

• Git Sync
  Learn about Git Sync, the Grafana feature for storing and managing dasards within repositories.
• Set up Git Sync
  Instructions for setting up Git Sync, so you can provision repositories for use with Grafana.
• Set up file provisioning
  Instructions for setting up file provisioning with a local path.
• Work with provisioned dasards
  Update, save, and modify provisioned resources in Grafana using Git Sync.
• Manage provisioned repositories with Git Sync
  Instructions for working with Git Sync to perform common tasks, such as saving dasards to and synchronizing changes with Grafana.