HotROD traces display without trace name

[yurishkuro]

@tiffon I just tried the latest UI and saw this

[yurishkuro]

This could be a server-side issue, the root span doesn't look right, span reference with traceID=0 is invalid

        {
          "traceID": "3fb3f396b13217b",
          "spanID": "3fb3f396b13217b",
          "flags": 1,
          "operationName": "HTTP GET /dispatch",
          "references": [
            {
              "refType": "CHILD_OF",
              "traceID": "0",
              "spanID": "0"
            }
          ],

[tiffon]

I've been running the latest UI with a prior all-in-one and haven't noticed the issue. I'll confirm, though.

[yurishkuro]

I'm pretty sure it's an issue on the server, when I use memory store I see it getting spans with above reference (traceID==0, invalid). I'm still looking where exactly it's being added, by the client or the server enrichment.

[yurishkuro]

Confirmed that the issue is in the Go client (jaegertracing/jaeger-client-go#242) that sends a bad reference {"refType":"CHILD_OF","traceIdLow":0,"traceIdHigh":0,"spanId":0} when baggage is provided externally to the root span.

[tiffon]

Is there a change necessary in the UI?

[yurishkuro]

no, just the backend - jaegertracing/jaeger#614