Issue: ContainerAppConsoleLogs_CL Not Visible in Data Export Rule

Question

Issue: ContainerAppConsoleLogs_CL Not Visible in Data Export Rule

Cobarrubias, Ian Luis 0

I’m trying to forward Azure Container Apps logs to Event Hub so they can be consumed by Dynatrace (Azure Logs Forwarder).

In Log Analytics, I can see:

ContainerAppConsoleLogs_CL

ContainerAppSystemLogs_CL

They are actively receiving logs and their type is:

Custom table (classic)

However, when creating a Data Export rule, these tables do not appear in the list of selectable tables.

From what I understand, Data Export only supports Analytics tables, not classic custom (_CL) tables.

Questions:

Is it correct that classic custom tables cannot be exported via Data Export rules?

Is there a supported way to convert or migrate these tables to Analytics type?

Is recreating the Container Apps Environment the only way to enable export to Event Hub?

The goal is to forward Container Apps logs to Event Hub for Dynatrace integration.

Any clarification would be appreciated.

0 comments

2 answers

Your answer

Answer 1

Hello Cobarrubias, Ian Luis,

Below is a clarification of the current behavior and the supported options.

Export of classic custom tables via Data Export

Your understanding is correct. Azure Monitor Data Export supports only Analytics and Basic table types. The Container Apps console and system logs are stored in classic custom Log Analytics tables (_CL), which are not supported for Data Export, and therefore do not appear in the selectable list.

Converting or migrating these tables to Analytics

There is no in-place conversion from classic custom tables to Analytics-supported tables.

The supported approach is to:

Create a new table using modern ingestion (DCR-based / custom log v2)
Re-ingest logs into this new export-supported table
Configure Data Export → Event Hub from the new table

Requirement to recreate the Container Apps Environment

Re-creating the environment is not strictly mandatory, but in many cases it becomes the most practical path because:

Current Container Apps diagnostics commonly write to classic custom tables (_CL)

These tables cannot be exported through Data Export

Enabling export typically requires logs to land in Analytics/modern custom tables, which may involve environment reconfiguration or recreation

Supported options to forward logs to Event Hub for Dynatrace

Recommended (fully supported, near real-time):

Configure logging to use modern ingestion (DCR / CLv2 or Analytics table)

Use Log Analytics Data Export → Event Hub → Dynatrace

Workaround:

Use a Logic App or Azure Function to periodically query the _CL tables and forward results to Event Hub
This introduces latency and additional cost, so it is suitable only as a temporary solution.

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

Praveen Kumar Gudipudi 2,275 Reputation points Microsoft External Staff Moderator

2026-02-16T08:04:55.0833333+00:00

Hello Cobarrubias, Ian Luis,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Cobarrubias, Ian Luis 0 Reputation points

2026-03-31T14:50:06.54+00:00

Hi @Praveen Kumar Gudipudi ,
Apologies, it's been a while. I have been trying different ways to send our logs, and I'm now able to push logs from Container Apps Environment to Event Hub using steps below:

Update the logging options to Azure Monitor by going to Monitoring -> Logging Options -> Logs Destination

Configure Diagnostic Settings to forward logs to both Logs Analytics Workspace and Event Hub. Under the Logs section, select the Container App Console logs.

The ContainerAppConsoleLogs table should then be available in the Log Analytics Workspace, and the logs should also be delivered to Event Hub in batches.

I noticed that there is a10-minute delay before logs appear in both Log Analytics Workspace and Event Hub after changing the logging options to Azure Monitor. Would you be able to confirm if this is a normal behavior?
Praveen Kumar Gudipudi 2,275 Reputation points Microsoft External Staff Moderator

2026-04-02T15:32:29.3733333+00:00

Hello Cobarrubias, Ian Luis,

Yes — the ~10-minute delay you observed after enabling Azure Monitor logging for Azure Container Apps is expected behavior.

Answer 2

Yes, you are correct that classic custom tables (like those ending in _CL) cannot be exported via Data Export rules. The Data Export feature in Azure Monitor only supports Analytics tables, not classic custom tables.

As for converting or migrating these tables to Analytics type, there is no direct method mentioned in the provided context for doing so. Recreating the Container Apps Environment might be one approach to enable the export to Event Hub, but this is not explicitly stated as the only way.

For your goal of forwarding Container Apps logs to Event Hub for Dynatrace integration, you may need to explore other options or configurations that allow for the use of Analytics tables instead.

References:

Share via

Issue: ContainerAppConsoleLogs_CL Not Visible in Data Export Rule

2 answers

Your answer