THE FIELD GUIDE / FLEET MANAGEMENT
Server workspaces & lifecycle
Everything recorded for a server, in a consistent set of tabs.
A workspace per host
Open a server name to see overview, packages, patching timeline, investigations, AI activity, history, repositories, security, file integrity and maintenance. Open Connection settings to test or repair its route. Switch hosts while keeping your current tab, or bookmark it directly. Tabs and actions respect role permissions.
Disable, enable or delete
Disable suspends polling, scheduled work and host AI requests, cancels queued operations and revokes enrollment links. Enable resumes future management without replaying cancelled jobs. Delete requires an exact name and reason, removes local credentials and retains historical records under Deleted servers. Active work and unresolved response or recovery holds must be reconciled first.
Focused workspaces and history
Use the searchable server directory and focused Overview pages for status and attention items, then open dedicated AI run, Activity, audit, package and historical snapshot list/detail pages. Per-server tabs, subpages, breadcrumbs, filters and back navigation keep context without crowding a single dashboard. Stored startup Files and Coverage pages preserve review evidence.
Read upgrade and delivery health at a glance
An offered major OS upgrade has a dashboard card and a consistent accessible badge wherever the server appears. Spool utilization, backlog age and delivery health explain collector pressure in server and fleet summaries. Stale or unknown checks remain visibly different from healthy or available states.
Keep retained-server access explicit
Deleted-server investigations, jobs, outputs and package history retain their administrator-only boundary, including indirect links and global lists. Disabled-server read access follows its separate existing policy. Hiding a navigation item is never the authorization control.
Fleet visibility
Filter inventory and investigation history, follow stale telemetry and overdue sweeps, inspect source-level repository diagnostics and use timeline diffs to understand changes. Pagination, cache quotas and worker backpressure keep growing inventories practical.
Open the application reference for capability scope and technical details.
Open Open SERVER_WORKSPACES.md on GitHub ↗