Francis Bogsanyi

In Ruby, we have implemented a similar mechanism using Context to [propagate attributes to HTTP client spans](https://github.com/open-telemetry/opentelemetry-ruby/blob/main/common/lib/opentelemetry/common/http/client_context.rb). We've also implemented this for Redis client spans. An example use from the...

Thanks @mmontalvo - no updates on this yet - we'd ❤️ your contributions! I've assigned this issue to you.

@mmontalvo are you still working on this?

> I know in OTel Ruby the concept of an "ID Generator" is directly in the opentelemetry-api package, but the specification describes Id Generator as only an SDK concept, not...

@mwear [commented](https://github.com/open-telemetry/opentelemetry-ruby/pull/280#discussion_r445213387): > +1 on wanting a helper. TBH, I like the first option better, because the second implicitly couples the Trace module to W3C trace context. Both are wordy,...

Discussed in the SIG meeting: * have an `opentelemetry-common` gem for common helpers (http response code to status, semantic conventions, etc.) -- this should only depend on API * have...

Thanks @rydzykje - I've assigned this to you.

This issue is specifically about EC2, but we'd be happy to see contributions around any of those environments. If it's a ton of work to support all the environments, then...

The consensus in [OTEP 100](https://github.com/open-telemetry/oteps/pull/100) is that this mechanism will be provided in the collector but not necessarily in-process for all languages.

See the review comments on that issue to get a better sense of what the community is thinking about here.