Jaeger v2 query trying to hit localhost:4317 to send traces to otlp grpc port

[RishithReddyRR]

Whenever jaeger query v2 is been hit to see traces in UI getting following error
{"level":"warn","ts":"2026-04-23T09:41:19.245Z","caller":"grpc@v1.79.3/clientconn.go:1525","msg":"[core] [Channel #1 SubChannel #5] grpc: addrConn.createTransport failed to connect to {Addr: "[::1]:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "transport: Error while dialing: dial tcp [::1]:4317: connect: connection refused"","resource":{"service.instance.id":"063f9213-2c01-4c4d-8201-94d6eefd72fd","service.name":"jaeger","service.version":""},"grpc_log":true}
is there any configuration to disable telemetry traces?
@dosu

[dosubot[bot]]

@RishithReddyRR those warnings are from Jaeger v2's internal self-tracing — the query service uses the OpenTelemetry SDK to trace itself, and by default it tries to export to localhost:4317. These errors are non-fatal and don't affect your actual trace collection.

To disable this, set these environment variables:

OTEL_TRACES_EXPORTER=none
OTEL_SDK_DISABLED=true

Or if you just want to stop sampling without fully disabling the SDK:

OTEL_TRACES_SAMPLER=always_off

These are standard OpenTelemetry SDK environment variables that Jaeger v2 respects [1] [2].

Alternatively, if you have another Jaeger/OTLP collector running, you can point the internal telemetry to it with OTEL_EXPORTER_OTLP_ENDPOINT=http://<your-collector>:4317 instead of disabling it entirely.

To reply, just mention @dosu.

^{Static docs are dead. Try Dosu.
Leave Feedback · Ask Dosu about jaeger · Share Dosu with your team}

[RishithReddyRR]

@dosu so by using OTEL_TRACES_EXPORTER=none,OTEL_SDK_DISABLED=true envs it only disable telemetry traces that is it right no other telemetry like metrics

[dosubot[bot]]

@RishithReddyRR correct — OTEL_TRACES_EXPORTER=none only disables trace exporting for Jaeger's internal self-telemetry. It does not affect metrics or logs. The OpenTelemetry SDK controls each signal independently [1].

OTEL_SDK_DISABLED=true is broader — per the OpenTelemetry spec, it disables the entire SDK, which would affect traces, metrics, and logs for Jaeger's internal telemetry.

So if you only want to suppress the trace export errors while keeping internal metrics intact, just use:

OTEL_TRACES_EXPORTER=none

without OTEL_SDK_DISABLED=true.

Either way, none of these affect the traces your applications send to Jaeger — they only control Jaeger's own self-observability [2].

To reply, just mention @dosu.

^{Knowledge infrastructure for agents and humans
Leave Feedback · Learn about jaeger with Dosu · Add Dosu to your team}