DNS and Connectivity Failures¶

Use this query when dependency calls fail due to DNS lookup errors, timeouts, or transport connectivity issues.

Data Source¶

Query Pipeline¶

flowchart LR
    A[Filter by app] --> B[Filter DNS and network terms] --> C[Project replica context] --> D[Sort by time]

Query¶

let AppName = "my-container-app";
ContainerAppConsoleLogs_CL
| where ContainerAppName_s == AppName
| where Log_s has_any ("name resolution", "NXDOMAIN", "timeout", "connection refused", "TLS", "handshake")
| project TimeGenerated, RevisionName_s, Log_s
| order by TimeGenerated desc

Example Output¶

Interpretation Notes¶

• Clustered errors across replicas often indicate shared DNS or network path problems.
• Single-replica concentration can indicate noisy neighbor or transient pod issues.
• Normal pattern: rare connectivity errors under external service turbulence.

Limitations¶

• Console logs require explicit app-side exception logging.
• Cannot independently verify DNS zone linkage.

See Also¶

• Ingress Error Analysis
• Internal DNS and Private Endpoint Failure Playbook