Are we sure we don't want support non W3C cases too?

Well for non-W3C TraceId is going to spit out00000000000000000000000000000000 and SpanId is going to spit out0000000000000000. We could just pushActivity.Id into the events which would includeW3C,Hierarchical, and (presumably) anything added in the future. BUT. AccessingActivity.Id will force an allocation in the process being monitored. And it will force consumers to have to inspect the value and understand the possible formats/differences. Probably also the consumers will have to chop up theId into the individual components. In my world of OTel I don't need hierarchical but if you feel there is a need and the tradeoffs are OK, I'm happy to switch it.

We have been supporting theHierarchical cases with external logger scopes.

Also, will it make sense to add the parent Id to the event as we do in scopes?

CC@noahfalk if he has more insight if we should ignore theHierarchical cases or not.

Just FYI the reason I went withActivityTraceId,ActivitySpanId, andActivityTraceFlags is because those are the only things defined on the OTel Logs Data Model for correlation:https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#log-and-event-record-definition

Happy to add other things, but from OTel perspective they aren't required.

I'd be fine omitting support for hierarichal. Worst case I forsee is we get feedback that someone wants Hierarichal support, we decide the scenario in the request is important and then we add that too in a future release. I think that has a pretty low chance of happening.