stdout / stderr logs from your workloads and — when your applications are instrumented with OpenTelemetry — distributed traces. AKS clusters also emit control plane logs (API server, audit, scheduler, controller manager); those are exported through Azure Monitor diagnostic settings rather than collected by an in-cluster agent.
Recommended method
Self-Managed OTel Collector — deploy the OpenTelemetry Collector on AKS via the OpenTelemetry Helm chart to collect pod logs and application traces and ship them over OTLP to Bronto. Run it as a DaemonSet for node-level log collection, or as a Deployment for centralised collection. Use the sameservice.name / service.namespace routing as your other OTel workloads (see Data Organization).
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.
Alternatives
- Azure Event Hub Forwarder — required path for AKS control plane / diagnostic logs, which are exported through Azure Monitor diagnostic settings to an Event Hub.