grafana-dashboards

Create and manage Grafana dashboards for real-time metric visualization.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yusoofsh/dotfiles --skill grafana-dashboards-yusoofsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grafana-dashboards
Source: https://github.com/yusoofsh/dotfiles/tree/main/home/dot_claude/private_plugins/private_marketplaces/claude-code-workflows/plugins/observability-monitoring/skills/grafana-dashboards
Command: npx skills add https://github.com/yusoofsh/dotfiles --skill grafana-dashboards-yusoofsh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides you in creating effective Grafana dashboards for real-time visualization of system, application, and business metrics, enabling proactive monitoring and faster incident response.

Core Features & Use Cases

  • Dashboard Design Principles: Apply hierarchy of information, RED method (Rate, Errors, Duration), and USE method (Utilization, Saturation, Errors).
  • Panel Types: Utilize graphs, single stats, tables, and heatmaps for diverse data representation.
  • Templating & Variables: Create dynamic dashboards that adapt to different services, environments, or time ranges.
  • Alerting Integration: Configure alerts directly from your dashboards to notify teams of critical issues.
  • Use Case: Build a comprehensive API monitoring dashboard that displays request rates, error percentages, and latency for all microservices, allowing your SRE team to quickly identify and troubleshoot performance bottlenecks.

Quick Start

Use the grafana-dashboards skill to generate a basic Grafana dashboard JSON structure for API monitoring, including panels for request rate and error rate.

Frequently Asked Questions about grafana-dashboards

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

FAQPage Schema
How do I create a Grafana dashboard to monitor application metrics in real time?

Create a Grafana dashboard by configuring data sources (like Prometheus), adding panels for metrics visualization, and applying templated variables for dynamic filtering. Use the dashboard JSON provisioning format to enable real-time metric ingestion and support panel types including Time Series, Stat, Table, and Heatmap for comprehensive system monitoring.

What's the best way to structure dashboards using the RED and USE methods?

The RED method (Rate, Errors, Duration) and USE method (Utilization, Saturation, Errors) are design principles that organize dashboard information hierarchically. Apply RED for service-level metrics like request rates and latency; use USE for infrastructure resources. Structure panels to show these metrics alongside alerting thresholds for proactive incident detection.

Can I use Grafana dashboards with Prometheus metrics and alerting?

Yes. Grafana integrates directly with Prometheus as a data source to visualize metrics, and you can configure alerts within dashboard panels to notify teams when thresholds are breached. Define alert rules at the panel level, set notification channels, and provision alerts via JSON/YAML for production-ready setups.

How do I build templated variables so dashboards adapt across services and environments?

Add templated variables to dashboards using Grafana's variable configuration to create dropdown selectors for services, environments, or time ranges. These variables populate panel queries dynamically, allowing a single dashboard to serve multiple contexts without duplication and reducing management overhead for multi-service monitoring.

What panel types and components should I use for different monitoring scenarios?

Use Time Series panels for metric trends over time, Stat panels for current values and KPIs, Table panels for detailed multi-metric views, and Heatmap panels for distribution analysis. Choose panel types based on your monitoring scenario—API latency uses Time Series, error rates use Stat, and infrastructure utilization uses Heatmap.

Do I need to provision dashboards in JSON or YAML for production use?

Yes. Provision dashboards using JSON or YAML configuration files to ensure consistency, version control, and repeatable deployments across environments. Provisioning eliminates manual dashboard creation, enables Infrastructure-as-Code practices, and supports SLO dashboards and business KPI tracking at scale.