JOJackson OchoaLeer en español

Systems dashboard

Rust Dashboard

A system and Docker dashboard pairing a Rust agent with a Svelte interface for operational visibility.

Operational signal
Status
In production
Project type
Personal tool
Role
Architecture, Rust agent, and web dashboard
Scope
Architecture, agent, and interface
Stack
Rust · Axum · Tokio · Svelte · TypeScript · Vite · SQLite · Docker · WebSockets

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.

Services

  • Systems architecture
  • Rust development
  • Dashboard development

Proof

  • Rust agent for system and Docker information
  • Web dashboard with typed operational states

Architecture

A Rust collection agent is separated from a typed web dashboard so system data can serve more than one interface.

Approved material

Rust Dashboard operational monitoring interface.
Operational dashboard for system and Docker signals.

Privacy

Infrastructure details, hostnames, addresses, credentials, and live system data are not published.

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.

Keep going?

Let’s talk about the real problem.

Start a conversation
All work