Warning: this is an oversimplification. Performance optimization and being able to "plug in" to the data ecosystem that Apache Arrow exists in. OpenTelemetry

Warning: this is an oversimplification. Performance optimization and being able to "plug in" to the data ecosystem that Apache Arrow exists in. OpenTelemetry is pretty great for a lot of uses, but the protocol over the wire is too chunky for some applications where. From last year's post on the topic[0]: > In a side-by-side comparison between OpenTelemetry Protocol (“OTLP”) and OpenTelemetry Protocol with Apache Arrow for similarly configured traces pipelines, we observe 30% improvement in compression. Although this study specifically focused on traces data, we have observed results for logs and metrics signals in production settings too, where OTel-Arrow users can expect 50% to 70% improvement relative to OTLP for similar pipeline configurations. For your average set of apps and services running in a k8s cluster somewhere in the cloud, this is just a nice-to-have, but size on wire is a problem for a lot of systems out there today, and they are precluded from adopting OpenTelemetry until that's solved. [0]: https://opentelemetry.io/blog/2024/otel-arrow-production/ https://opentelemetry.io/blog/2024/otel-arrow-production/