grafana-architect

Organize Grafana dashboards and alerts as code with Grizzly drift detection.

3|Updated Feb 26, 2026

Search Tags:#dashboards #observability #infrastructure #alerts #grafana #grizzly #dashboards-as-code

Ready to run

npx skills add https://github.com/ralvarezdev/ralvaskills --skill grafana-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grafana-architect
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/infra/grafana-architect
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill grafana-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grafana dashboards and alerts are often edited directly in the UI, causing drift and inconsistencies. This skill provides a dashboards-as-code workflow to enforce a single source of truth and predictable changes across services.

Core Features & Use Cases

Dashboards-as-code workflow with Grizzly for drift detection and automated deployment.
Per-service folder layout ensuring ownership and clean boundaries.
Panel design and alerting guidelines, including SLO dashboards and runbooks.
Data source provisioning and access control aligned to service ownership.

Quick Start

Install Grizzly and configure your Grafana instance, then organize dashboards per service in git and apply changes with grr to maintain drift-free dashboards.

Frequently Asked Questions about grafana-architect

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

FAQPage Schema

How do I manage Grafana dashboards as code to prevent drift?▼

Manage Grafana dashboards as code by organizing them per service in git and applying changes with Grizzly. This enforces a single source of truth, preventing manual UI edits and configuration drift across your services.

What is the best way to structure Grafana folders for multi-service observability?▼

The best way to structure Grafana folders for multi-service observability is using a per-service layout. This ensures clear ownership boundaries and clean separation when provisioning data sources and standardized panel types.

How does Grizzly detect configuration drift in Grafana dashboards?▼

Grizzly detects configuration drift by treating git as the single source of truth for your dashboards and alerts. It automates deployment and identifies any manual UI edits that diverge from your committed dashboard-as-code configurations.

Can I provision Grafana data sources and alerts using a dashboards-as-code workflow?▼

Yes, you can provision Grafana data sources and alerts using a dashboards-as-code workflow. This skill standardizes alert annotations, data sources, and SLO dashboards while aligning access control to service ownership.

Do I need Grizzly to standardize Grafana alerting and panel types across services?▼

You need Grizzly to apply a dashboards-as-code workflow that standardizes panel types and alert annotations. It requires configuration with your Grafana instance to deploy and maintain consistent observability configurations.

Why are my Grafana dashboards inconsistent across multiple services?▼

Grafana dashboards become inconsistent across services when edited directly in the UI, causing configuration drift. Adopting a dashboards-as-code workflow with standardized panel types and per-service folders eliminates these unpredictable changes.