You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we add it automatically when calling AddOpenTelemetry() as a cross cutting exporter using UseOtlpExporter().
If later signal specific calls add it using AddOtlpExporter they will get an exception.
Unhandled exception. System.NotSupportedException: Signal-specific AddOtlpExporter methods and the cross-cutting UseOtlpExporter method being invoked on the same IServiceCollect
ion is not supported.
I personally think it be better if this was a NOOP if the AddOtlpExporter does not throw on repeated invocations if the configuration matches the already configured OTLP exporter.
We'll need to investigate if we think this is possible and a good idea and then propose this upstream.
The text was updated successfully, but these errors were encountered:
Right now we add it automatically when calling
AddOpenTelemetry()
as a cross cutting exporter usingUseOtlpExporter()
.If later signal specific calls add it using
AddOtlpExporter
they will get an exception.Mpdreamz/opentelemetry-demo@b5ae9bf.
I personally think it be better if this was a NOOP if the
AddOtlpExporter
does not throw on repeated invocations if the configuration matches the already configured OTLP exporter.We'll need to investigate if we think this is possible and a good idea and then propose this upstream.
The text was updated successfully, but these errors were encountered: