Nikita Salnikov-Tarnovski
Nikita Salnikov-Tarnovski
Just a note: this problem can _also_ be solved by doing #1298
I agree that there are a lot of open questions about Resources. But I also agree with Bogdan that making `InstrumentationLibrary` available to Samplers is not controversial, is useful and...
@Oberon00 I want to have `InstrumentationLibrary` available to Samplers by doing https://github.com/open-telemetry/opentelemetry-specification/pull/1658#issuecomment-847958368. Are you Ok with me picking the corresponding part of that PR of yours and make a new...
> I'd be happy to reopen #1658 as-is if we now have found a good use case, if @iNikem agrees? But probably you had reasons for just proposing Resources. My...
During Maintainers meeting on 20-09-2021 @jmacd expressed his opinion that we should move to configuration-time decisions of configuring SDK and/or `Tracers` with the correct `Samplers`: all decisions based on `Resources`...
But resources are immutable? How decisions can be changed based on immutable resources?
> it may be enough to send the "current" time with each request, so the receiver can calculate the offset between the current time of the sender and it's own...
We don't usually change accepted OTEPs. Such changes as this can go directly to Spec repo
We had much more agreement on removing current status code, than on its replacement. So we want to remove Google RPC code bases status before GA, that is what my...
@mwear Should this be closed in favor of #136 ?