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

> Choose the right ingestion path for function execution logs, host logs, and distributed traces from Azure Functions.

Azure Functions emits function execution logs (your code's output), host logs, and — when instrumented — distributed traces. The right ingestion path depends on whether you want application telemetry emitted directly from the function or the Function App's platform logs.

## Recommended method

[**OpenTelemetry SDK**](/opentelemetry/overview) — instrument the function 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). 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) — Function App logs streamed through Azure Monitor diagnostic settings are automatically assigned to a dedicated collection and dataset by the forwarder.

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

## References

* [Use OpenTelemetry with Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/opentelemetry-howto)