Ben Sigelman

Re the X-Trace paper: my understanding was that the top-left operation would record just the one piece of metadata, and that the `pushNext` and `pushDown` therein would be considered their...

@adriancole I agree completely that RPCs can and probably should be rendered as a single row in a conventional zipkin/dapper-style UI... yet from a data modeling perspective there is still...

(cc @jmacd who cares about this... also @yurishkuro who brought this up in the [opentracing.io PR](https://github.com/opentracing/opentracing.io/pull/189#issuecomment-283952766) cited above) @objectiser thank you for bringing this up. I like the idea of...

> I think we need to consider batching as a separate issue (Agreed) > So maybe the issue really is, whether the application needs to provide guidance to the tracer...

@yurishkuro IMO the situation you described isn't something to be modeled with span references... I would imagine that each mobile span would be tagged with a `driver_id` or `session_id` or...

@yurishkuro I guess I don't see it that way... rather than having each trace refer to the previous one, it seems more natural (at least to my brain) to have...

@yurishkuro I see. So I think the key differentiator here is that you are talking about an actual *Span* for the mega-trace in that there's a specific start time and...

@lookfwd sorry for the delay, having a crazy week. The primary value prop around interoperation of Tracers is not actually so that an org can necessarily switch from one tracing...

Well, the importer thing works, at least to a first approximation... I'll give people a few days to say "STOP STOP TERRIBLE IDEA" before doing this for all non-documentation issues...

Well, the migration tool was a total fail. It has lots of soft-errors and was only partially migrating issues. I decided to just do them manually. :-/ Sad times. But...