Fix default Jaeger collector endpoint

[pellared]

Why

The current default value of the Jaeger collector endpoint is wrong as it points to gRPC endpoint. See: https://www.jaegertracing.io/docs/1.22/getting-started/

What

Set the default endpoint to :14268/api/traces as suggested in https://www.jaegertracing.io/docs/1.22/apis/#thrift-over-http-stable

Testing

I started Jaeger like this:

$ docker run -d --name jaeger \
  -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \
  -p 5775:5775/udp \
  -p 6831:6831/udp \
  -p 6832:6832/udp \
  -p 5778:5778 \
  -p 16686:16686 \
  -p 14268:14268 \
  -p 14250:14250 \
  -p 9411:9411 \
  jaegertracing/all-in-one:1.22

And created little program to set the exporter and make a sample span.

[codecov]

Codecov Report

Merging #1898 (edd3030) into main (1e3fa3a) will decrease coverage by 0.0%.
The diff coverage is 100.0%.

@@           Coverage Diff           @@
##            main   #1898     +/-   ##
=======================================
- Coverage   79.4%   79.4%   -0.1%     
=======================================
  Files        139     139             
  Lines       7418    7418             
=======================================
- Hits        5894    5892      -2     
- Misses      1278    1280      +2     
  Partials     246     246             

Impacted Files	Coverage Δ
exporters/trace/jaeger/uploader.go	50.6% <100.0%> (ø)
exporters/trace/jaeger/jaeger.go	93.4% <0.0%> (-1.1%)	⬇️

[MrAlias]

This looks good. Can you update the otel-collector to use this endpoint as well?

[pellared]

This looks good. Can you update the otel-collector to use this endpoint as well?

I can take a look in the following days.

[pellared]

@MrAlias It looks like everything is fine in OTel Collector:

• https://github.com/open-telemetry/opentelemetry-collector/blob/e3c294708464fd4f2babcd3d5bdf583abc0631e8/receiver/jaegerreceiver/trace_receiver.go#L452
• https://github.com/open-telemetry/opentelemetry-collector/blob/03c7bf98f7edf6e578aac303e4d8b767f117541e/examples/k8s/otel-config.yaml#L168

[MrAlias]

@pellared I was referrering to:

• opentelemetry-go/example/otel-collector/k8s/otel-collector.yaml

  Line 37 in 79d9852

  endpoint: "jaeger-collector.observability.svc.cluster.local:14250"

• https://github.com/open-telemetry/opentelemetry-go/blame/79d9852e96b0b4abe1818a905773d203b087bbf2/example/otel-collector/README.md#L134

But, on second look, it looks like this is actually using the collector's gRPC exporter for Jaeger. So nothing to actually change.