Julian Tescher

@djc need a 👍 to merge 😄

I like the idea of more fully supporting the trace-context spec, the interaction for the text map propagator is fairly explicit in [the propagators spec](https://github.com/open-telemetry/opentelemetry-specification/blob/3f07b6669dbbf4625579b5a0f371768f50788cd2/specification/context/api-propagators.md#textmap-propagator) which is a little unfortunate,...

Could consider creating a crate with macros to help here, similar to how [tracing-attributes](https://github.com/tokio-rs/tracing/tree/master/tracing-attributes) allows you to have a more ergonomic async API.

This has been resolved in #848

Any chance of this getting resolved? Running into the same issues.

@kevincox unfortunatley I don't believe that this is possible with the current [opentelemetry sampling spec](https://github.com/open-telemetry/opentelemetry-specification/blob/28d02cc310d9c789b5faac58f9939bf735adadb5/specification/trace/sdk.md#shouldsample), the only data you are given access to is the parent context, you would have...

> Is there a way to add information to the context when processing a span so that it can be fetched from the parent context when processing the child span?...

Closing this for now as metrics have been rewritten. Feel free to re-open if the issue occurs again.

This config has now been removed

#897 has been released in #1156