V2 Migration - ChildOf deprecated, but what is the solution for tracer.SpanContexts?

[J7mbo]

The V2 migration instructions show that parent.StartChild should be used instead of tracer.ChildOf(parent).

This works fine when you have two spans and you just want to make a span the child of another one.

However, some spans come from non-go code, such as a kafka event, or an async process. They are extracted with tracer.Extract, which returns a tracer.SpanContext.

I don't see any way to, given this tracer.SpanContext, either specify that a new Span in the go tool is a child of this given that it's not a Span, it's a SpanContext, or somehow convert that SpanContext into a Span so that it can be set as a parent with the new v2 API.

Can someone shed some light on the right way forward here?

[darccio]

@J7mbo Sorry for the late answer. We were already discussing this in #3598, and we are working on a proposal.

[J7mbo]

Thanks a lot for getting back to us anyway 🙏