Current deploy state
See the active deployment stage and its current outcome.
Current Status & App Logs
The console keeps the evidence available today close to the application: current deployment status, health and lifecycle state, and a bounded tail of local application output. Named support uses that context with the application's runbook.
For teams that need a practical first diagnostic view and a clear escalation path without mistaking it for a complete observability suite.
01
What it gives the application
The capability, the operating value, and the boundary are described together.
Runtime state
Read the application's current running, stopped, or failed lifecycle status.
Bounded local output
Inspect the locally retained application-log tail available for the workload.
Named escalation
Bring the current evidence to the engineer who knows the environment and runbook.
02
How it works in a production engagement
Start with evidence, make the current boundary explicit, then apply the verified workflow.
- 01
Identify the application
Start from the tenant and application identity shown in the console.
- 02
Read current state
Check deployment stage, health result, and runtime lifecycle.
- 03
Inspect local output
Use the bounded application-log tail to find the immediate failure signal.
- 04
Escalate with context
Share the application, time window, action, and current evidence through the agreed support route.
03
Included in the current capability
These are the available building blocks; the workload-specific scope is confirmed during review.
- ✓Current deployment status
- ✓Runtime lifecycle state
- ✓Health result
- ✓Bounded local application logs
- ✓Tenant and application context
- ✓Named support route
Current limitations
This view is not a durable log archive or a complete telemetry product. Long-term retention, dashboards, automated alerting, and distributed request tracing are not included in the current public capability.
Production Operations PilotApply this capability to one real workload.