> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bronto.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Container Apps Logs and Traces

> Choose the right ingestion path for console logs, system logs, and distributed traces from Azure Container Apps.

Azure Container Apps emits console (`stdout` / `stderr`) logs and system logs from your containers, and — when your applications are instrumented with OpenTelemetry — distributed traces.

## Recommended method

[**Self-Managed OTel Collector**](./azure-otel#self-managed-opentelemetry-collector) — run the OpenTelemetry Collector as its own container app and have your apps export OTLP to it, or instrument each app with the [OpenTelemetry SDK](/opentelemetry/overview) to export to Bronto directly. Either way, telemetry reaches Bronto over OTLP/HTTP. Use the same `service.name` / `service.namespace` routing as your other OTel workloads (see [Data Organization](/Search-and-Visualize/Partitions)).

<Note>
  The Container Apps environment's built-in managed OpenTelemetry agent exports only over OTLP/gRPC, which Bronto's ingestion endpoint does not accept — so it can't deliver to Bronto directly. Use a Collector container or direct SDK export instead.
</Note>

## Alternatives

* [**Azure Event Hub Forwarder**](./azure-client) — for Container Apps platform / diagnostic logs exported through Azure Monitor diagnostic settings.

See [Ingesting Azure Data into Bronto](./azure-overview) for the full service-to-method mapping.

## References

* [Collect and read OpenTelemetry data in Azure Container Apps](https://learn.microsoft.com/en-us/azure/container-apps/opentelemetry-agents)