Evalute tracing.distributed_tracing.propagation_style option before accesing tracing.distributed_tracing.propagation_inject_style and tracing.distributed_tracing.propagation_extract_style #3006
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.
What does this PR do?
Make sure
Datadog.configuration.tracing.distributed_tracing.propagation_style
is evaluated before accessingtracing.distributed_tracing.propagation_inject_style
andtracing.distributed_tracing.propagation_inject_style and tracing.distributed_tracing.propagation_extract_style
The solution could be better. the Propagation class is used as the parent class for other propagation-specific integrations. So if a customer has multiple distributed integrations, we might evaluate
Datadog.configuration.tracing.distributed_tracing.propagation_style
multiple times.Motivation
Additional Notes
How to test the change?