grafana-dashboard▌
aj-geddes/useful-ai-prompts · updated Apr 8, 2026
Design and implement comprehensive Grafana dashboards with multiple visualization types, variables, and drill-down capabilities for operational monitoring.
Grafana Dashboard
Table of Contents
Overview
Design and implement comprehensive Grafana dashboards with multiple visualization types, variables, and drill-down capabilities for operational monitoring.
When to Use
- Creating monitoring dashboards
- Building operational insights
- Visualizing time-series data
- Creating drill-down dashboards
- Sharing metrics with stakeholders
Quick Start
Minimal working example:
{
"dashboard": {
"title": "Application Performance",
"description": "Real-time application metrics",
"tags": ["production", "performance"],
"timezone": "UTC",
"refresh": "30s",
"templating": {
"list": [
{
"name": "datasource",
"type": "datasource",
"datasource": "prometheus"
},
{
"name": "service",
"type": "query",
"datasource": "prometheus",
"query": "label_values(requests_total, service)"
}
]
},
"panels": [
{
"id": 1,
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Grafana Dashboard JSON | Grafana Dashboard JSON |
| Grafana Provisioning Configuration | Grafana Provisioning Configuration |
| Grafana Alert Configuration | Grafana Alert Configuration |
| Grafana API Client | Grafana API Client |
| Docker Compose Setup | Docker Compose Setup |
Best Practices
✅ DO
- Use meaningful dashboard titles
- Add documentation panels
- Implement row-based organization
- Use variables for flexibility
- Set appropriate refresh intervals
- Include runbook links in alerts
- Test alerts before deploying
- Use consistent color schemes
- Version control dashboard JSON
❌ DON'T
- Overload dashboards with too many panels
- Mix different time ranges without justification
- Create without runbooks
- Ignore alert noise
- Use inconsistent metric naming
- Set refresh too frequently
- Forget to configure datasources
- Leave default passwords
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★30 reviews- ★★★★★Shikha Mishra· Dec 8, 2024
We added grafana-dashboard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Noah Gupta· Dec 8, 2024
grafana-dashboard is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ganesh Mohane· Dec 4, 2024
Registry listing for grafana-dashboard matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Yash Thakker· Nov 27, 2024
grafana-dashboard fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Benjamin Nasser· Nov 27, 2024
Solid pick for teams standardizing on skills: grafana-dashboard is focused, and the summary matches what you get after install.
- ★★★★★Aarav Srinivasan· Nov 3, 2024
Registry listing for grafana-dashboard matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sophia Diallo· Oct 22, 2024
Keeps context tight: grafana-dashboard is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Oct 18, 2024
grafana-dashboard is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Benjamin Ndlovu· Oct 18, 2024
We added grafana-dashboard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Sep 25, 2024
grafana-dashboard reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 30