no more spans sent with 1.6.1

[vincentserpoul]

Description

I realized a few days ago my spans were not sent anymore, I thought there was an error on my side, tried to tune things for a few days, to no avail.

Environment

• OS: linux
• Architecture: x86
• Go Version: 1.16, 1.18
• opentelemetry-go version: v1.6.1
• collector: opentelemetry collector installed via the helm chart (0.46)

Steps To Reproduce

I decided to go back to basics

1. Clone the opentelemetry-go repo main branch
2. cd to the example lying in the repo.
3. go mod tidy, go run main.go > spans are sent
4. remove all the replace in go.mod, go mod tidy, go run main.go > spans are not sent anymore
5. re-add the replace of the main oltptrace in go.mod

replace go.opentelemetry.io/otel/exporters/otlp/otlptrace => ../../exporters/otlp/otlptrace

spans are sent.

Expected behavior

importing the otlptrace@v1.6.1 doesn't seem to work properly.

[alexrudd]

Think I've also just hit this. Reverted to 1.5 and everything is working again.

[Aneurysm9]

Can you provide information about what collector and OTLP proto version you are using? Please also see #2769 (comment) for some details about changes to the OTLP protocol and how they're (supposed to be) handled by this exporter and the collector.

[Aneurysm9]

We have released v1.6.2 which should mitigate issues that can arise with the use of the OTLP proto v0.15.0 and any prior SDK release. Can you please verify that your data flow is as expected with v1.6.2?

[vincentserpoul]

it is now flowing, thank you for the very short reaction time!

[enosi-rl]

I hit the same problem yesterday and spent too much time debugging the AWS side (tracing is in lambda's) before seeing the new release and landing on this issue.

v1.6.1 and the 0.48 release of the collector produced no spans with silent failure.

Thanks for the quick fix.