See logs in Aspire Dashboard and Azure Monitoring/Log stream in Azure Container Apps

Hello Jesper Clausen,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are unable to see the console logs in the Aspire Dashboard and in the Azure Monitoring/Log stream in Azure Container Apps.

Since there is no prove of failure, you will need to affirm whether new console output from the currently active revision is still reaching Log Analytics. By carry out the followings:

• Generate a unique log entry through the application’s existing ILogger pipeline.
• Verify that the new entry reaches ContainerAppConsoleLogs_CL.
• Confirm that the active revision has a running replica and that the correct container is selected.
• Test live console streaming independently with Azure CLI.
• If CLI streaming works, correct the portal, browser, proxy, revision, or container selection.
• If CLI and Portal Log Stream work but Aspire does not, correct the Aspire Dashboard access, default hostname, RBAC, or OpenTelemetry configuration.
• If fresh logs reach Log Analytics but CLI, Portal Log Stream, and Aspire all fail for multiple applications, open an Azure support request for the affected Container Apps environment. That result proves that application logging and stored ingestion are operating, while the Azure-managed live-streaming path is failing.

Do not change the Log Analytics destination, recreate the environment, redeploy every application, or permanently set all applications to one replica before completing this isolation. Those changes may not repair the failed path and could remove evidence needed for the root-cause investigation.

Use the following Microsoft resources and steps:

• https://learn.microsoft.com/azure/container-apps/log-streaming
• https://learn.microsoft.com/azure/container-apps/logging
• https://learn.microsoft.com/azure/container-apps/log-monitoring
• https://learn.microsoft.com/azure/container-apps/aspire-dashboard
• https://learn.microsoft.com/azure/container-apps/troubleshooting

Therefore, when fresh markers reach Log Analytics but cannot be retrieved through CLI or either live interface for multiple applications, open an Azure support request under Azure Container Apps.

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

Hi @Jesper Clausen ,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

The most important observation is that your Log Analytics workspace (law-lrisssquyjg3y) is still receiving log entries, while both the Log stream and the Aspire Dashboard stopped showing data around the same time. This is a useful clue because these features use different data pipelines.

• Log stream displays your application's console output (stdout/stderr).

Aspire Dashboard relies on OpenTelemetry (OTel) telemetry.

Since both became blank together, this could either be a platform-side live streaming issue or a configuration/deployment change. To identify which one it is, could you please perform the following checks?
Step 1: Verify that new console logs are still reaching Log Analytics

Generate some activity in your application and log a unique message using your existing ILogger, for example:

LOGPROBE-20260730

Wait approximately 10–15 minutes, then run the following query in Log Analytics:

ContainerAppConsoleLogs_CL
| where ContainerAppName_s == "mgtservice"
| where TimeGenerated > ago(30m)
| order by TimeGenerated desc

What to check:

• If you see the LOGPROBE-20260730 message, your application is still sending console logs successfully.
• If no recent records appear, the application may no longer be writing to stdout/stderr.

Step 2: Test live log streaming using Azure CLI

Please run the following commands:

az containerapp logs show --name mgtservice --resource-group <your-resource-group> --type console --follow

az containerapp logs show --name mgtservice --resource-group <your-resource-group> --type system --tail 50

While these commands are running, access your application's endpoint to generate traffic.

Also, in the Azure portal Log Stream page, verify that:

The correct revision, replica, and container are selected.

The application has not scaled down to zero replicas.

What to check:

• If console logs appear, the streaming pipeline is working.
• If only System logs appear but Console logs do not, that provides an important clue about where the issue exists.

Step 3: Create a new revision (only if Steps 1 and 2 indicate a streaming issue)

If new logs are reaching Log Analytics but live streaming still does not work, create a new revision by updating an environment variable:

az containerapp update --name mgtservice --resource-group <your-resource-group> --set-env-vars LOGREBIND=20260730

Then verify that a new revision has been created:

az containerapp revision list --name mgtservice --resource-group <your-resource-group> -o table

After the new revision becomes active, check whether Log Stream starts displaying console logs again.

Note: Please perform this step only after completing Steps 1 and 2, as creating a new revision may remove useful evidence if this turns out to be a platform-side issue.

Step 4: Verify Aspire Dashboard (OpenTelemetry) configuration

Since the Aspire Dashboard depends on OpenTelemetry, please verify that:

AddServiceDefaults() is still configured.

Your OpenTelemetry (OTLP) exporter configuration has not changed.

If you recently introduced Serilog, confirm that it has not replaced the default ILogger pipeline, as this can prevent structured logs from appearing in the Aspire Dashboard.

After redeploying, generate some application traffic and check whether data appears in the Structured Logs and Traces sections of the Aspire Dashboard.

If your test log appears in Log Analytics but no logs stream through the Azure CLI, especially if this affects multiple Container Apps in the same environment, it is likely pointing to a platform-side live streaming issue. In that case, we can investigate further and determine whether an Azure Container Apps support request would be the appropriate next step.

I look forward to your update.

If the assistance was helpful, kindly take a moment to click on Accept Answer and click on Yes. It will be helpful for other community members.

The cae--lrisssquyjg3y is configured to use Azure Log Analytics for the correct Resource group and use the mentioned Log Analytics workspace law-lrisssquyjg3y and Enable Aspire Dashboard.