You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This post is a case-study about the performance of the OpenTelemetry Protocol with Apache Arrow exporter and receiver pair, which we have been running in production for one year.
This follows our earlier post, https://opentelemetry.io/blog/2023/otel-arrow/, with a real experience report from putting the Exporter and Receiver (now included in the Collector-Contrib repository) into production following the project donation to OpenTelemetry.
In this post, we explain the basic mechanisms that the Exporter and Receiver use to achieve reliable performance in addition to the stated compression benefits. The data show performance consistent with our earlier benchmarks and we consider our original results to be validated. This post says: the OTel-Arrow components are ready for general use.
This post is a case-study about the performance of the OpenTelemetry Protocol with Apache Arrow exporter and receiver pair, which we have been running in production for one year.
This follows our earlier post, https://opentelemetry.io/blog/2023/otel-arrow/, with a real experience report from putting the Exporter and Receiver (now included in the Collector-Contrib repository) into production following the project donation to OpenTelemetry.
In this post, we explain the basic mechanisms that the Exporter and Receiver use to achieve reliable performance in addition to the stated compression benefits. The data show performance consistent with our earlier benchmarks and we consider our original results to be validated. This post says: the OTel-Arrow components are ready for general use.
SIG: OTel-Arrow
Sponsor: @lquerel
The text was updated successfully, but these errors were encountered: