Zhongyang Wu

I think the issue lie with `reqwest-tracing` create, which priovides a middle layer to create a child span for HTTP calls. ``` let client = ClientBuilder::new(reqwest::Client::new()) .with(TracingMiddleware::::new()) .build(); ``` But...

By default the propgation on the `POST` span should be included automatically by the middleware(as we didn't use `DisableOtelPropagation` extension here)

Yep I can open the issue on their side. I also want to construct some examples between rust client and rust server to help investigation

> Tagging another maintainer, @TommyCpp, to see if this is just my account. Can confirm I don't have access to manage the account in teams

> The next release, which is planned for June 30 2024, is expected to update status of https://github.com/open-telemetry/opentelemetry-rust/issues/1733, https://github.com/open-telemetry/opentelemetry-rust/issues/1719 to Beta. Huh I thought the next release will be end...

> `build_body` Not exactly for the http exporter but in `opentelemetry-proto` we have this test https://github.com/open-telemetry/opentelemetry-rust/blob/e98c61ce73865b56917695dc0ab89ba3eca6c454/opentelemetry-proto/tests/json_deserialize.rs

> It seems that having a single default protocol is the source of the confusion. Yeah I think it's reasonable to rely on features if the user didn't provide any...

> Are we ok to pick `http-json` in that case? Or should we `require` the protocol to be specified when building the pipeline for `http`? Yeah I think it's OK...

> How can I test that parent ID is set correctly? You can replace the OTLP exporter with stdout exporter ```rust let exporter = opentelemetry_stdout::SpanExporterBuilder::default().build(); ``` This will print the...

Proposed changes in 5/21 community calls ``` TracerProvider::tracer_builder("tracer_name") // advanced scenario. .with_instrutation_library(InstrumentationLibrary::default().version(XXX).schema_url(xxxx)) .build(); ```