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.

Sign up for GitHub

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

OTel Arrow blog drive-by copyedits #5268

Merged
merged 1 commit into from
Sep 30, 2024
Merged

OTel Arrow blog drive-by copyedits #5268

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/blog/2023/otel-arrow/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,8 @@ repository that supports this protocol. This protocol, designed to complement
the OTLP protocol in situations with substantial telemetry data volumes, has
been under discussion and development for two years. It represents a
collaborative effort between [F5](https://f5.com),
[ServiceNow Cloud Observability](https://www.servicenow.com/products/observability.html)
, and numerous technical leaders from the OpenTelemetry community (see
[ServiceNow Cloud Observability](https://www.servicenow.com/products/observability.html),
and numerous technical leaders from the OpenTelemetry community (see
[donation](https://github.com/open-telemetry/community/issues/1332)). The
compression benefits are significant, demonstrating a **40% improvement
compression efficiency** for the majority of workloads and even greater
Expand Down
15 changes: 7 additions & 8 deletions content/en/blog/2024/otel-arrow-production/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,9 @@
title: OpenTelemetry Protocol with Apache Arrow in Production
linkTitle: OpenTelemetry Arrow in Production
date: 2024-09-25
author:
>- # If you have only one author, then add the single name on this line in quotes.
[Joshua MacDonald](https://github.com/jmacd) (ServiceNow, Inc), [Laurent
Querel](https://github.com/lquerel) (F5, Inc)
author: >-
[Joshua MacDonald](https://github.com/jmacd) (ServiceNow), [Laurent
Querel](https://github.com/lquerel) (F5)
Comment on lines +6 to +7
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmacd - we don't typically include "Inc" like qualifiers in blog post credentials, neither did you in your 2023 post, so I stripped them (FYI).

cSpell:ignore: Querel Zstd
issue: 5193
sig: OpenTelemetry Arrow
Expand Down Expand Up @@ -54,8 +53,8 @@ OpenTelemetry Collectors.
The compression bridge consists of two OpenTelemetry Collectors labeled exporter
and receiver, or they could equally be two pools of load-balanced collectors.

As described in this
["OTEP" design document](https://github.com/open-telemetry/oteps/blob/main/text/0156-columnar-encoding.md#mapping-otel-entities-to-arrow-records),
As described in the
[OTEP 0156 design document](https://github.com/open-telemetry/oteps/blob/main/text/0156-columnar-encoding.md#mapping-otel-entities-to-arrow-records),
the exporter converts arbitrary OpenTelemetry data into an Arrow record batch.
The Arrow record batch is a block of memory, with a standardized layout, making
it possible to exchange data across address spaces and virtual process
Expand Down Expand Up @@ -224,7 +223,7 @@ giving them an opportunity to retry on another connection, and it gives the
service operator a chance to auto-scale the number of instances to handle the
increase in load based on memory utilization.

See the
For details, see the
[documentation on batching and back-pressure](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/otelarrowexporter/README.md#batching-configuration)
for the OTel-Arrow exporter.

Expand All @@ -246,7 +245,7 @@ the OpenTelemetry standard OTLP over gRPC, with round-robin load balancing. The
gateway collectors apply a variety of processors, including the concurrent batch
processor described above, followed by the OTel-Arrow exporter.

![A pool of gateway collectors sends to a load balancer, then to a backend service.](./setup.png)
![A pool of gateway collectors sends to a load balancer, then to a backend service.](setup.png)

On the other side of the bridge, a pool of Envoy load balancers distributes the
streams across a pool of collectors running the OTel-Arrow receiver, after
Expand Down