The WS/SDK path hand-crafts a partial OTLP serializer that drops resource, most span events, links, and (the painful one) the trace/span IDs on log records. That missing correlation is what forces "broadcast enrichment" plus a big pile of downstream heuristics to undo it. The zero-code examples already prove the plain OTLPSpanExporter path works, so the SDK could just become a thin configurator pointing at our own receiver. Deleting this path removes a lot of compensating code.
The WS/SDK path hand-crafts a partial OTLP serializer that drops resource, most span events, links, and (the painful one) the trace/span IDs on log records. That missing correlation is what forces "broadcast enrichment" plus a big pile of downstream heuristics to undo it. The zero-code examples already prove the plain
OTLPSpanExporterpath works, so the SDK could just become a thin configurator pointing at our own receiver. Deleting this path removes a lot of compensating code.