I’ve always found it confusing when people talk of telemetry having a tracing library.
Technically it can work. Either use the pdict or pass the current span context as part of the metadata to each execute and then use events start_span and end_span to create/finish children.
That is, I don’t think spans should be considered and treated like events.
And then Telemetry really starts to just be an alternative to OpenCensus, hehe, but with a different philosophy of being vendor neutral. Telemetry tracing would delegate to other libraries like telemetry stats do (so like ex_ray or New Relic) while OpenCenus works to create a common core.
Anyway, I see Telemetry events as perfect for adding attributes and time events (https://opencensus.io/tracing/span/time_events/annotation/) to existing spans and was planning to have it plug in to OpenCensus tracing that way.
