Grafana dashboard provisioning failed: JSON model invalid error on startup fix

TL;DR

Read the provisioning error in the Grafana server log first, because it names the file and the parse problem. Fix the JSON syntax or the schema mismatch in that file, such as a dashboard exported from a newer Grafana version or a file with a wrapper object the provider does not accept, and restart or wait for the provider rescan. Provisioning is strict, one invalid file can block its whole provider folder.

Grafana dashboard provisioning failed: JSON model invalid error on startup fix

Use this when

• Provisioned dashboards are missing after a restart, upgrade, or a Git sync of dashboard files.
• The Grafana server log shows a provisioning error naming a dashboard file.
• Dashboards created in the interface on the same instance work normally.

Not for this skill when

• A single interface created dashboard fails to load. That is a dashboard content issue, not provisioning.
• The data sources provisioned from the same system also failed. Check the provisioning configuration root first.

Steps

1. Search the Grafana server log for provisioning errors and record the file name and message for the first failure. Verify: the log names one file and one concrete parse or validation problem
2. Validate that file with a JSON parser to separate a pure syntax error from a schema problem. Verify: the file either fails parsing at a known position or parses cleanly
3. If the file carries the export wrapper, extract the inner dashboard object, and if the schema version is newer than the instance, downgrade or upgrade deliberately. Verify: the file top level is the dashboard model itself with a supported schema version
4. Check the provider configuration for the folder path, the folder name, and update behaviour so the loader reads the corrected file. Verify: the provider points at the folder that actually contains the file
5. Restart Grafana or wait for the rescan interval, then watch the log for a clean provisioning pass. Verify: the log shows the dashboard provisioned without an error
6. Open the provisioned dashboard in the interface and confirm it renders and carries the expected update behaviour for edits. Verify: the dashboard appears in its folder and panels load

Why it happens

Provisioning treats dashboards as code, so it inherits code discipline problems, hand edited JSON, version skew between instances, and export formats pasted into source files. Validating dashboard files in the same pipeline that ships them, with a JSON check and a schema version matched to the target Grafana, makes provisioning failures a build error instead of a startup surprise.

File provisioning loads dashboards from disk at startup and on a rescan interval. The loader validates each JSON model before saving it, and rejects files with syntax errors, unknown schema versions, or the export wrapper format that includes extra top level keys. Because the failure happens outside the interface, the instance looks healthy while the provisioned folders stay empty, and only the server log explains why.

Field notes for Grafana specifically. The server log at startup and the provisioning and alerting sections are where instance level truth lives, and the dashboard JSON model view in the interface shows exactly what Grafana stored, which settles most arguments about what a panel is really querying. Grafana changes behaviour across versions in the alerting and provisioning areas especially, so record the version in every incident note. Instances managed as code should treat the Git copy of a dashboard as the source to fix, with interface edits treated as drafts to be ported back.

A Grafana habit that prevents repeat incidents is to keep one small health dashboard for the monitoring system itself, showing data source query success, alert evaluation state, and provisioning status. Monitoring the monitor sounds recursive, but the failures in this family are silent by nature, empty variables, unevaluated rules, missing dashboards, and a health view is the only surface where silence itself becomes visible. Checking it after every upgrade, migration, or provisioning change catches the breakage in the same hour it was introduced.

Variants and edge cases

Grafana provisioning failed invalid dashboard JSON startup

The startup phrasing matching the log symptom.

Grafana provisioned dashboard missing exported wrapper JSON

The wrapper variant for files saved from the share export dialog.

Grafana dashboard schema version too new provisioning error

The version skew variant between instances.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CfS8taqJlL07aVui6aJOFg