Zhongyang Wu

It may not be a problem with datadog exporter. Could you share a more detailed example of how you configure the tracer provider? Or maybe try using some other exporters...

It feels like a communication problem with the datadog collector. I noticed you are sending spans to `http://localhost`. Is that expected?

Thanks for the bug report. I did try to reproduce this bug locally. Here is [my current setup](https://github.com/TommyCpp/opentelemetry-rust/tree/674/examples/datadog). Here is my approach: You mentioned the default reqwest async client is...

Currently, we only have `tonic` based implementation for metrics exporters. `http-proto` support will be added later

Yeah, I agree there is a gap on how to set `BatchConfig` for the batch span processors. Currently only way to do it is to build your own span processor...

This issue should have been fixed by #869 and released as part of 0.18

Since the metrics spec has been stabilized. We are looking to migrate the existing implementation onto the stable spec. In the stable metric spec. This can be achieved via [Histogram](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#histogram)...

@Alexx-G I am working on creating some issue to lay out our road map on metrics. It will take some time to implement it. So if many users need those...

I believe we have fixed it in https://github.com/open-telemetry/opentelemetry-rust/pull/818. Once the new version is released it should be fixed. Meanwhile, maybe we can try to backport this to 0.17? cc @jtescher...

> Does `opentelemtry-otlp` already add the signal path automatically when using gRPC? gRPC doesn't really require a path, right? The service/client stub should take care of that