grafana-dashboards

Publish and review Grafana dashboards as version-controlled assets with stable UIDs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Grafana dashboards are frequently created and edited in isolation, resulting in drift between rendered assets and source truth, difficult reviews, and inconsistent governance across environments.

Core Features & Use Cases

  • Author and review Grafana dashboards as version-controlled assets or mixin-generated configurations.
  • Preserve stable UIDs, explicit datasources, and consistent panel structures for cross-environment reliability.
  • Support source-vs-rendered handoff, reference documentation, and review workflows to streamline maintenance.

Quick Start

Create or review a Grafana dashboard asset with a stable uid and explicit datasource references in your repo.

Frequently Asked Questions about grafana-dashboards

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

FAQPage Schema
How do I manage Grafana dashboard drift and review JSON changes across environments?

Manage Grafana dashboard drift by publishing dashboards as version-controlled JSON assets with stable UIDs and explicit datasources. This enforces consistent panel structures and enables structured review workflows to maintain cross-environment reliability.

How do I version control Grafana mixin generated dashboards?

Version control Grafana mixin generated dashboards by treating them as deliberate assets with stable UIDs. The process preserves explicit datasources, panel types, and layout decisions, ensuring consistent structure and lifecycle governance across rendered environments.

Why do my Grafana dashboards lose their datasource references when imported to a new environment?

Grafana dashboards lose datasource references due to inconsistent governance. Using version-controlled assets with explicit datasource references and stable UIDs prevents this drift, ensuring reliable rendering across different environments.

Can I review Grafana dashboard JSON changes before deploying to production?

Yes, you can review Grafana dashboard JSON changes before deployment. The system supports source-vs-rendered handoff and structured review workflows, streamlining maintenance by enforcing explicit time ranges, datasource references, and panel layouts.

What is the best way to maintain stable UIDs for Grafana dashboards in source control?

The best way to maintain stable UIDs is authoring dashboards directly as version-controlled assets. This enforces consistent structure, explicit datasources, and lifecycle governance, preventing UID drift when deploying across multiple environments.