Leverage BatchSpanProcessor's span dropping functionality #1566
Labels
Bug
Something isn't working
priority:p1
Critical issues and bugs. Highest priority; breaking API changes.
release:required-for-ga
Required for 1.0 GA release
The recent change to make the export methods async appears to have introduced a situation where the
BatchSpanProcessor
can lose telemetry in the case where itsspansList
isn't drained fast enough.While the
BatchSpanProcessor
is built to cater for spans being dropped, and therefore its usage must assume this as a possibility, we can at least ensure thatexportBatches
is replaced by a function to take just one batch (drainBatch
?) so that the existingBatchSpanProcessor
reporting of dropped telemetry is leveraged.The text was updated successfully, but these errors were encountered: