Jaeger Exporter Configurations issue #2215
Closed
wmashal
announced in
Community Discussions
Replies: 2 comments 2 replies
-
That might be the wrong port, try 4317 or 4318 |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I find the issue I just drop the istio proxy from my Jaeger and changed the endpoint port in the configurations to 4317 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
When I am configuring the opentelemetry in my k8s cluster using the "otel/opentelemetry-collector-contrib:0.103.1" in deployment mode with the following jaeger exporter configurations but I got errors (see below) when the collector trying to export the traces so as a workaround I am using zipkin to send my traces to Jaeger
The Original Configurations
The workaround in traces exporter I am using zipkin
The Error
Beta Was this translation helpful? Give feedback.
All reactions