Telemetry Colosseum: OTel Collector vs. Fluent Bit v5 vs. OTel-Arrow....
summary
Three agents (OTel Collector, Fluent Bit v5, OTel‑Arrow) run under identical Kubernetes conditions and five trials compare design, signal support, self‑observability, and performance. Fluent Bit excels on logs and low CPU for many loads; Collector wins overall today with broad plugin support; OTel‑Arrow shows ~80x reduction in network packets when using OTAP but needs an extra Collector for OTLP apps, which raises CPU/memory. Missing features slow Arrow adoption: missing plugins: file reader, kube metadata, Prometheus scrape, sampling, and benchmarks run on Kubernetes with 2‑hour ramp to 200 users. All configs and results go to GitHub.
AI-written summary · about
chapters (13)
- 0:00Introduction and disclaimer
- 2:07Introducing the three gladiators
- 3:51OTLP vs OTel Arrow protocol
- 7:18Design comparison of tools
- 11:11Logs processing capabilities
- 14:01Metrics handling features
- 15:46Traces support and sampling
- 17:10Benchmark setup and environment
- 18:12CPU and memory consumption results
- 20:20OTel Arrow protocol efficiency
- 21:22Network consumption analysis
- 22:23Final recommendations and conclusion
- 23:07Call to action and Q&A
