[Bug]: Jaeger all in one connection refused when setting `collector.otlp.grpc.host-port` about jaeger HOT 5 CLOSED

The port setting you're changing affects where collector listens for OTLP. You did not provide any indication that it's not working for traces submitted externally. The internal errors are coming up because Jaeger uses OTEL SDK internally and sends the traces back to itself, at the default port 4317. You need to pas another env var that is recognized by the SDK to indicate the new location of the OTLP endpoint.

from jaeger.

I did further tests as you suggested with:

services:
  jaeger:
    image: jaegertracing/all-in-one:1.54.0
    environment:
      COLLECTOR_OTLP_GRPC_HOST_PORT: :14317
      LOG_LEVEL: debug
    ports:
      - 14317:14317
      - 16686:16686

  telemetry-gen:
    depends_on:
      - jaeger
    image: ghcr.io/open-telemetry/opentelemetry-collector-contrib/telemetrygen:latest
    command:
      - traces
      - --otlp-insecure
      - --otlp-endpoint=jaeger:14317
      - --duration=30s
      - --workers=4
      - --rate=4

The Web ui is accessible and the traces generated by telemetrygen are visible.

What's left if the error message generated by the collector.

You need to pas another env var that is recognized by the SDK to indicate the new location of the OTLP endpoint.

Indeed setting the variable OTEL_EXPORTER_OTLP_ENDPOINT or OTEL_EXPORTER_OTLP_TRACES_ENDPOINT to http://localhost:14317 fix the error message.

But I would have expected those value to be set when I pass COLLECTOR_OTLP_GRPC_HOST_PORT or --collector.otlp.grpc.host-port

from jaeger.

But I would have expected those value to be set ...

I don't know, I can see pros and cons. Curious why you need to change the port in the first place - since you running Jaeger it its own container, you can map its internal port to anything else externally, while the internal span exports would still be sent to the default port and continue to work.

from jaeger.

Closing as I don't think it's worth the added complexity

from jaeger.

Curious why you need to change the port in the first place

I was trying to troubleshoot why the traces I was generating was displayed on Jaeger

Closing as I don't think it's worth the added complexity

I understand, if it cannot be done automatically, can the step setting `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` to the correct value be documented on the troubleshoot section ?

from jaeger.