Description
Feature
Optimize Encoding by Grouping Multiple Spans into OTEL TraceData
Rationale
The current implementation of the encoder converts each Zipkin Span into a OTEL TraceData object. As a result, TraceData with only a single Span is sent each time. In OTEL, multiple Spans are typically grouped within ResourceSpans, and multiple ResourceSpans can be wrapped within a single TraceData. This makes the current implementation appear inefficient.
By converting MutableSpan to io.opentelemetry.proto.trace.v1.Span within the encoder, and then aggregating multiple Spans into a single TraceData on the zipkin2.reporter.Encoding or zipkin2.reporter.internal.AsyncReporter side, the efficiency of the encoding process could be significantly improved.
Example Scenario
In the current setup, each individual Zipkin Span results in a separate TraceData object being sent, even though OTEL is designed to handle multiple Spans together within ResourceSpans. By adjusting the implementation to aggregate multiple Spans into a single TraceData object, it would reduce overhead and improve processing efficiency, especially in environments where a large volume of Spans is being reported.