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

> Choose the right ingestion path for pod logs, kubelet metrics, control plane logs, and traces from Azure Kubernetes Service with a Collector DaemonSet.

AKS workloads emit pod logs and application telemetry, while the kubelet exposes node, pod, container, and volume metrics. Control-plane logs are exported through Azure Monitor diagnostic settings.

## Recommended method

[**Self-Managed OTel Collector**](./azure-otel#self-managed-opentelemetry-collector) — deploy the Collector as a DaemonSet to collect pod logs, kubelet metrics, and application telemetry. See [Kubernetes logs and metrics](/integrations/kubernetes) for the Helm preset and RBAC requirements.

For **Windows node pools**, run the Collector DaemonSet on the Windows nodes (the `opentelemetry-collector-contrib` image ships the Windows receivers) to collect Windows Event Log and IIS logs — see [Collecting Windows OS Logs](./azure-windows-logs).

## Alternatives

* [**Azure Event Hub Forwarder**](./azure-client) — required path for AKS control plane / diagnostic logs, which are exported through Azure Monitor diagnostic settings to an Event Hub.

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

## References

* [Monitor Azure Kubernetes Service](https://learn.microsoft.com/en-us/azure/aks/monitor-aks)