Container Apps console logs take 7–9 minutes to reach Log Analytics; delay occurs before workspace receipt and varies per revision

We see consistently high latency for Azure Container Apps console logs (ContainerAppConsoleLogs) arriving in Log Analytics, in Sweden Central.

Setup: Container Apps environments using the "Azure Monitor" logs destination, with a diagnostic setting sending console logs to the resource-specific ContainerAppConsoleLogs table. Migrated from the legacy ContainerAppConsoleLogs_CL / Data Collector API path in September 2026.

Measurements:

• For a one-hour window, the receive delay (TimeGenerated to _TimeReceived) was p50 440 s / p95 515 s, while workspace ingestion (_TimeReceived to ingestion_time()) was only p50 4 s / p95 36 s. Approx. 98% of the delay happens before the workspace receives the data.
• Over 30 days, the median total delay has stayed between 5 and 7.5 minutes, with p95 at 8-9.5 minutes.
• The delay level is fixed per revision. Three apps deployed at the same moment settled at median delays of 3.4, 6.2 and 7.8 minutes respectively, and stayed there until the next deployment.
• Log volume does not explain it: a second environment, logging to a separate workspace at approx. 100 lines per hour, shows the same 6-minute median as our main environment at several hundred thousand lines per hour.

Questions:

1. Is a multi-minute delay before workspace receipt expected for Container Apps log collection in Sweden Central?
2. What could make the delay level differ per revision (replica placement, node-level collectors)?
3. Is there anything on the customer side that influences this collection stage?

We also have an open support case for this.