unknown

Grafana v12 introduces Git Sync, an experimental feature that enables version control for dashboards through bidirectional synchronization with GitHub repositories. This solves the common problem of untracked dashboard changes in production by automatically committing UI edits to Git while maintaining the familiar visual editing experience. The feature allows teams to collaborate on dashboards using standard Git workflows including branches, pull requests, and rollbacks, treating observability assets with the same rigor as application code.

Observability as Code with Grafana Git Sync

The official daily.dev DevOps community. Led by thought leaders and DevOps experts. Join the Squad!

DevOps

Everyone talks about Infrastructure as Code...

But what about Dashboards as Code?

Traditional Grafana dashboard management has the following limitations.

- If you use Terraform, you get dashboards as code, but you lose the Grafana visual editor.
- If you used Grafana UI editor, ou cant easily track who changed what, when, or why.
- backup scripts are not true version control.

Grafana Git Sync eliminates these issues.

Hands-on guide how to use Git Sync with Grafana.

Over to you.

<p>Everyone talks about Infrastructure as Code...

But what about Dashboards as Code?

Traditional Grafana dashboard management has the following limitations.

- If you use Terraform, you get dashboards as code, but you lose the Grafana visual editor.
- If you used Grafana UI editor, ou cant easily track who changed what, when, or why.
- backup scripts are not true version control.

Grafana Git Sync eliminates these issues.

Hands-on guide how to use Git Sync with Grafana.

Over to you.</p>

<p>At first sight, I thought, it wasn’t that useful, because it seemed like it only saves the GUI changes. However, it is actually bi-directional, so you can still edit it delcaratively. Nice!</p>
