Operations
Operations overview
LiveThe 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.
Current status
Live
This area is documented as current, user-reliable behavior.
Workflow
- 1Use operations when you want a platform-wide view instead of a single resource view.
- 2Drill into services, alerts, and nodes depending on the operational question.
- 3Treat recovery-state messaging as part of the operational model, not just a design flourish.
When to start in Operations
- Several services look unhealthy at once
- You need a fleet-level view before drilling into one resource
- You want to understand alerts, services, and node state together
What Operations is not
Operations is not a replacement for resource detail pages. It is the platform-wide orientation surface. Start there when the question is broad, then drill into the relevant project, stack, database, or node page when you need resource-specific evidence.
Expected result
You know where to look first when something feels wrong at a platform level.