> ## 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 Telemetry

> Choose the right ingestion path for container stdout logs, metrics, and traces from Azure Container Instances, using an OpenTelemetry Collector sidecar.

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 Collector as a sidecar. A same-group application normally uses `localhost:4317` for OTLP/gRPC or `localhost:4318` for OTLP/HTTP; use the actual receiver address and security settings when your configuration differs. The Collector forwards all three signals to Bronto.

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)