Health Probe Timeline¶

Use this query to reconstruct the sequence of probe-related events so you can see whether a replica recovered, kept flapping, or failed repeatedly during rollout.

Data Source¶

Query Pipeline¶

flowchart LR
    A[Filter by app] --> B[Filter probe signals] --> C[Project timeline columns] --> D[Sort oldest to newest]

Query¶

let AppName = "my-container-app";
ContainerAppSystemLogs_CL
| where ContainerAppName_s == AppName
| where Log_s has_any ("probe", "Readiness", "Liveness", "Startup") or Reason_s has_any ("ProbeFailed", "ProbeSucceeded")
| extend ProbePhase = case(
    Log_s has "readiness" or Log_s has "Readiness", "readiness",
    Log_s has "liveness" or Log_s has "Liveness", "liveness",
    Log_s has "startup" or Log_s has "Startup", "startup",
    "unspecified")
| project TimeGenerated, RevisionName_s, ReplicaName_s, ProbePhase, Reason_s, Log_s
| order by TimeGenerated asc

Example Output¶

Interpretation Notes¶

• Read the rows top-to-bottom to distinguish transient warm-up failures from persistent health instability.
• Repeated ProbeFailed events on the same ReplicaName_s without a later success usually mean the replica never stabilized.
• A normal rollout often shows early startup/readiness failures followed by ProbeSucceeded once the app finishes initialization.

Limitations¶

• Probe wording can vary, so text-matching may miss uncommon platform messages.
• This timeline does not prove root cause; correlate with console logs and revision configuration.

See Also¶

• Revision Failures and Startup
• Replica Crash Signals