open-telemetry/opentelemetry-dotnet

[otlp] UseOtlpExporter and AddOtlpExporter extensions don't play nice together

Open

#5,538 opened on Apr 16, 2024

View on GitHubContributor guide
 (4 comments) (5 reactions) (0 assignees)C# (889 forks)auto 404
help wantedpkg:OpenTelemetry.Exporter.OpenTelemetryProtocol

Repository metrics

Stars
 (3,725 stars)
PR merge metrics
 (Avg merge 3d 17h) (112 merged PRs in 30d)

Description

In 1.8.0 we introduced the UseOtlpExporter extension which will turn on OtlpExporter for all signals. If UseOtlpExporter is called more than once, or AddOtlpExporter is called in addition, exceptions will be thrown:

This was intentionally done but some users have run into issues:

Opening this issue to track the demand for changing the behavior.

Contributor guide

Research direction
Review the linked pull request and comments to understand user scenarios. Examine the restrictions in the source code and propose a change that allows multiple calls or combination of UseOtlpExporter and AddOtlpExporter without exceptions.
Tech stack
csharp
Domain
observabilitybackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NETOpenTelemetry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55