Grafana Dashboard Authoring
- Inspect dashboard JSON, folder, datasource UIDs, and panel IDs first.
- Keep dashboard and panel request bodies in project-local JSON files. Use
dashboards create/updatefor whole documents andpanels create/update/delete/copy/movefor focused changes. - Preserve variables, datasource references, transformations, field configuration, links, and version/resource metadata unless the user explicitly changes them.
- Use
panels query <dashboard-uid> <panel-id>with a bounded time range to validate targets after edits. - Read the dashboard back and verify panel placement and IDs.
Grafana 12+ /apis/dashboard.grafana.app/v1beta1 documents use metadata and spec; legacy documents use dashboard and meta. The CLI preserves the detected representation. Never fall back from /apis after 401/403. All authoring and live query operations require confirmation.