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

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

Closed
EMUNES opened this issue Aug 29, 2024 · 2 comments

Comments

@EMUNES
Copy link

EMUNES commented Aug 29, 2024

I found this error when testing the example axum_oltp. I have deployed jaeger on docker following this repo's instruction. However, it reports this error on port 4318, which is the OLTP http port.

I found a possible related issue about this here. But I have no idea how to make configurations for this crate to fix this problem.

Logs:

     0.000634300s DEBUG otel::setup::resource: key: telemetry.sdk.version, value: 0.23.0
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\resource.rs:65 on main

     0.001000700s DEBUG otel::setup::resource: key: service.name, value: unknown_service
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\resource.rs:65 on main

     0.001283100s DEBUG otel::setup::resource: key: os.type, value: windows
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\resource.rs:65 on main

     0.001464200s DEBUG otel::setup::resource: key: telemetry.sdk.language, value: rust
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\resource.rs:65 on main

     0.001596900s DEBUG otel::setup::resource: key: telemetry.sdk.name, value: opentelemetry     
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\resource.rs:65 on main

     0.001811600s DEBUG otel::setup: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT: "http://localhost:4318" 
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\otlp.rs:31 on main

     0.001987100s DEBUG otel::setup: OTEL_EXPORTER_OTLP_TRACES_PROTOCOL: "http/protobuf"
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\otlp.rs:32 on main

     0.003359400s DEBUG otel::setup: OTEL_TRACES_SAMPLER: "parentbased_always_on"
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\otlp.rs:115 on main

     0.003868100s DEBUG otel::setup: OTEL_PROPAGATORS: "tracecontext,baggage"
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\init-tracing-opentelemetry-0.19.0\src\lib.rs:59 on main

Error:

   366.797249200s TRACE otel::tracing: close, time.busy: 1.37ms, time.idle: 432µs
    at C:\Users\HZB\.cargo\registry\src\index.crates.io-6f17d22bba15001f\tracing-opentelemetry-instrumentation-sdk-0.19.0\src\http\http_server.rs:13 on tokio-runtime-worker
    in otel::tracing::HTTP request with http.request.method: GET, network.protocol.version: 1.1, server.address: "127.0.0.1:7999", user_agent.original: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36", url.path: "/", url.scheme: "", otel.name: GET, otel.kind: Server, span.type: "web", http.route: "/", otel.name: "GET /", http.response.status_code: 200

OpenTelemetry trace error occurred. HTTP status client error (404 Not Found) for url (http://localhost:4318/)
@davidB
Copy link
Owner

davidB commented Aug 31, 2024

I don't know which crates you talk (they are several on this repo), but configuration could be done by environment variables a subset of https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/ (also look at the names in uppercase in the log above)

@EMUNES
Copy link
Author

EMUNES commented Sep 13, 2024

This error does not occur after updating to the newest packages.

@EMUNES EMUNES closed this as completed Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants