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

Jump to bottom

Fail fast when unsecure channel is not configured correctly in .NET 3.1 #2690

Closed
tomkerkhove opened this issue Nov 26, 2021 · 0 comments · Fixed by #2691
Closed

Fail fast when unsecure channel is not configured correctly in .NET 3.1 #2690

tomkerkhove opened this issue Nov 26, 2021 · 0 comments · Fixed by #2691
Labels
enhancement New feature or request

Comments

@tomkerkhove
Copy link
Contributor

Feature Request

Is your feature request related to a problem?

Yes, unsecured channels must be configured correctly in .NET 3.1 but is not surfaced at runtime.

Describe the solution you'd like:

Fail fast when creating an OTLP export client when the unsecured channel is not configured correctly.

Describe alternatives you've considered.

Add logging.

Additional Context

Learn more about this requirement in the docs - https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md#special-case-when-using-insecure-channel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
1 participant
@tomkerkhove