首页/数据分析/dashboard-builder
D

dashboard-builder

by @affaan-mv
4.4(6)

构建可操作监控仪表板,聚焦健康状态、瓶颈定位、变更分析和行动建议,而非堆砌指标

data-visualizationmonitoringdashboarddata-analysisGitHub
安装方式
npx skills add affaan-m/everything-claude-code --skill dashboard-builder
compare_arrows

Before / After 效果对比

1
使用前

手动在多个工具间切换查看日志、指标和追踪,难以关联事件,发现问题后还需额外时间定位根因

使用后

单一仪表板显示关键健康指标、异常高亮和待处理行动,自动关联相关日志和追踪,5分钟内定位问题

SKILL.md

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)

发表评价

效果
易用性
文档
兼容性

暂无评价

统计数据

安装量2.7K
评分4.4 / 5.0
版本
更新日期2026年5月23日
对比案例1 组

用户评分

4.4(6)
5
50%
4
33%
3
17%
2
0%
1
0%

为此 Skill 评分

0.0

兼容平台

🔧Claude Code

时间线

创建2026年4月16日
最后更新2026年5月23日