Cijo Thomas
Cijo Thomas
> If we find out that it is really not possible to follow to the specification by default, I think we should try to extend the specification to handle duplicate...
Excellent discussion. Overall, the plan was always to continue offer a callback so as to let app owners deal with failures, if they want to, and provide a default callback...
As per the most recent spec, there is no ability to change temporality on a per instrument basis, so this issue is only to specify the aggregation itself, along with...
Removing this from the upcoming 1.4.0 milestone. This is less important, so far haven't seen any asks for this capability.
Already support the ability to configuration for the Aggregation itself (like pick tags, change boundaries for histogram etc.)
Unstale. This is spec requirement.
The "spec_unstable_logs_enabled" feature flag needs to be removed completely. All methods/code should be enabled always. Do this for `opentelemetry`, `opentelemetry_sdk`, `opentelemetry-appender-tracing` and `opentelemetry-appender-log` crates. Also update changelog.md file for all...
`reqwest-blocking` should be used by default. (`reqwest` cannot be used with the default periodic_reader). I'll see what doc gaps we have, and address them shortly.
OTel SDK uses a dedicated own thread for BatchLog/SpanProcessor and for PeriodicReader - inside this thread, it does blocking calls (hence the need for reqwest-blocking). Yes shutdown can be done...
https://github.com/open-telemetry/opentelemetry-dotnet/pull/4141/files need similar for ResourceDetectors too.