Migrate ddtrace(v1) to datadog(v2). #15
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gedorinku
reviewed
Jan 8, 2026
Member
gedorinku
left a comment
gedorinku
left a comment
There was a problem hiding this comment.
datadog 2.x includes many breaking changes. It is necessary to address all of them.
https://github.com/DataDog/dd-trace-rb/blob/release/docs/UpgradeGuide2.md
For example, this code uses Datadog::Tracing::Span#span_id, but it has been renamed in datadog 2.x.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
Migrate ddtrace(datadog v1) gem to datadog v2 gem.
📝
ddtracegem was renamed todatadogwhen ddtrace version bump to 2.0.0.What