plugin/trace: migrate dd-trace-go v1 to v2 #7466
Merged
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.
1. Why is this pull request needed and what does it do?
Migrates the DataDog tracing integration
dd-trace-gofrom v1 to v2. Version 1 will be deprecated by the end of this year. See docs here.Changes:
dd-trace-godependency to v2.2.2OnShutdown()opentracer.New()withtracer.Start()Validated with a DataDog test account that spans are being spawned properly, with the proper tags.
2. Which issues (if any) are related?
Fixes #7372.
3. Which documentation changes (if any) need to be made?
None - configuration syntax and behavior remain identical for users.
4. Does this introduce a backward incompatible change or deprecation?
This change is fully backwards compatible:
coredns.io@name,coredns.io@type, etc.)