Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evalute tracing.distributed_tracing.propagation_style option before accesing tracing.distributed_tracing.propagation_inject_style and tracing.distributed_tracing.propagation_extract_style #3006

Closed

Conversation

GustavoCaso
Copy link
Member

@GustavoCaso GustavoCaso commented Jul 27, 2023

What does this PR do?

Make sure Datadog.configuration.tracing.distributed_tracing.propagation_style is evaluated before accessing tracing.distributed_tracing.propagation_inject_style and tracing.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?

…ccesing tracing.distributed_tracing.propagation_inject_style and tracing.distributed_tracing.propagation_extract_style
@TonyCTHsu
Copy link
Contributor

I am closing it, because I have included this into #2879

@TonyCTHsu TonyCTHsu closed this Sep 1, 2023
@GustavoCaso GustavoCaso deleted the ensure-propagation_style-option-is-computed branch October 11, 2023 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants