Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Use the Services view as a platform operations inventory, not just a list page.

​
Prerequisites

  • Live stacks or databases

​
Workflow

1
Review service status and health from the operations surface.
2
Use service cards to jump into more specific detail when needed.
3
Read backup and update signals as operational cues, not decoration.

​
What appears in the service hub

  • Template-backed stacks and direct stacks
  • Standalone managed databases
  • Operational cues like backup posture, update availability, node assignment, and recovery state

​
Reading the cues

  • Health and status tell you whether a service is actually serving.
  • Update availability reflects template upgrade status (update_available, upgrade_blocked).
  • Backup posture flags services without a usable recent backup.
  • Node assignment shows where the service landed, which matters when one node is unhealthy.
  • Recovery state surfaces an in-flight or failed operation so you catch it from the hub, not after the fact.

​
Expected result

You can reason about the live service ecosystem from one surface.

Operations overview

The operations area is the cross-resource health and runtime visibility surface for StackShift.

Recovery states, logs, and troubleshooting

Read the operation state on a resource — its status, current step, attempt count, retryable flag, and last error — together with logs, instead of treating a single “error” badge as the whole story.

Stack logs, health, and placement

Use the stack detail, logs, and placement information to understand how the stack is actually running.