> ## 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 Instances Logs and Traces

> Choose the right ingestion path for container logs and distributed traces from Azure Container Instances (ACI).

Azure Container Instances emits container `stdout` / `stderr` logs and — when your applications are instrumented with OpenTelemetry — distributed traces. Containers in the same container group share a network namespace, so a collector can run alongside your app as a sidecar.

## Recommended method

[**Self-Managed OTel Collector**](./azure-otel#self-managed-opentelemetry-collector) — run the OpenTelemetry Collector as a sidecar container within the same container group. Your application exports OTLP to `localhost:4317` (gRPC) or `localhost:4318` (HTTP), and the collector ships logs and traces to Bronto. Use the same `service.name` / `service.namespace` routing as your other OTel workloads (see [Data Organization](/Search-and-Visualize/Partitions)).

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

## References

* [Retrieve container logs and events in Azure Container Instances](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-log-analytics)