Section Overview
Operations
Use the operations surfaces to understand health, services, alerts, node state, and recovery progress.
Operations overview
The operations area is the cross-resource health and runtime visibility surface for StackShift.
Goal
Understand what belongs in operations versus in a resource detail page.
Expected result
You know where to look first when something feels wrong at a platform level.
Services view
Track stack-backed services and databases in one place with health, backup posture, and upgrade cues.
Goal
Use the Services view as a platform operations inventory, not just a list page.
Expected result
You can reason about the live service ecosystem from one surface.
Alerts view
Use alerts to focus on active operational problems instead of scanning every resource manually.
Goal
Understand the current alerts surface and what actionability to expect from it today.
Expected result
You can tell which issues need immediate attention and which are informational.
Nodes view
Use the node-focused operations surface when you need to think about capacity, health, and runtime readiness across hosts.
Goal
Read the node fleet operationally instead of node-by-node in isolation.
Expected result
Node problems can be found more quickly from the platform view.
Recovery states, logs, and troubleshooting
Interpret retrying, cleanup-required, manual-attention, and failure states without treating them as generic “error” badges.
Goal
Use the new recovery-state model and logs together to diagnose operational problems accurately.
Expected result
Recovery and failure states feel operationally useful instead of vague.