dashboard-builder
実行可能な監視ダッシュボードを構築。単にメトリクスを積み重ねるのではなく、健全性ステータス、ボトルネック特定、変更分析、および行動可能な推奨事項に焦点を当てます。
npx skills add affaan-m/everything-claude-code --skill dashboard-builderBefore / After 効果比較
1 组複数のツールを手動で切り替えてログ、メトリクス、トレースを確認するため、イベントの関連付けが難しく、問題発見後に根本原因を特定するのにさらに時間がかかる。
単一のダッシュボードで主要な健全性指標、異常のハイライト、および保留中のアクションを表示し、関連するログとトレースを自動的に関連付け、5分以内に問題を特定できる。
dashboard-builder
Dashboard Builder
Use this when the task is to build a dashboard people can operate from.
The goal is not "show every metric." The goal is to answer:
-
is it healthy?
-
where is the bottleneck?
-
what changed?
-
what action should someone take?
When to Use
-
"Build a Kafka monitoring dashboard"
-
"Create a Grafana dashboard for Elasticsearch"
-
"Make a SigNoz dashboard for this service"
-
"Turn this metrics list into a real operational dashboard"
Guardrails
-
do not start from visual layout; start from operator questions
-
do not include every available metric just because it exists
-
do not mix health, throughput, and resource panels without structure
-
do not ship panels without titles, units, and sane thresholds
Workflow
1. Define the operating questions
Organize around:
-
health / availability
-
latency / performance
-
throughput / volume
-
saturation / resources
-
service-specific risk
2. Study the target platform schema
Inspect existing dashboards first:
-
JSON structure
-
query language
-
variables
-
threshold styling
-
section layout
3. Build the minimum useful board
Recommended structure:
-
overview
-
performance
-
resources
-
service-specific section
4. Cut vanity panels
Every panel should answer a real question. If it does not, remove it.
Example Panel Sets
Elasticsearch
-
cluster health
-
shard allocation
-
search latency
-
indexing rate
-
JVM heap / GC
Kafka
-
broker count
-
under-replicated partitions
-
messages in / out
-
consumer lag
-
disk and network pressure
API gateway / ingress
-
request rate
-
p50 / p95 / p99 latency
-
error rate
-
upstream health
-
active connections
Quality Checklist
-
valid dashboard JSON
-
clear section grouping
-
titles and units are present
-
thresholds/status colors are meaningful
-
variables exist for common filters
-
default time range and refresh are sensible
-
no vanity panels with no operator value
Related Skills
-
research-ops -
backend-patterns -
terminal-ops
Weekly Installs509Repositoryaffaan-m/everyt…ude-codeGitHub Stars156.2KFirst Seen9 days agoSecurity AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex478opencode463gemini-cli460github-copilot459amp459cline459
ユーザーレビュー (0)
レビューを書く
レビューなし
統計データ
ユーザー評価
この Skill を評価