Skip to main content
Amazon EKS workloads emit pod logs and application telemetry, while the kubelet exposes node, pod, container, and volume metrics. Control-plane logs are written to CloudWatch by AWS. ADOT — deploy the Collector as a DaemonSet on EC2 node groups to collect pod logs (filelog) and application telemetry. On Fargate, use a per-pod sidecar because DaemonSets cannot run there. ADOT doesn’t include the kubeletstats receiver, so for kubelet metrics use the contrib or k8s Collector distribution as described in Kubernetes logs and metrics.

​
Alternatives

  • Fluent Bit on EKS — DaemonSet that collects container logs from every node; lighter than a full collector.
  • Self-Managed OTel Collector — full control over the OpenTelemetry pipeline when ADOT’s distribution doesn’t fit.
  • CloudWatch Log Forwarder — required path for EKS control plane logs, which are CloudWatch-only.
  • Amazon Data Firehose — EKS Auto Mode managed-component logs and EKS Capabilities logs (Argo CD, ACK, kro) can be delivered as vended logs to Firehose and on to Bronto. Control plane logs still go to CloudWatch only.
See Ingesting AWS Data into Bronto for the full service-to-method mapping.

​
References