~/talk

Telemetry Colosseum: OTel Collector vs. Fluent Bit v5 vs. OTel-Arrow....

slides:none on file

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

  1. 0:00Introduction and disclaimer
  2. 2:07Introducing the three gladiators
  3. 3:51OTLP vs OTel Arrow protocol
  4. 7:18Design comparison of tools
  5. 11:11Logs processing capabilities
  6. 14:01Metrics handling features
  7. 15:46Traces support and sampling
  8. 17:10Benchmark setup and environment
  9. 18:12CPU and memory consumption results
  10. 20:20OTel Arrow protocol efficiency
  11. 21:22Network consumption analysis
  12. 22:23Final recommendations and conclusion
  13. 23:07Call to action and Q&A
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.