Skip to content
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.

Zipkin exporter not working towards /v2 jaeger collector endpoint #133

Closed
ekarlso opened this issue Mar 25, 2019 · 3 comments
Closed

Zipkin exporter not working towards /v2 jaeger collector endpoint #133

ekarlso opened this issue Mar 25, 2019 · 3 comments

Comments

@ekarlso
Copy link

ekarlso commented Mar 25, 2019

Start Jaeger

docker run -d --name jaeger   -e COLLECTOR_ZIPKIN_HTTP_PORT=9411   -p 5775:5775/udp   -p 6831:6831/udp   -p 6832:6832/udp   -p 5778:5778   -p 16686:16686   -p 14268:14268   -p 9411:9411   jaegertracing/all-in-one:1.11```

Run the example zipkin or anything alike and Jaeger will give http 400 back. I got this via Wireshark when using the example TestZipkin.cs
@ekarlso
Copy link
Author

ekarlso commented Mar 25, 2019

With zipkin's docker image it seems you get 404 also.

@rstraszewski
Copy link

rstraszewski commented Mar 26, 2019

I've also been trying this today, and had similar problem. I received 400. The problem is with ipv6 - zipkin exporter is trying to send spans with ipv6 with scope ID (part with percent in the end) and Jaeger is rejecting this with error:
Unable to process request body: wrong ipv6

@SergeyKanzhelev
Copy link
Member

moved to OpenTelemetry

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants