We added span name inference for OTel-based spans directly into the captureSpan pipeline. This is a bit suboptimal because it increases browser bundle size that also uses captureSpan despite these spans never going through a browser SDK.
Instead, we can use the client.on('processSpan') hook in the Sentry SpanProcessor to use the already existing parseSpanDescription logic from @sentry/opentelementry.
We added span name inference for OTel-based spans directly into the
captureSpanpipeline. This is a bit suboptimal because it increases browser bundle size that also usescaptureSpandespite these spans never going through a browser SDK.Instead, we can use the
client.on('processSpan')hook in the SentrySpanProcessorto use the already existingparseSpanDescriptionlogic from@sentry/opentelementry.