Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Blog Post: Announcing OpenTelemetry Protocol with Apache Arrow - Phase 2 #6410

Open
jmacd opened this issue Feb 24, 2025 · 0 comments
Open
Labels

Comments

@jmacd
Copy link
Contributor

jmacd commented Feb 24, 2025

The OpenTelemetry Protocol with Apache Arrow project would post a project update as we embark on Phase 2 of the project. This post will be the third in a series, preceded by:
https://opentelemetry.io/blog/2023/otel-arrow/
https://opentelemetry.io/blog/2024/otel-arrow-production/

OTel-Arrow Phase 2 (as originally described in the OTEP, in the donation) will investigate an end-to-end pipeline for OpenTelemetry data using Apache Arrow data frames as the pipeline data representation. We anticipate that using OpenTelemetry Protocol with Apache Arrow (OTAP) instead OTLP as the intermediate representation will result in substantial savings, lower CPU and memory usage across the entire pipeline. We will experiment with writing new, column-oriented processing logic for OpenTelemetry data.

We choose the Rust language for this project due to its popularity in the Apache Arrow ecosystem. We are specifically interested in using the Apache DataFusion project's embedded query engine as a component in OpenTelemetry pipelines.

We will investigate the use of an OTAP-first OpenTelemetry-Rust SDK. We are specifically interested in using the OpenTelemetry Weaver project to generate type-safe bindings for exporting into an OTAP pipeline.

The blog post will summarize these points and remind users that they can contribute, where to find us, and so on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant