open-telemetry/opentelemetry-dotnet

[bug] UseOtlpExporter is not respecting services.Configure<OtlpExporterOptions> but AddOtlpExporter does

Open

#6,231 opened on Apr 4, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C# (889 forks)auto 404
bughelp wantedpkg:OpenTelemetry.Exporter.OpenTelemetryProtocol

Repository metrics

Stars
 (3,725 stars)
PR merge metrics
 (PR metrics pending)

Description

Package

OpenTelemetry.Exporter.OpenTelemetryProtocol

Package Version

Package Name Version
OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11.2
OpenTelemetry 1.11.2

Runtime Version

net8.0

Description

UseOtlpExporter() is not respecting services.Configure<OtlpExporterOptions> Endpoint

Steps to Reproduce

  1. Configure non-default Endpoint via e.g., environment variable OpenTelemetry__OtlpExporter__Endpoint
  2. services.Configure<OtlpExporterOptions>(ctx.Configuration.GetSection("OpenTelemetry:OtlpExporter"));
  3. services.AddOpenTelemetry().UseOtlpExporter()

Expected Result

UseOtlpExporter is respecting services.Configure<OtlpExporterOptions> Endpoint

Actual Result

Connecting with default URL

Exception: {1}{http://localhost:4317/opentelemetry.proto.collector.metrics.v1.MetricsService/Export}{System.Net.Http.HttpRequestException: Connection refused (localhost:4317)
 ---> System.Net.Sockets.SocketException (111): Connection refused

...but when separately adding AddOtlpExporter then Endpoint setting is read correctly.

Additional Context

No response

Contributor guide

Research direction
Investigate the difference in how UseOtlpExporter and AddOtlpExporter handle the IOptions pattern. UseOtlpExporter may not be picking up the configuration from services.Configure<OtlpExporterOptions> because it creates a new instance or uses a different scope.
Tech stack
csharpopentelemetry
Domain
backendapiobservability
Issue type
Bug
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.
60