Revision Failures and Startup¶

Use this query when a revision fails to become healthy or startup behavior is unstable.

Data Source¶

Query Pipeline¶

flowchart TD
    A[Filter by app] --> B[Filter startup and failure signals] --> C[Project revision columns] --> D[Sort by time]

Query¶

let AppName = "my-container-app";
ContainerAppSystemLogs_CL
| where ContainerAppName_s == AppName
| where Log_s has_any ("Failed", "provision", "startup", "probe", "timeout")
| project TimeGenerated, RevisionName_s, ReplicaName_s, Reason_s, Log_s
| order by TimeGenerated desc

Example Output¶

Interpretation Notes¶

• Focus on earliest failure event for each revision.
• Reason_s helps separate config validation failures from runtime startup issues.
• Normal pattern: short startup logs followed by healthy state, not repeated failures.

Limitations¶

• System logs can be delayed by ingestion latency.
• Some workspaces use non-_CL table names.

See Also¶

• Image Pull and Auth Errors
• Revision Provisioning Failure Playbook