build-grafana-dashboards

Solid

Create production-ready Grafana dashboards with reusable panels, template variables, annotations, and provisioning for version-controlled dashboard deployment. Use when creating visual representations of Prometheus, Loki, or other data source metrics, building operational dashboards for SRE teams, migrating from manual dashboard creation to version-controlled provisioning, or establishing executive-level SLO compliance reporting.

Data & Documents 26 stars 4 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
48
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Build Grafana Dashboards Design and deploy Grafana dashboards with best practices for maintainability, reusability, and version control. ## When to Use - Creating visual representations of Prometheus, Loki, or other data source metrics - Building operational dashboards for SRE teams and incident responders - Establishing executive-level reporting dashboards for SLO compliance - Migrating dashboards from manual creation to version-controlled provisioning - Standardizing dashboard layouts across teams with template variables - Creating drill-down experiences from high-level overviews to detailed metrics ## Inputs - **Required**: Data source configuration (Prometheus, Loki, Tempo, etc.) - **Required**: Metrics or logs to visualize with their query patterns - **Optional**: Template variables for multi-service or multi-environment views - **Optional**: Existing dashboard JSON for migration or modification - **Optional**: Annotation queries for event correlation (deployments, incidents) ## Procedure > See [Extended Examples](references/EXAMPLES.md) for complete configuration files and templates. ### Step 1: Design Dashboard Structure Plan dashboard layout and organization before building panels. Create a dashboard specification document: ```markdown # Service Overview Dashboard ## Purpose Real-time operational view for on-call engineers monitoring the API service. ## Rows 1. High-Level Metrics (collapsed by default) - Request rate, error rate, latency (RED metric...

Details

Author
pjt222
Repository
pjt222/agent-almanac
Created
1 years ago
Last Updated
today
Language
R
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

grafana-architect

Grafana dashboards + alerts — dashboards-as-code (Grizzly), per-service folders, one-question-per-panel, unified alerting with runbooks, low-cardinality discipline. Use when designing dashboards, writing alert rules, or auditing.

2 Updated 4 days ago
ralvarezdev
AI & Automation Listed

grafana-dashboard

Spec a Grafana dashboard — rows, panels, PromQL/LogQL, variables, on-call layout. No API provision.

7 Updated 4 days ago
KhaiTrang1995
AI & Automation Listed

grafana-best-practice

Review, improve, organize, deploy, and verify Grafana dashboards, provisioned alert rules, and the Telegraf→InfluxDB→Grafana monitoring stack. Use when working on Grafana dashboards, dashboard folders, tags, legends, panel readability, Flux/InfluxDB query correctness or performance, Prometheus/Telegraf dimensions, Telegraf JSON/HTTP scraping, anonymous access, dashboard/alert provisioning, Grafana Docker deployments, high CPU or memory caused by dashboard queries, provisioned alert rules and Flux alert conditions, contact points and Telegram/notification delivery, or requests like "review this dashboard", "optimize Grafana panels", "why is this dashboard slow / using CPU", "fix legends", "move dashboards into a folder", "add tags", "set up Grafana alerting", "alert won't fire / won't deliver", "fix Telegram alerts", "route alerts to a Telegram topic/thread (message_thread_id)", "bump/upgrade the Grafana version", "deploy and verify dashboards", or "Grafana best practices".

85 Updated yesterday
wquguru