swactor/crates/dashboard
Zachery Aaron Shores-Chmielewski e0fe5b5481 refactor: remove dead code, consolidate files (#52)
Remove the unused TCP transport and dead CLI/simulation scaffolding and collapse scattered single-purpose modules into consolidated files across the dashboard, process, and simulation crates.

- crates/transport: drop the TCP transport (src/tcp.rs and its tcp feature), leaving only ed25519 identity and encoding utilities behind the iroh transport
- crates/dashboard: collapse actor_detail_html/actors_html/dashboard_html/topology_html into a single html.rs, drop command/parse.rs, and inline the trace types into lib.rs
- crates/process: fold driver, pipeline_types, queue, subscriber, waker, and local pipes/signal/wait into local/mod.rs, pipeline.rs, and a unified types.rs, consolidating the public re-exports
- crates/simulation: remove the ci subdirectory (local_sim, sim) and dead node/config/trace modules, and flatten the distribution subdirectory into top-level files
- crates/datastore: remove the unused store_cli, cli, and in-memory storage, and deduplicate crypto.rs across datastore and distribution (about 190 lines of shared code removed)
- crates/distribution: drop dead codec code and trim the messages module

Signed-off-by: Zachery Aaron Shores-Chmielewski <zacheryasc@gmail.com>
2026-02-25 14:33:04 +00:00
..
src refactor: remove dead code, consolidate files (#52) 2026-02-25 14:33:04 +00:00
tests refactor: remove dead code, consolidate files (#52) 2026-02-25 14:33:04 +00:00
.gitignore feat: stability for deployment and distribution (#44) 2026-02-19 14:39:33 +00:00
AGENTS.md refactor: consolidate crate functions (#50) 2026-02-24 09:12:28 +00:00
Cargo.toml refactor: consolidate crate functions (#50) 2026-02-24 09:12:28 +00:00
README.md refactor: consolidate crate functions (#50) 2026-02-24 09:12:28 +00:00

dashboard

Visual dashboard for the swactor runtime. Provides a live HTTP dashboard, a terminal UI (TUI), trace recording/replay, and an HTTP API for programmatic runtime investigation.

Features

Feature Default Description
distribution yes /distribution page with SWIM membership, Kademlia routing, and location cache
tui no Terminal UI with overview, worker detail, and distribution views

HTTP Dashboard

Start the dashboard demo and open it in a browser:

cargo run -p dashboard --example dashboard_demo

Pages:

  • http://localhost:9090 — live overview (workers, actors, message rates)
  • http://localhost:9090/actors — actor table
  • http://localhost:9090/distribution — SWIM membership, Kademlia routing, cache entries

The demo creates a 4-worker runtime with ping-pong and counter actors, plus a 9-node distribution cluster (1 main node + 8 peers) with simulated SWIM membership and actor registrations in the directory/cache.

TUI

A standalone binary that connects to any running dashboard over SSE:

cargo run -p dashboard --features tui --bin swactor-tui
# or point at a specific endpoint
cargo run -p dashboard --features tui --bin swactor-tui -- http://localhost:9090

Views (cycle with Tab):

  • Overview — htop-style worker bars, summary line, sortable actor table
  • Worker Detail — focused view of a single worker's actors and phase breakdown
  • Distribution — cluster summary, scrollable members table, cache entries, routing bucket histogram

Key bindings: q quit, Tab cycle views, s sort column, r reverse sort, arrow keys/j/k scroll, Enter drill into worker, Esc back to overview.

Agent HTTP API (Investigate)

All diagnostic commands are available as HTTP endpoints when the dashboard server is running. See AGENTS.md for full protocol documentation.

curl 'http://localhost:9090/api/investigate?cmd=overview'
curl 'http://localhost:9090/api/investigate?cmd=hot&n=5'
curl 'http://localhost:9090/api/investigate?cmd=workers'
curl 'http://localhost:9090/api/investigate?cmd=worker&id=2'
curl 'http://localhost:9090/api/investigate?cmd=actors&sort=mailbox&limit=10'
curl 'http://localhost:9090/api/investigate?cmd=diff&seconds=2'

The same commands are also available via a stdin/stdout REPL for direct programmatic use (see investigate::run_investigate).

Demos

All examples are run from the workspace root.

HTTP dashboard — live workload with distribution cluster, Ctrl+C to stop:

cargo run -p dashboard --example dashboard_demo
# http://localhost:9090              — runtime overview
# http://localhost:9090/distribution — cluster view

Benchmarks — four automated scenarios (~20 s total):

cargo run -p dashboard --example bench_dashboard
# open http://localhost:9090

Record & replay — records ~10 s of activity, then serves a replay:

cargo run -p dashboard --example record_and_replay_demo
# live dashboard at http://localhost:9090 during recording
# replay dashboard at http://localhost:9091 after recording finishes
# Ctrl+C to stop