Merged RPC spans not correctly shown, multi value tags not shown about jaeger-ui

[tiffon]

@pavolloffay Thanks for reporting this.

I tested things out with the JSON you linked. I was able to reproduce the behavior.

• merged RPC spans are now shown (symbol ->)

Not sure this is an error. The parent span does not have the span.kind: client tag, it has (multiple) span.kind: server.

@yurishkuro, can you weigh in?

• multi value tags are not shown

This is a bug that should be resolved in PR #53.

[yurishkuro]

in fact the very first span has span.kind tags with both server and client values. How did that happen? It looks like an instrumentation issue where the child span was not started for downstream call, so the parent server the span was tagged as a client.

[pavolloffay]

in fact the very first span has span.kind tags with both server and client values. How did that happen? It looks like an instrumentation issue where the child span was not started for downstream call, so the parent server the span was tagged as a client.

It's correct OT instrumentation with brave-ot. Maybe it's some brave magic... I wanted to check this again but the link to JSON is not valid anymore.