ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Grafana dashboard provisioning is designed to load dashboards from YAML files at startup, but the default behavior still permits modifications through the UI. When a team relies on version-controlled files as the source of truth, the split between the file-based definition and the live database state creates uncertainty about which version is authoritative a
I'm planning a migration of a small Grafana instance (single node, Grafana 10.x assumed) to a new back-end data source endpoint, and the goal is to keep all dashboards queryable throughout the switch with no restart and no visible gap for viewers. Two documented approaches seem viable, and I'm unsure which fits this constraint better. File-based provisioning
Migrating a small application’s monitoring to a config-driven Grafana setup using file provisioning for datasources and dashboards. The goal is a cutover with no visible interruption to viewers and preserved access. Provisioning of dashboards and datasources is documented for config-driven installs. The operational uncertainty is the ordering and atomicity b
