Azure Container Apps: No logs/metrics flowing to Log Analytics or Storage (westus3)

Question

Azure Container Apps: No logs/metrics flowing to Log Analytics or Storage (westus3)

Andrew Cuncannan (Admin) 20

Issue Summary

Azure Container Apps environment is not delivering diagnostic logs or metrics to Log Analytics or Storage, despite correct diagnostic settings and traffic generation.

Environment

Resource Group: <resource-group-name>
Container App: <container-app-name>
Environment: <aca-environment-name> in region <region>
Log Analytics Workspaces tested:
- <original-law-name> (original)
- <new-law-name> (new, isolated test)
Storage Account tested: <storage-account-name>

Problem Details

Diagnostic settings are configured at the environment scope:
- ContainerAppConsoleLogs (enabled)
- ContainerAppSystemLogs (enabled)
- AllMetrics (enabled)
Multiple destinations tested:
- Existing Log Analytics workspace
- New Log Analytics workspace (to rule out LAW misconfiguration)
- New Storage account (to rule out LAW pipeline issues)
Synthetic traffic (hundreds of requests) generated against the Container App ingress FQDN.

Observations

Log Analytics: Queries return 0 rows for ContainerAppConsoleLogs, ContainerAppSystemLogs, and AzureMetrics. Both the original LAW and the new test LAW show no ingestion.
Storage Account: Even after extended polling, no insights-logs-* or insights-metrics-* containers were created.
Diagnostic Settings Validation: Confirmed via CLI that the environment has multiple diagnostic settings pointing to LAW and Storage, with categories enabled.

Steps Already Taken

Verified diagnostic settings JSON (categories correctly enabled).
Tested both LAW and Storage as sinks.
Ran isolation test with new LAW — still no logs.
Burst traffic against Container App ingress endpoint.
Waited for ingestion (LAW >10 minutes, Storage >6 minutes).

Request

This appears to be a platform-level ingestion issue in the specified region for Azure Container Apps environment diagnostics.

Please confirm whether this is a known issue, and if not, help investigate why no logs or metrics are flowing from ACA → LAW/Storage despite valid configuration.

Andrew Cuncannan (Admin) 20 Reputation points

2025-09-03T01:34:06.61+00:00

Hello Bharath,

Thank you for the guidance and verification steps. We tested in our environment and can confirm the behavior you described.

After updating the Container Apps Environment log destination to Log Analytics, existing apps in the environment stopped sending console logs, while newly deployed or revised apps ingested normally.

Queries confirmed this: one app produced continuous entries in ContainerAppConsoleLogs_CL, while another remained empty until action was taken.

Environment-level AzureMetrics continued to flow without interruption.

Remediation Applied
We forced a new revision on the affected apps by applying a no-op update (adding a dummy environment variable). This immediately restored log ingestion for the previously stranded apps.

Results

All apps in the environment now emit console logs into LAW.

The remediation is consistent and repeatable.

We are documenting this as an interim SOP: after any environment log destination change, force a new revision for each app to rebind logging.

We appreciate your confirmation of this behavior and will maintain the SOP until a platform-level fix is documented. Please let us know if there are updates planned for this scenario.

Best regards,

Andrew
Siva shunmugam Nadessin 10,895 Reputation points Microsoft External Staff Moderator

2025-09-03T08:38:46.15+00:00

Hello Andrew Cuncannan (Admin),

We have checked your reply.

You have mentioned on behavior, kindly elaborate on which behavior you need the confirmation?
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-04T17:06:52.2366667+00:00

Hello Andrew Cuncannan (Admin), We have reached out to you for few of the details in Private message, could you please check and share the details?

Thanks,
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-05T20:25:36.92+00:00

Hello Andrew Cuncannan (Admin), Thank you for the update. Applying a no-op change specifically adding a dummy environment variable successfully triggered a new revision and restored log ingestion for the previously disconnected apps. Since this approach is working, we will check with this behavior with our Product team and will follow up with any updates.

We appreciate your patience in this regard.

Thanks
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-09T17:32:37.61+00:00

Hello Andrew Cuncannan (Admin), We have reached out to you for few of the details in Private message, could you please check and share the details?

Thanks,
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-10T17:17:56.6866667+00:00

Hello Andrew Cuncannan (Admin), We have reached out to you for few of the details in Private message, could you please check and share the details?

Thanks,

1 answer

Your answer

