use latest OTEL collector and switch Jaeger to OTLP protocol#1
Conversation
|
hi is this PR ok to use already? thanks! |
|
Yes, I've used this for some development without issues. |
| jaeger: | ||
| endpoint: jaeger-all-in-one:14250 | ||
| otlp/jaeger: | ||
| endpoint: jaeger-all-in-one:4317 |
There was a problem hiding this comment.
why there is a change in port? I guess they have purposefully kept it 14250 to support nextJS framework.
There was a problem hiding this comment.
Frankly I don't know the nextJS framework.
New Jaeger versions support the OTLP protocol natively, and use that for communication with the OTEL collector, while in older version the collector used the Jaeger protocol to talk to Jaeger.
This port is not supposed to be seen or used by the observer application.
There was a problem hiding this comment.
Great fix. For further context: https://opentelemetry.io/blog/2023/jaeger-exporter-collector-migration/
|
I'm trying to use this one but logs aren't showing up. could you please point me to any repo link? |
4 participants
No description provided.