Julian Tescher

In addition to what @fraillt mentioned, I would also recommend not having the `root` span that lives for the entire lifetime of the program. Jaeger cannot show spans before they...

Closing for now, feel free to re-open if you run into more issues.

I think @djc was moving some of https://github.com/vivint-smarthome/opentelemetry-stackdriver over, could work out what the best path forward is for that. I think either way the contrib crate is probably the...

@TommyCpp good point, can be done separately if they only have an exporter. Looks like contrib is still the right place for the propagator either way according to [the propagators...

@djc I think having a top level crate works as well for common exporters like aws/gcp, having more niche exporters like newrelic/datadog at the top level could become a maintenance...

Could consider having both constants, you should be able to use [Key::as_str](https://docs.rs/opentelemetry/latest/opentelemetry/struct.Key.html#method.as_str) as a workaround to check equality as well.

@TommyCpp I haven't looked to much into it, but that sounds reasonable to me

@djc good point, is there a better beta convention?

Should be soon hopefully, just have to resolve the MSRV issues on main

@open-telemetry/rust-approvers should we wait for the current open PRs to land? or merge this sooner than that.