zacheryasc
85dd1d4cb4
Adds some more polish to the dashboard. Further modification will have to wait until swactor is used for more complex projects. Signed-off-by: Zachery Aaron Shores-Chmielewski <zacheryasc@gmail.com>
1.2 KiB
1.2 KiB
Dashboard Improvements — Research Phase
Summary
Researched 10 comparable monitoring/dashboard systems to inform swactor's dashboard improvement plan.
Systems Analyzed
- Actor runtimes: Erlang Observer (GUI/CLI/Web), Akka Insights, Ray Dashboard, Orleans Dashboard
- Async/runtime tools: tokio-console, Lunatic
- Message/infrastructure: RabbitMQ Management, Consul UI, Nomad UI
- Web frameworks: Phoenix LiveDashboard
Key Findings
- Time-series history is table-stakes — every system provides it
- Actor detail drill-down is universal (Observer has 6-tab process info, Orleans has grain state inspection)
- Search/filter exists in every system
- Warning/anomaly detection (tokio-console's lint system) is a high-value differentiator
- Topology visualization (Consul golden metrics, Observer supervision tree) is rare but powerful
Implementation Plan
8 feature stages defined (see CLAUDE/notes/feature-stages/):
- Time-Series History Infrastructure
- Actor Detail Drill-Down
- Search and Filter
- Per-Worker Utilization Visualization
- Warning/Anomaly Detection
- Actor-to-Actor Message Flow Topology
- Per-Actor Logging
- Per-Message-Type Breakdown