Rust Dashboard

The problem

System state is rich but rarely legible. Operators need a small, trustworthy surface that turns containers, resources, and events into action.

Decisions

• Keep collection and presentation separate so the agent remains useful beyond one UI.
• Use a typed contract at the boundary between Rust data and the Svelte surface.
• Design the dashboard around signal hierarchy, not a wall of metrics.

Evidence

• Rust agent architecture for system and Docker information.
• Svelte dashboard shell with typed data and operational states.
• Traefik-fronted deployment shape prepared for real environments.

What I learned

• Observability is a product design problem: signal without hierarchy is noise.
• A small contract can preserve freedom between a systems agent and its interfaces.