search

opentracing-contrib / java-spring-jaeger

Apache License 2.0
257 stars 95 forks source link

Library generating 256bit traceId #59

Open dbsheta opened 5 years ago

dbsheta commented 5 years ago

I deployed few services in a k8 cluster and was surprised to see that no traces were visible in jaeger. On checking app logs, I found that traceId being generated was 256 bits long like: "f397a1768f8a0e5a4955c4cdfeda67c3"

However, on an old cluster I have the same services deployed for which I am able to see traces in jaeger and which have 128 bit long trace Ids. For eg. "d64800f409abf213"

We checked all our network and infra configurations. All are the same for both services. Can a 256bit traceId be causing issue for jaeger?

geoand commented 5 years ago

cc @pavolloffay

pavolloffay commented 5 years ago

Who is generating traceIds? The traceIds are max 128bit in jaeger.

dbsheta commented 5 years ago

The library itself is generating. Since we wanted traceId in our app logs, we created an interceptor, where we get traceId using the OpenTracing API and put it in MDC. The 256bit Span ID I mentioned above is an actual traceId generated by the library visible in our app logs. But when we search in Jaeger, we couldn't find any trace

pavolloffay commented 5 years ago

The library itself is generating.

I might be missing something here. What library do you mean? Jaeger java client?