Skip to content
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

Closed
2 of 9 tasks
brooksmtownsend opened this issue Jun 7, 2024 · 4 comments · Fixed by #2266
Closed
2 of 9 tasks

[BUG] OTEL traces/logs get constant 404s after otlp upgrade #2265

brooksmtownsend opened this issue Jun 7, 2024 · 4 comments · Fixed by #2266
Assignees
Labels
bug Something isn't working

Comments

@brooksmtownsend
Copy link
Member

Affected project(s)

  • documentation
  • examples
  • wasmCloud host
  • wasmCloud CLI (wash)
  • wasmCloud dashboard UI (washboard)
  • capability providers
  • provider bindgen
  • control interface client
  • other / not sure

Describe the bug

In the console when running the wasmCloud host from main, or any providers built from main, I get the following output constantly as direct console output (not formatted with our logs):

OpenTelemetry trace error occurred. HTTP status client error (404 Not Found) for url (http://localhost:4318/)
OpenTelemetry log error occurred. HTTP status client error (404 Not Found) for url (http://localhost:4318/)
OpenTelemetry trace error occurred. HTTP status client error (404 Not Found) for url (http://localhost:4318/)

Steps to reproduce

  1. checkout main
  2. Launch the OTEL docker compose under examples/docker
  3. cargo run -- --enable-observability
  4. See errors

Expected behavior

I expected for the default tracing/logging endpoints to keep working as before.

Environment

  • OS: [e.g. Linux, MacOS] MacOS
  • Shell [e.g. bash, zsh, powershell] zsh
  • wasmcloud Version [e.g. 0.81.0] 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

@brooksmtownsend brooksmtownsend added the bug Something isn't working label Jun 7, 2024
@brooksmtownsend
Copy link
Member Author

As a workaround I've been able to test using our override endpoints.

./wasmcloud --override-traces-endpoint http://localhost:4318/v1/traces --override-logs-endpoint http://localhost:4318/v1/logs

joonas added a commit to joonas/wasmCloud that referenced this issue Jun 7, 2024
…oints

Fixes wasmCloud#2265

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
joonas added a commit to joonas/wasmCloud that referenced this issue Jun 10, 2024
…oints

Fixes wasmCloud#2265

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
joonas added a commit to joonas/wasmCloud that referenced this issue Jun 10, 2024
…oints

Fixes wasmCloud#2265

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
joonas added a commit to joonas/wasmCloud that referenced this issue Jun 10, 2024
…oints

Fixes wasmCloud#2265

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
@joonas joonas self-assigned this Jun 10, 2024
joonas added a commit to joonas/wasmCloud that referenced this issue Jun 10, 2024
…oints

Fixes wasmCloud#2265

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
joonas added a commit to joonas/wasmCloud that referenced this issue Jun 11, 2024
…oints

Fixes wasmCloud#2265

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
github-merge-queue bot pushed a commit that referenced this issue Jun 11, 2024
…oints

Fixes #2265

Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
@peter-jerry-ye
Copy link
Contributor

I'm somehow still experiencing this using the docker-compose-full.yml in the repository. Shouldn't it been fixed?

@vados-cosmonic
Copy link
Contributor

@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?

@peter-jerry-ye
Copy link
Contributor

@vados-cosmonic It's different in that I used the docker file directly or with endpoint http://otelcol:4318/ and they both gave me 404, which is exactly as described in this issue.

I'm not sure if we are expected to add /v1/entry? I thought it was just a hacking solution and the document (though might be outdated: https://wasmcloud.com/docs/reference/host-config) didn't mention it.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants