Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/learn-and-build/as-code/git-sync/scenarios/dev-prod.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/learn-and-build/as-code/git-sync/scenarios/dev-prod/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Git Sync for development and production environments
Use separate Grafana instances for development and production. Each syncs with different Git locations to test dashboards before production.
Before you begin, ensure you have the following:
- A Git repository hosted on a compatible Git provider.
- Two Grafana instances, one for development and one for production, that meet the Git Sync setup prerequisites.
Use it for
Use this scenario in the following situations:
- Staged deployments: You need to test dashboard changes before production deployment.
- Change control: You require approvals before dashboards reach production.
- Quality assurance: You verify dashboard functionality in a non-production environment.
- Risk mitigation: You minimize the risk of breaking production dashboards.
Architecture
In this scenario, each instance syncs a different path of the same branch:
┌──────────────────────────────────────────────────────────────┐
│ GitHub Repository │
│ Repository: your-org/grafana-manifests │
│ Branch: main │
│ │
│ grafana-manifests/ │
│ ├── dev/ │
│ │ ├── dashboard-new.json ← Development dashboards │
│ │ └── dashboard-test.json │
│ │ │
│ └── prod/ │
│ ├── dashboard-stable.json ← Production dashboards │
│ └── dashboard-approved.json │
└──────────────────────────────────────────────────────────────┘
↕ ↕
Git Sync (dev/) Git Sync (prod/)
↕ ↕
┌───────────────────────┐ ┌───────────────────────┐
│ Dev Grafana │ │ Prod Grafana │
│ │ │ │
│ Repository: │ │ Repository: │
│ - path: dev/ │ │ - path: prod/ │
│ │ │ │
│ Creates folder: │ │ Creates folder: │
│ "grafana-manifests" │ │ "grafana-manifests" │
└───────────────────────┘ └───────────────────────┘Repository structure
The following examples show how the dashboards appear in Git and in each Grafana instance.
In Git:
your-org/grafana-manifests
├── dev/
│ ├── dashboard-new.json
│ └── dashboard-test.json
└── prod/
├── dashboard-stable.json
└── dashboard-approved.jsonIn Grafana Dashboards view:
Development instance:
Dashboards
└── 📁 grafana-manifests/
├── New Dashboard
└── Test DashboardProduction instance:
Dashboards
└── 📁 grafana-manifests/
├── Stable Dashboard
└── Approved Dashboard- Both instances create a folder titled
grafana-manifests, the display name of each instance’s Repository resource. - Each instance only shows dashboards from its configured path (
dev/orprod/). - Dashboards appear with their titles from the JSON files.
Configuration parameters
Configure each instance with the following parameters.
Development instance:
- Repository:
your-org/grafana-manifests - Branch:
main - Path:
dev/
Production instance:
- Repository:
your-org/grafana-manifests - Branch:
main - Path:
prod/
How it works
Dashboards move from development to production through Git:
- Developers create and modify dashboards in development.
- Git Sync commits changes to
dev/. - You review changes in Git.
- You promote approved dashboards from
dev/toprod/. - Production syncs from
prod/. - Production dashboards update.
Alternative: Use branches
Instead of using different paths, you can configure instances to use different branches.
Development instance:
- Repository:
your-org/grafana-manifests - Branch:
develop - Path:
grafana/
Production instance:
- Repository:
your-org/grafana-manifests - Branch:
main - Path:
grafana/
With this approach:
- Development changes go to the
developbranch. - You use Git merge or pull request workflows to promote changes from
developtomain. - Production automatically syncs from the
mainbranch.
Alternative: Use separate repositories for stricter isolation
For stricter isolation, use completely separate repositories.
Development instance:
- Repository:
your-org/grafana-manifests-dev - Branch:
main - Path:
grafana/
Production instance:
- Repository:
your-org/grafana-manifests-prod - Branch:
main - Path:
grafana/
Learn more
Refer to the following documents to learn more:
Was this page helpful?
Related resources from Grafana Labs


