[exporterhelper] Propagate Context in DisabledBatcher #12225
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When the batching functionality of
exporterhelper
is disabled (which is the default), theDisabledBatcher
discards the provided Context and creates a new one with context.Background. This breaks traces, even when using the in-memory queue.Link to tracking issue
No tracking issue.
Testing
I compared the traces emitted for a simple OTLP receiver -> OTLP exporter pipeline: the
exporterhelper
span is in its own trace before the PR, and in the same trace as the receiver span after.