grafana

Operate, configure, and troubleshoot Grafana OSS, Enterprise, and Cloud environments.

40|6|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/magnus919/agent-skills --skill grafana-magnus919
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grafana
Source: https://github.com/magnus919/agent-skills/tree/main/grafana
Command: npx skills add https://github.com/magnus919/agent-skills --skill grafana-magnus919

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the common disconnect between Grafana dashboard health and actual system reliability by providing a discovery-first workflow that validates query semantics, alert routing, and provisioning ownership.

Core Features & Use Cases

  • Dashboard Engineering: Design and review dashboards based on proven observability models like RED and USE, ensuring queries are semantically correct and actionable.
  • Alerting & Routing: Trace alert paths from rule evaluation through policy trees to final notification delivery, preventing silent failures.
  • Provisioning & GitOps: Reconcile ownership between UI, file-based, and Terraform-managed resources to eliminate configuration drift and duplicate providers.

Quick Start

Use the grafana skill to discover the version, edition, and deployment owner of your target instance before planning any configuration changes.

Frequently Asked Questions about grafana

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

FAQPage Schema
How do I troubleshoot Grafana alerting rules to prevent silent notification failures?

Troubleshoot Grafana alerting by tracing alert paths from rule evaluation through policy trees to final notification delivery. This discovery-first workflow validates query semantics and routing configurations to prevent silent failures and ensure reliable observability pipelines.

What is the best way to reconcile Grafana provisioning between Terraform, file-based, and UI configurations?

Reconcile Grafana provisioning by mapping ownership between UI, file-based, and Terraform-managed resources. This GitOps approach eliminates configuration drift and duplicate providers, ensuring consistent dashboard and alert management across your observability infrastructure.

How do I design Grafana dashboards using RED and USE observability models?

Design Grafana dashboards using RED and USE models by validating that queries are semantically correct and actionable. This dashboard engineering approach ensures your visualizations align with proven observability patterns for monitoring system reliability.

Does this Grafana workflow support both OSS and Enterprise Cloud environments?

Yes, the workflow supports Grafana OSS, Enterprise, and Cloud environments through structured discovery and validation. It applies version-aware API selection and least-privilege credential handling to operate, configure, and troubleshoot across all editions securely.

Why should I discover the Grafana instance version before making API configuration changes?

Discovering the Grafana instance version before configuration changes ensures version-aware API selection and least-privilege credential handling. This security-conscious approach prevents API incompatibility errors and validates deployment ownership before applying any modifications.

What causes configuration drift in Grafana GitOps workflows and how do I fix it?

Configuration drift in Grafana GitOps workflows occurs when UI, file-based, and Terraform-managed resources conflict. Fix it by reconciling ownership between these provisioning sources to eliminate duplicate providers and ensure consistent observability pipeline configurations.