Goal
Read the node fleet operationally instead of node-by-node in isolation.Prerequisites
- Two or more nodes is ideal, but not required
Workflow
1
Use the operations node view to compare health and issue concentration.
2
Cross-check with the nodes management page when you need to act.
What this page emphasizes
- Node status filtering across healthy, degraded, and offline hosts
- Region and node-name search
- Hotspot-style fleet review instead of one-node-at-a-time management
From view to action
The operations nodes view is for spotting where problems concentrate across the fleet — a cluster of degraded or offline hosts, or a region with issues. When you need to act on a specific node (drain it, upgrade the agent, inspect diagnostics), cross over to that node on the Nodes management page.Expected result
Node problems can be found more quickly from the platform view.
Related guides
Node overview
What a node is, what the agent does, and what node health means in StackShift.
Maintenance mode
Use maintenance as a safety control before upgrades or disruptive host changes.
Node health, diagnostics, and deletion
Interpret overlay, mTLS, heartbeat, runtime, operation, inventory, and explicit deletion-blocker state before taking action.