Grafana Provisioning load order constraint for datasources and dashboards

Direct Answer

Grafana processes datasource provisioning before dashboard provisioning during startup and config reload, at least through v9.4. This order is deterministic in the source code. If a dashboard references a datasource that has not yet been registered, the dashboard loads but displays a "Data source not found" error until the datasource appears, at which point Grafana retries and clears the error automatically. There is no documented mechanism to apply datasource and dashboard changes as a single atomic transaction.

Confirmed Behavior (v6.0–v9.4)

• The provisioning loader iterates datasource YAML files first, then dashboard JSON files.
• A dashboard that references a missing datasource is not rejected; it is stored and marked with an unavailable-datasource state.
• When the datasource is subsequently provisioned (same reload or a later one), the dashboard picks it up on the next reconciliation cycle.

What This Means for Zero-Downtime Cutover

During a reload, viewers may see a brief "Data source not found" banner on affected dashboards. The window is typically seconds, but it is not guaranteed to be invisible. If true zero-downtime is required, you must orchestrate the change outside Grafana (e.g., blue/green instances or a proxy that swaps after both sets are healthy).

Verification Steps

1. Enable debug logging: set logs.level=debug and provisioning.logger=debug in grafana.ini.
2. Restart Grafana and watch the log for Loading datasource from … lines appearing before Loading dashboard from ….
3. Create a dashboard JSON referencing a datasource name that does not exist in any datasources.yaml. Reload. The dashboard appears with the error banner.
4. Add the missing datasource via its provisioning file, trigger a reload (or touch the provisioning directory), and confirm the banner clears and data renders.

Version Assumption & Uncertainty

The load-order guarantee is confirmed in the Grafana source tree up to v9.4. Behavior in versions <6.0 or in future releases (v10+) is not guaranteed by documentation. If you are running a version outside the 6.0–9.4 range, the order could differ.

One diagnostic detail needed: What Grafana version are you targeting? If it is v10 or later, the recommendation to rely on the built-in order should be re-verified against that release’s changelog or source.