Kafka consumer spans are coming as HTTP endpoints in Service Call View as can be seen in the following pictures:
Full Trace Containing Producer and Consumer Spans:
The consumer spans shows as a new Endpoint Span:
The first question is that should the consumer span be treated as a new trace? Currently, to see the consumer span, we have to expand the full trace. Otherwise, they don't see the consumer span. Jaeger on the other hand, shows it has a child of the producer span (although it's not a child technically as it's a fire-and-forget call).
Further, Hypertrace is treating these spans as HTTP spans while they're not. So you get these useless fields like status and url.
Kafka consumer spans are coming as HTTP endpoints in Service Call View as can be seen in the following pictures:
Full Trace Containing Producer and Consumer Spans:
The consumer spans shows as a new Endpoint Span:
The first question is that should the consumer span be treated as a new trace? Currently, to see the consumer span, we have to expand the full trace. Otherwise, they don't see the consumer span. Jaeger on the other hand, shows it has a child of the producer span (although it's not a child technically as it's a fire-and-forget call).
Further, Hypertrace is treating these spans as HTTP spans while they're not. So you get these useless fields like
status
andurl
.