Adding AwsUnsampledOnlySpanProcessor to export batches of unsampled spans #948
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 of changes
Following the approach as ADOT Python: aws-observability/aws-otel-python-instrumentation#247. Note that the span attribute key was later changed to
aws.trace.flag.sampled
.Introducing
AwsUnsampledOnlySpanProcessor
that can be appended to aTracerProvider
. This span processor wraps aBatchSpanProcessor
for delegating all the operations after processing. TheAwsUnsampledOnlySpanProcessor
does 2 things:aws.trace.flag.sampled
span attribute on each span.Testing
Setup
Observations:
alwaysOn
sampler, the sampled span is not exported at all.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.