Known limitations

Git Sync has certain limitations you should be aware of when planning your dashboard management workflow. Understanding these constraints helps you design effective processes and avoid unexpected behavior.

Current limitations

Be aware of the following limitations when using Git Sync:

Synced resources

  • You can only sync dashboards and folders. Refer to Supported resources for more information.
  • If you’re using Git Sync in Grafana OSS and Grafana Enterprise, some resources might be in an incompatible data format and won’t be synced.
  • Full-instance sync is not available in Grafana Cloud and is experimental in Grafana OSS and Grafana Enterprise.
  • If you want to manage existing resources with Git Sync, you need to save them as JSON files and commit them to the synced repository. Use grafanactl or open a PR to import, copy, move, or save a dashboard. Refer to Export non-provisioned resources from Grafana for more details.
  • Restoring resources from the UI is currently not possible. As an alternative, you can restore dashboards directly in your GitHub repository by raising a PR, and they will be updated in Grafana.
  • You cannot modify the permissions of a provisioned folder after you’ve synced it.

For detailed information about usage limits and quotas, refer to the Git Sync usage limitations documentation.

In the next milestone, you’ll navigate to the Git Sync interface in Grafana Cloud.

More to explore (optional)

At this point in your journey, you can explore the following paths:

Git Sync usage limitations


page 5 of 9