[Bug]: Jaeger v1.59 doesn't accept OpenTelemetry data on ports 4317/4318

[mpbnkg]

See this ticket for more info - open-telemetry/opentelemetry-collector-contrib#33995

What happened?

When I try to export metrics to jaeger via OTLP collector it fails with the following error. What is causing this given the fact that it was working a few weeks back?

2024-07-09T18:35:39.864Z info exporterhelper/retry_sender.go:118 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "traces", "name": "otlp", "error": "rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 172.25.0.2:4317: connect: connection refused"", "interval": "3.136185958s"}

[PedemonteGiacomo]

Yes I have the same problem that we have already discussed here.

With older image version like the 1.58 of the jaeger-all-in-one it works fine.

[yurishkuro]

Most likely due to recent OTEL Collector change to default receivers to use localhost instead of 0.0.0.0. There is an upstream issue to revert this change open-telemetry/opentelemetry-operator#3126

The workaround is to pass host IP explicitly to Jaeger, e.g. via these env variables, as in this fix:

      - COLLECTOR_OTLP_GRPC_HOST_PORT=0.0.0.0:4317
      - COLLECTOR_OTLP_HTTP_HOST_PORT=0.0.0.0:4318

Alternatively, refer to OTEL guidelines https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks

[mpbnkg]

@yurishkuro Yep, it works when I added those two lines :)

[yurishkuro]

In the next release we are going back to listening on all IPs.

[matthewgrossman]

FYI, this env-based workaround discussed in this issue wasn't working for me; no services external to my jaeger container could send (gRPC) traces to 4317. I noticed in this https://github.com/jaegertracing/jaeger/pull/6134/files that you can do settings overrides, which did work for me:

docker run --rm --name jaeger \
  -p 16686:16686 \
  -p 4317:4317 \
  jaegertracing/jaeger:2.0.0 \
  --set=receivers.otlp.protocols.grpc.endpoint="0.0.0.0:4317"

Not sure if this is a regression for 2.0, or if this is just expected behavior now that jaeger has more settings parity with the otel-collector