Closed timhabermaas closed 3 years ago
This fix should be verifiable by using Jaeger's all-in-one Docker image (https://www.jaegertracing.io/docs/1.18/getting-started/#all-in-one) and pointing Zipkin
s settingsHostname
to localhost
and settingsPort
to 9411
.
With the Content-Type set all seems to be working fine when sending data to Jaeger. Including tags and annotations (called events in Jaeger):
Thanks for the PR @timhabermaas and apologies for the slow reply. I wasn't getting notifications from this repo and am just going through the PRs now. I think this was fixed by https://github.com/mtth/tracing/pull/3.
Without the Content-Type Jaeger (tested using version 1.18) responded with "Unsupported Content-Type":