Parent
Outcome
Make running workloads understandable and operable after deployment: runtime inventory, safe lifecycle actions, shell/log access, historical telemetry, request insights, health checks, alerts, notifications, workers, schedules, and cost context.
UX direction
Every service detail page should answer: what is running, where, which release, whether it is healthy, what changed, what it costs, and what safe action is available next. Live data must clearly distinguish fresh, stale, snapshot, unavailable, and unsupported states.
Existing work incorporated
Children
Exit criteria
Operators can diagnose and recover common incidents from one service timeline without switching among provider consoles, while every action remains available through shared application services for CLI automation.