Zipkin transformation to support resource and instrumentation scope attributes

[ysolomchenko]

Relates to open-telemetry/opentelemetry-dotnet#5936

What are you trying to achieve?

So, there will be two ways to set tags(Span.Attributes):

• Adding tags directly to the Activity(Span)
• Adding tags via ActivitySource(Tracing Provider (or Tracer))

We should specify which of these has higher priority.

Additional context.

OpenTelemetry to Zipkin Transformation

I'm happy to update the documentation in a follow-up PR, but I need clarification on which source should take precedence and how collisions should be handled.

[mx-psi]

From triage session on 2025-04-07 this is related to #2535 (probably a sub-issue of this?). Since the parent issue needs a sponsor, we are labeling this one in the same way.

We would also like to reword this in terms of the specification-level concepts, since ActivitySource and Activity are .NET specific. Could you reword this @ysolomchenko ?

[ysolomchenko]

From triage session on 2025-04-07 this is related to #2535 (probably a sub-issue of this?). Since the parent issue needs a sponsor, we are labeling this one in the same way.

We would also like to reword this in terms of the specification-level concepts, since ActivitySource and Activity are .NET specific. Could you reword this @ysolomchenko ?

Activity corresponds to a Span in tracing specifications, and ActivitySource corresponds to a Tracing Provider (or Tracer).

[pellared]

I think it is also also unclear how resource attributes collision should be handled. @ysolomchenko, am I correct?

[ysolomchenko]

I think it is also also unclear how resource attributes collision should be handled. @ysolomchenko, am I correct?

Yes, you are right