[Bug]: HTTP status client error (404 Not Found) after upgrade to 0.23

[frederikhors]

What happened?

If I upgrade these:

- opentelemetry = { version = "0.22.0", default-features = false, features = [
+ opentelemetry = { version = "0.23.0", default-features = false, features = [
    "trace",
] }
- opentelemetry-otlp = { version = "0.15.0", default-features = false, features = [
+ opentelemetry-otlp = { version = "0.16.0", default-features = false, features = [
    "http-proto",
    "reqwest-client",
    "reqwest-rustls",
] }
- opentelemetry_sdk = { version = "0.22", default-features = false, features = [
+ opentelemetry_sdk = { version = "0.23", default-features = false, features = [
    "rt-tokio",
] }
- tracing-opentelemetry = { version = "0.23.0", default-features = false }
+ tracing-opentelemetry = { version = "0.24.0", default-features = false }

I get the error:

OpenTelemetry trace error occurred. HTTP status client error (404 Not Found) for url (https://otlp.uptrace.dev/).

These are the only changes in the code.

Why the error?

API Version

0.23

SDK Version

0.23

What Exporter(s) are you seeing the problem on?

OTLP

Relevant log output

No response

[frederikhors]

I opened this too: uptrace/uptrace#385.

[cijothomas]

https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/CHANGELOG.md#fixed
Default grpc endpoint will not have path based on signal(e.g /v1/traces) #1706

Maybe the above ?
(Unfortunately, the changelog is not very clear about the impact....)

[imWildCat]

any news?

or any possible fixes?

[frederikhors]

@cijothomas did you find a way?

[jaymell]

@imWildCat @frederikhors Have you tried appending /v1/traces to your tracing URLs? I believe that will fix the issue. This is unfortunately the second time this functionality has been changed/broken in recent releases.

[frederikhors]

/v1/traces

Yeah. It works with that string.

[imWildCat]

@imWildCat @frederikhors Have you tried appending /v1/traces to your tracing URLs? I believe that will fix the issue. This is unfortunately the second time this functionality has been changed/broken in recent releases.

yes. I can confirm this will fix!

thank you!