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

> Choose the right ingestion path for application logs, web server logs, and distributed traces from Azure App Service.

Azure App Service emits application logs (your code's `stdout` output), HTTP / web server logs, and platform diagnostic logs, and — when your application is instrumented — distributed traces. App Service does not run a node-level agent, so application telemetry is best emitted directly from the app.

## Recommended method

[**OpenTelemetry SDK**](/opentelemetry/overview) — instrument the application with the vendor-neutral OpenTelemetry SDK and configure the OTLP exporter to send logs and traces to Bronto, either directly or through a [Collector](./azure-otel#self-managed-opentelemetry-collector) running on a VM, AKS, or a Container App. Use the same `service.name` / `service.namespace` routing as your other OTel workloads (see [Data Organization](/Search-and-Visualize/Partitions)).

## Alternatives

* [**Azure Monitor OpenTelemetry Distro**](./azure-monitor-otel-distro) — if you already use Application Insights, you can forward the same logs and traces to Bronto as well.
* [**Azure Event Hub Forwarder**](./azure-client) — for App Service 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

* [Enable diagnostics logging for apps in Azure App Service](https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-diagnostic-logs)