Why do we need IOptionsMonitor in OpenTelemetry?

[bwn-z]

Hello everyone!

I have a problem. We want to work with IOptionsSnapshot/IOptionsMonitor in the service. I am stuck on the integration with OpenTelemetry. I saw the pr: https://github.com/open-telemetry/opentelemetry-dotnet/pull/3662/files but I don't quite understand how it should work?

We use AddOtlpExporter

My case:

1. I thought that IOptionsMonitor support is in OpenTelemetry
2. I started the service locally
3. I executed some logic
4. I saw traces and metrics in kibana Elk
5. I change the endpoint for the exporter in the settings. I expect hotReload for this configuration
6. I expect that the new settings will be applied immediately or after a default time - 2 minutes for cached clients. And I will not see traces and metrics in kibana
7. In fact, nothing changes, the new settings are not applied. traces and metrics are flying, which means the new address for Otlp was not applied

What am I doing wrong? Please tell me

configure.AddOtlpExporter(opt => configuration.GetSection("OtlpExporterOptions").Bind(opt));

I also look at the client code: https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/Implementation/ExportClient

There is no support for IOptionsMonitor, why is it needed then?

[bwn-z]

@CodeBlanch Hi! If it's not too much trouble, could you please give me some advice on this issue?