Andrew Cuncannan (Admin) 20 Reputation points

2025-09-03T01:34:06.61+00:00

Hello Bharath,

Thank you for the guidance and verification steps. We tested in our environment and can confirm the behavior you described.

After updating the Container Apps Environment log destination to Log Analytics, existing apps in the environment stopped sending console logs, while newly deployed or revised apps ingested normally.

Queries confirmed this: one app produced continuous entries in ContainerAppConsoleLogs_CL, while another remained empty until action was taken.

Environment-level AzureMetrics continued to flow without interruption.

Remediation Applied
We forced a new revision on the affected apps by applying a no-op update (adding a dummy environment variable). This immediately restored log ingestion for the previously stranded apps.

Results

All apps in the environment now emit console logs into LAW.

The remediation is consistent and repeatable.

We are documenting this as an interim SOP: after any environment log destination change, force a new revision for each app to rebind logging.

We appreciate your confirmation of this behavior and will maintain the SOP until a platform-level fix is documented. Please let us know if there are updates planned for this scenario.

Best regards,

Andrew
Siva shunmugam Nadessin 10,895 Reputation points Microsoft External Staff Moderator

2025-09-03T08:38:46.15+00:00

Hello Andrew Cuncannan (Admin),

We have checked your reply.

You have mentioned on behavior, kindly elaborate on which behavior you need the confirmation?
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-04T17:06:52.2366667+00:00

Hello Andrew Cuncannan (Admin), We have reached out to you for few of the details in Private message, could you please check and share the details?

Thanks,
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-05T20:25:36.92+00:00

Hello Andrew Cuncannan (Admin), Thank you for the update. Applying a no-op change specifically adding a dummy environment variable successfully triggered a new revision and restored log ingestion for the previously disconnected apps. Since this approach is working, we will check with this behavior with our Product team and will follow up with any updates.

We appreciate your patience in this regard.

Thanks
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-09T17:32:37.61+00:00

Hello Andrew Cuncannan (Admin), We have reached out to you for few of the details in Private message, could you please check and share the details?

Thanks,
Bharath Y P 9,810 Reputation points Microsoft External Staff Moderator

2025-09-10T17:17:56.6866667+00:00

Hello Andrew Cuncannan (Admin), We have reached out to you for few of the details in Private message, could you please check and share the details?

Thanks,

Answer 1

Hello Andrew Cuncannan (Admin),

You're facing an issue where the Azure Container Apps (ACA) environment fails to deliver diagnostic logs or metrics to Log Analytics Workspaces (LAW) or Azure Storage, even though diagnostic settings are correctly configured, multiple destinations have been tested, and synthetic traffic has been generated.

Here are some common reasons why logs might be missing:

Diagnostic logs are only ingested if container apps emit logs and system logs are generated.
This may occur when the Log Destination setting of an Azure Container Apps environment is modified, for example, switching between "Don't save logs" and "Azure Log Analytics." The issue specifically affects container apps that were already deployed in the environment prior to the change. These existing apps may stop sending logs as expected. In contrast, newly created container apps that deployed after the Log Destination is set to Log Analytics continue to emit logs correctly, unless the environment’s log destination is changed again.

Additionally, confirm the following settings to validate that the configuration is correctly applied:

1. Verify the Container Apps Environment logging option is correctly configured.

Go to azure portal.
Open your Container Apps Environment > monitoring > logging option
Verify that you selected the logs destination as Azure log analytics and check the configuration

Double-check diagnostic settings exist and are correctly set at the Container Apps Environment level for:

Logs: ContainerAppConsoleLogs, ContainerAppSystemLogs
Metrics: AllMetrics

Run Log Analytics queries for your container app across the correct workspace using:

ContainerAppConsoleLogs_CL :

ContainerAppConsoleLogs_CL
| where ContainerAppName_s == "<Your App name>"

ContainerAppSystemLogs_CL

ContainerAppSystemLogs_CL
| where ContainerAppName_s == "<Your App name>"

AzureMetrics

AzureMetrics | where ResourceId contains
/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.App/managedEnvironments/<environment-name> | order by TimeGenerated desc

Check these queries and see if you can see any of the logs for your container app

Please confirm if this is helpful and please let us know if you need further assistance.

Share via

Azure Container Apps: No logs/metrics flowing to Log Analytics or Storage (westus3)

Issue Summary

Environment

Problem Details

Observations

Steps Already Taken

Request

1 answer

Your answer