A container app fails right after deployment. What do you check first?
Why C is the answer
Its console and system logs
Logs show startup errors, such as a missing setting or a failed probe.
In detail
- Console logs show your app's output.
- System logs show platform events.
- Check system logs when the app never starts.
Use case
An illustrative scenario, not a real incident.
A container app fails after deployment. Its console logs show a missing variable, and system logs confirm that the container exited.
See it in different ways
sequenceDiagram participant A as Service A participant B as Service B participant C as Service C participant M as Application Insights A->>B: Request, with trace context B->>C: Request, with trace context A->>M: Spans B->>M: Spans C->>M: Spans
flowchart TD
Q{"What do you need to see?"}
Q -->|"Your app's output"| A0["Console logs"]
Q -->|"Platform events"| A1["System logs"]Key point: Console and system logs come first.
Why the other options are wrong
- A. The subscription's budget alerts
- Budget alerts do not stop a container.
- B. The tags on the environment
- Tags do not affect startup.
- D. The Azure Advisor score
- An Advisor score does not show why it failed.