OpenTelemetry.Exporter.OpenTelemetryProtocol support

[cijothomas]

As discussed in this issue, the 1.0 version of OpenTelemetry.Exporter.OpenTelemetryProtocol will not support secure channel (no https allowed).

Releases upto 1.0.0-rc2 allowed user to configure Credentials, GrpcChannelOptions, thereby allowing user to setup secure channel. This functionality is removed in 1.0.0-rc3 (and 1.0.0)

The plan is to release 1.1 soon, with proper support for secure channel. The exact mechanism of allowing configuration could be one of the following:

1. Options as per the spec https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md, including in-flight spec changes: Add configuration for client TLS auth and rename variable for trusted… opentelemetry-specification#1375
2. Bring back pre 1.0.0-rc2 model where user had ability to configure Grpc channel (via GrpcChannelOptions/Credentials)
3. A combination of the above
4. New model using the concept of a ConnectionString.

This post will be updated when the pre-release versions of 1.1 is released.
Please share any concerns/feedback in the original issue.

[cijothomas]

There is a PR (#1795) which might help with addressing this in 1.0 itself.

[cijothomas]

Basic support for TLS is merged as per 1795. Ability to support custom certificate file is planned to post 1.0 release.