skills.rest
freedom909
freedom909COMMUNITY
Explore all skills by this author →
GitHub

dashboard-builder

Builds operational monitoring dashboards for Grafana and SigNoz from operator questions.

Updated Mar 18, 2026
Search Tags:#monitoring#metrics#dashboard#observability#Grafana#kafka#SigNoz
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill dashboard-builder-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dashboard-builder
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/dashboard-builder
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill dashboard-builder-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often end up with vanity dashboards that display every available metric but fail to answer whether a system is healthy, where the bottleneck is, or what action to take. This Skill structures dashboard creation around real operator questions so the result is a board people can actually operate from. ## Core Features & Use Cases - Question-Driven Design: Organizes panels around health, latency, throughput, saturation, and service-specific risk instead of raw metric dumps. - Platform Schema Awareness: Inspects existing Grafana or SigNoz dashboard JSON, query languages, variables, and threshold styling before building. - Ready-Made Panel Sets: Provides example panel groupings for Elasticsearch, Kafka, and API gateway/ingress monitoring. - Use Case: When asked to "build a Kafka monitoring dashboard," it produces a structured board covering broker count, under-replicated partitions, consumer lag, and disk pressure with meaningful thresholds and units. ## Quick Start Ask the AI to build a Grafana dashboard for your Kafka cluster that answers whether the system is healthy and where bottlenecks are.

Frequently Asked Questions about dashboard-builder

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

FAQPage Schema
How do I build a Grafana dashboard that is actually useful?▼

Start from operator questions rather than visual layout: is the system healthy, where is the bottleneck, what changed, and what action should someone take. Then group panels into overview, performance, resources, and service-specific sections with clear titles, units, and thresholds.

What panels should a Kafka monitoring dashboard include?▼

A Kafka dashboard should include broker count, under-replicated partitions, messages in and out, consumer lag, and disk and network pressure. These panels answer real operational questions about cluster health and throughput rather than displaying every available metric.

Can I use this approach with SigNoz instead of Grafana?▼

Yes, the workflow applies to SigNoz and similar observability platforms. The key step is studying the target platform's dashboard schema first, including its JSON structure, query language, variables, and threshold styling, before building the board.

What metrics belong on an Elasticsearch monitoring dashboard?▼

An Elasticsearch dashboard should cover cluster health, shard allocation, search latency, indexing rate, and JVM heap and garbage collection. Organize these under health, performance, and resource sections so operators can quickly locate problems.

Why should I avoid adding every available metric to a dashboard?▼

Including every metric creates a vanity board that obscures actionable signals. Each panel should answer a specific operator question; panels that do not help someone decide whether the system is healthy or what action to take should be removed.

Related Skills

Explore More Software Engineering Skills→
alti3alti3
7

litestar-metrics

Instrument Litestar applications with OpenTelemetry metrics for Prometheus-compatible export.

Community
Intermediate
abzhawabzhaw

notification-systems

Coordinate multi-channel incident notifications with escalation chains and deduplication.

Community
Intermediate
thomasslobodathomassloboda

observability-troubleshooting

Correlates logs, traces, metrics, and dashboards to identify root causes of incidents.

Community
Intermediate
GRCEngClubGRCEngClub
367

glba-expert

Identify and interpret GLBA regulatory requirements to guide compliance efforts.

Official
Advanced