dashboard-provisioning

Provision Grafana dashboards as code via provider YAML with drift control.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ririnto/sinon --skill dashboard-provisioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dashboard-provisioning
Source: https://github.com/ririnto/sinon/tree/main/plugins/observability-assets/skills/dashboard-provisioning
Command: npx skills add https://github.com/ririnto/sinon --skill dashboard-provisioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Grafana dashboards are often edited in the UI or drift from version-controlled sources; this skill enables provisioning dashboards as code via provider YAML, with drift control and built-in guidance for reviewable folder layouts and predictable delete behavior.

Core Features & Use Cases

  • Provision dashboards as code via provider YAML
  • Manage folder structures and drift between source files and Grafana UI state
  • Deliver reviewable dashboard configurations and clear provisioning boundaries

Quick Start

Define a Grafana provider YAML that points to your dashboards directory, place the dashboard JSON under the configured path, and commit the changes to version control.

Frequently Asked Questions about dashboard-provisioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision Grafana dashboards as code?

Grafana dashboard drift occurs when UI edits overwrite version-controlled configurations. This skill enforces code-driven provisioning via provider YAML to keep source files synchronized with Grafana UI state across environments.

How do I manage Grafana dashboard folder structures using YAML?

Grafana folder structures are managed in YAML by specifying either a fixed folder or foldersFromFilesStructure in the provider configuration, creating predictable, reviewable dashboard layouts organized by environment.

Can I use environment variable substitution in Grafana provisioning YAML?

Environment-variable substitution is supported in provisioning YAML, but configurations must strictly follow the specified substitution rules to ensure dashboards deploy correctly across different environments without errors.

What is the best way to prevent dashboard drift between source files and Grafana UI?

The best way to prevent dashboard drift is provisioning dashboards as code via provider YAML with drift control, which keeps version-controlled source files synchronized with the live Grafana UI state and enforces clear provisioning boundaries.

Why are my Grafana dashboards not syncing with the configured path?

Grafana dashboards fail to sync when the provider options.path does not correctly point to the dashboards directory, or when the provider YAML lacks a valid fixed folder or foldersFromFilesStructure designation.