grafana-dashboard-datasource-uid-mismatch

Grafana dashboards show no data after importing JSON when the datasource UID embedded in the dashboard file does not match the UID Grafana actually assigned. This UID mismatch causes silent binding failures where panels render empty despite correct underlying Prometheus queries.

Fix Grafana panels with no data by inspecting the dashboard JSON datasource references and comparing them against the provisioning YAML UID settings. Pin the correct datasource UID and re-provision safely to ensure the dashboard binds to the Prometheus datasource again.

Grafana provisioning YAML handles immutable datasource records by requiring explicit deleteDatasources entries to remove old bindings before applying new UIDs. This prevents silent failures where panels render empty because datasource references no longer match the newly provisioned records.

Yes, you can troubleshoot Docker-provisioned Grafana stacks after a volume reset by diagnosing whether the datasource UID changed during re-provisioning. This applies to fresh Grafana volumes where dashboards break because embedded JSON datasource references no longer match the newly assigned UIDs.

The best way to pin a Prometheus datasource UID in Grafana dashboard JSON is to explicitly define the UID in your provisioning YAML configuration. This ensures the datasource receives a fixed identifier instead of an auto-generated one, preventing dashboard binding failures across Docker re-provisioning.