-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] OTEL traces/logs get constant 404s after otlp upgrade #2265
Comments
As a workaround I've been able to test using our override endpoints.
|
…oints Fixes wasmCloud#2265 Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
…oints Fixes wasmCloud#2265 Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
…oints Fixes wasmCloud#2265 Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
…oints Fixes wasmCloud#2265 Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
…oints Fixes wasmCloud#2265 Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
…oints Fixes wasmCloud#2265 Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
…oints Fixes #2265 Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
I'm somehow still experiencing this using the |
@peter-jerry-ye is this possibly a duplicate of #2839 ? How many of those messages are you getting versus how many providers do you have running? |
@vados-cosmonic It's different in that I used the docker file directly or with endpoint I'm not sure if we are expected to add I got two messages and 0 providers. I just spin up the docker compose and deployed nothing else to it. It's kinda the first few messages that complained the error to me. |
Affected project(s)
Describe the bug
In the console when running the wasmCloud host from
main
, or any providers built frommain
, I get the following output constantly as direct console output (not formatted with our logs):Steps to reproduce
cargo run -- --enable-observability
Expected behavior
I expected for the default tracing/logging endpoints to keep working as before.
Environment
main
Screenshots / Logs / Additional context
I don't think this is technically a bug in the upstream otlp crate, it was just a breaking change that wasn't documented well enough for us to catch it from the changelog. open-telemetry/opentelemetry-rust#1866
Introduced in #2197 so this hasn't been released in any providers/the host
The text was updated successfully, but these errors were encountered: