New component: OTel-Arrow Exporter and Receiver

[jmacd]

The purpose and use-cases of the new component

The OpenTelemetry Arrow project has been donated to OpenTelemetry, as described here:
open-telemetry/community#1332

This donation included two components, an exporter and receiver, which (as the donation states) are intended to live in the contrib repository. These components have been developed across two repositories:

1. https://github.com/open-telemetry/otel-arrow houses the producer and consumer "adapter" library and the tooling that was built to debug and qualify the primary OTel Arrow components
2. https://github.com/open-telemetry/otel-arrow-collector houses the original branch history as the core OTLP exporter and receiver components were modified to produce the corresponding OTel-Arrow components.

Example configuration for the component

For the receiver, no configuration is necessary. Like the OTLP exporter, but gRPC is presumed, thus nothing to configure.

receivers:
  otelarrow:

For the exporter, (like the OTLP exporter), endpoint and tls are usually set:

  otelarrow/insecure:
    endpoint: agent.local:4317
    tls:
      insecure: true

Telemetry data types supported

Traces, Logs and Metrics.

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

@codeboten

Sponsor (optional)

jmacd, gramidt

Additional context

The OTel Arrow protocol was researched and documented in this OTEP.

[jmacd]

This project has sponsorship, as described in the Arrow community donation, open-telemetry/community#1332. I am acting as the @open-telemetry/technical-committee sponsor. The recommendation to include these components in contrib is taken from open-telemetry/community#1332 (comment),

The Arrow-based protocol implementations in the Collector should be added as a dedicated contrib receiver and exporter instead of being incorporated in the OTLP receiver and exporter.

Thank you for reviewing. I have updated the CODEOWNERS to refer to @open-telemetry/arrow-approvers which includes currently members of the two donating organizations. Interested in contributing? Join us at open-telemetry/otel-arrow.

[codeboten]

@jmacd i'm happy to sponsor the component. Just for future reference, component sponsors are required to be approvers of the repository. See https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components

Who's the sponsor for your component. A sponsor is an approver who will be in charge of being the official reviewer of the code and become a code owner for the component.

[jmacd]

@moh-osman3 are you willing to be named as CODEOWNER?
@lquerel are you willing to be named as CODEOWNER? (Even better, IMO, would be for F5 to delegate a new collector maintainer, including a replacement for its current f5cloudexporter owner who has left the company.)

[moh-osman3]

Yes happy to be a codeowner for these components. Thanks @jmacd!

[lquerel]

@jmacd I am checking internally to see if we have someone for the role of collector maintainer. If not, I will volunteer.

[jmacd]

There is an open question in open-telemetry/otel-arrow#43