Dashboard Control Interface Update

wasmCloud / wasmcloud-otp

wasmCloud host runtime that leverages Elixir/OTP and Rust to provide simple, secure, distributed application development using the actor model

Apache License 2.0

228 stars 48 forks source link

Dashboard Control Interface Update #171

Closed brooksmtownsend closed 3 years ago

brooksmtownsend commented 3 years ago

High-level things that need to be done

[x] Lattice view vs Host specific view (could just be filtering by-host in lattice view). #192
[x] Use control interface for remote hosts, host API for local operations
[x] Stop listening to lc.> prefix for cache operations, use GenServer instead (facilitated by #169)
[x] Query resources on startup. This includes actors, providers, link definitions, and hosts. This will likely involve some restructuring of the state_monitor as it may be less efficient to store a flat list of actors/providers (implemented in #181)

brooksmtownsend commented 3 years ago

We'll also want to re-evaluate the metrics that we show at the top of the page as they are local-host specific and don't belong on a lattice view. We should consider only showing them for the local wasmcloud host, or hiding them altogether for now if they are misleading.

brooksmtownsend commented 3 years ago

Notes from community meeting for fixes

[x] Show host selector by the breadcrumb

widgets (some items here are out of scope for 0.50)

[x] Change processes to Running Processes (OTP) to avoid confusion
[x] may only care about wasmcloud actor count, rather than OTP processes
[x] Overall vote: Metrics tab with higher fidelity metrics over time
[ ] OneView to see overall observability when metrics are useful
[ ] Tone down the metrics widget colors

actors, providers, ldfs

[x] Show Provider name (requires it to be stored in the claims information)

brooksmtownsend commented 3 years ago

All items completed