Sponsored Keynote: Datadog - Every Byte Counts: How Protocol Design Shapes the Cost...
summary
Telemetry volumes grow about 35% year over year for the average enterprise, driving ingestion, storage and especially egress costs. A new protocol, OTAP (OpenTelemetry Arrow Protocol) built on Apache Arrow uses stateful streaming and columnar encoding to avoid re-sending metadata and benchmarks show a 20–40% payload reduction versus OTLP with standard compression. OTAP is experimental, reduces bytes sent across regions, but requires long‑lived streams and extra operational complexity and uneven Arrow support across languages.
AI-written summary · about
related talks
32mThe Invisible Tax: How Data Format Conversions Drive up Telemetry Pipeline Costs
27mIngesting 6.5 Tb of Telemetry Data Daily Through Open Telemetry Protocol and Collectors
24mScaling Telemetry To Terabytes: Applying Google's Principles To OpenTelemetry...
13mLightning Talk: Taming Metric Cardinality: Practical Cost Reduction Wit...
36mObservability For You and Me with OpenTelemetry
30mBut Wait! There's...Still More‽ - Observability Data Volumes and Strategies for Managing Them
26mScaling OpenTelemetry for Modern Workloads: From Mobile To Ma...
32mTaming the Cost of Telemetry: How Riot Games Reined In...