Skip to content

feat(dashboard): surface live telemetry widgets (Power/Thermal, Per-Slot Throughput, MHz/temp)#1019

Merged
thinmintdev merged 1 commit into
mainfrom
fix/wave8a-dashboard-telemetry
Jul 4, 2026
Merged

feat(dashboard): surface live telemetry widgets (Power/Thermal, Per-Slot Throughput, MHz/temp)#1019
thinmintdev merged 1 commit into
mainfrom
fix/wave8a-dashboard-telemetry

Conversation

@thinmintdev

Copy link
Copy Markdown
Contributor

Wave 8A — live telemetry on the main dashboard

The customizable dashboard board already shipped the telemetry cards as opt-in; this makes the throughput / usage / live-clock signals visible by default.

  • Power & Thermal card (live GPU MHz + temp + power, from /api/stats/power) → defaultOn: true.
  • Per-Slot Throughput card (per-slot tok/s, from /api/throughput) → defaultOn: true.
  • Utilization card (already default-on) now shows a guarded live clock/temp caption ("1234 MHz · 61°C") reusing gpu_clock_mhz/gpu_temp_c already in its useStatsHardware payload.

Both CARD_REGISTRY copies (dash-grid.jsx + useDashLayout.ts) updated identically. No new data hooks or client ring buffers; existing card behavior unchanged.

Verification

  • npm run build (vite) clean; 13 dashboard e2e specs pass locally (dashboard-overhaul, dashboard-v3, footer-throughput, etc.).

🤖 Generated with Claude Code

…Per-Slot Throughput, MHz/temp on Utilization

The dashboard widget board already carried PowerCard (live GPU MHz/temp/
power) and SlotTrackCard (per-slot tok/s) as opt-in; flip both defaultOn:
true in both CARD_REGISTRY copies (dash-grid.jsx + useDashLayout.ts), and
add a guarded live clock/temp caption to the default Utilization card
(reuses gpu_clock_mhz/gpu_temp_c already in the useStatsHardware payload).
No new data hooks or ring buffers.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@thinmintdev thinmintdev enabled auto-merge (squash) July 4, 2026 04:08
@thinmintdev thinmintdev merged commit 9793a8e into main Jul 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant