Ingress Error Analysis
Use this query to investigate ingress-related request failures such as 502/504 and backend connectivity errors.
Data Source
| Table | Schema Note |
ContainerAppSystemLogs_CL | Legacy schema. If empty, try ContainerAppSystemLogs (non-_CL). |
Query Pipeline
flowchart LR
A[Filter by app] --> B[Filter ingress and gateway signals] --> C[Project revision and reason] --> D[Sort by time]
Query
let AppName = "my-container-app";
ContainerAppSystemLogs_CL
| where ContainerAppName_s == AppName
| where Log_s has_any ("ingress", "gateway", "502", "503", "504", "connection refused", "upstream")
| project TimeGenerated, RevisionName_s, Reason_s, Log_s
| order by TimeGenerated desc
Example Output
| TimeGenerated | RevisionName_s | Reason_s | Log_s |
| 2026-04-04T11:44:02.611Z | ca-myapp--0000002 | ProbeFailed | upstream request timeout while waiting for backend response (504) |
| 2026-04-04T11:43:57.204Z | ca-myapp--0000002 | ProbeFailed | ingress gateway received 502 from backend pod |
| 2026-04-04T11:42:11.933Z | ca-myapp--0000002 | RevisionUpdate | ingress endpoint switched to latest revision |
Interpretation Notes
- Repeated 502/504 with unhealthy revisions points to backend readiness issues.
- Errors without revision failures may indicate caller network path or DNS issues.
- Normal pattern: occasional transient errors, not sustained spikes.
Limitations
- Ingress behavior details can vary by environment topology.
- Needs correlation with console logs for app-level failures.
See Also