Summary
A UI to view and manage distributed-worker runners — roster/status, heartbeats, and queue activity — plus administration of runner access (approve / revoke).
Context
Requested by @gissf1 in #31:
we should at some point have a UI to view and manage runners, but that would need authentication and login permissions and a bunch of other stuff, so if there's no ticket for it yet, create one, but it should be in the backlog and low priority at this time.
Scope (provisional)
Priority
Backlog / low priority (per @gissf1). Not on the critical path. Depends on #31 (HTTP queue API + runner registration + submission auth) landing first.
Related
— Filed by Bastion at @gissf1's request // 060205ZJUN26
Summary
A UI to view and manage distributed-worker runners — roster/status, heartbeats, and queue activity — plus administration of runner access (approve / revoke).
Context
Requested by @gissf1 in #31:
Scope (provisional)
ACTIVE/IDLE/DEAD), last heartbeat, current claim, host/identity; queue depth and in-flight runs.Priority
Backlog / low priority (per @gissf1). Not on the critical path. Depends on #31 (HTTP queue API + runner registration + submission auth) landing first.
Related
— Filed by Bastion at @gissf1's request // 060205ZJUN26