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: Organize around: Inspect existing dashboards first: Recommended structure: Every panel should answer a real question. If it does not, remove it. - is it healthy? - where is the bottleneck? - what changed? - what action should someone take? - "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" - 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 - health / availability - latency / performance - throughput / volume - saturation / resources - service-specific risk - JSON structure - query language - variables - threshold styling - section layout - overview - performance - resources - service-specific section - cluster health - shard allocation - search latency - indexing rate - JVM heap / GC - broker count - under-replicated partitions - messages in / out - consumer lag - disk and network pressure - request rate - p50 / p95 / p99 latency - error rate - upstream health - active connections - research-ops -...