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

[APM Go] fix and clarify dd-trace-go v2 docs for release #28292

Draft
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

hannahkm
Copy link
Contributor

@hannahkm hannahkm commented Mar 21, 2025

What does this PR do? What is the motivation?

To minimize confusion with the differences between v1 and v2, we clarify when there are not significant changes to the specific product and link customers to the migration guide whenever possible.

Also see profiling changes here.

  • Add reusable snippet to link users to migration guide. This will ease maintenance burden too.
  • Swap order of v1 and v2 tabs--put v2 first.
  • Remove mention of v2 in Preview.
  • Add GA date to support table (subject to change).
  • Refine migration guide to include more context. Preview
  • TODO: Swap v2 code statements to come first OR remove v1 import statements entirely.

Merge instructions

Merge whenever possible, preferably before or around the dd-trace-go v2 GA release.

Merge readiness:

  • Ready for merge

Merge queue is enabled in this repo. Your branch name MUST follow the <slack_username>/<branch_name> convention, or your pull request will not pass in CI. If your branch doesn't follow this format, rename it or create a new branch and PR.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

/merge

Additional notes

Copy link
Contributor

github-actions bot commented Mar 21, 2025

Preview links (active after the build_preview check completes)

Modified Files

@github-actions github-actions bot added Guide Content impacting a guide FAQ Content impacting a FAQ labels Mar 21, 2025
@hannahkm hannahkm changed the title fix mgo link [APM Go] fix and clarify dd-trace-go v2 docs Mar 21, 2025
@hannahkm
Copy link
Contributor Author

Most important to review here is whether statements left under DSM and OTel files are accurate; has v2 made significant changes to their APIs? I don't think it has, but I'd like to confirm this.

@brett0000FF brett0000FF changed the title [APM Go] fix and clarify dd-trace-go v2 docs [APM Go] fix and clarify dd-trace-go v2 docs for release Mar 26, 2025
@brett0000FF brett0000FF requested a review from darccio March 26, 2025 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FAQ Content impacting a FAQ Guide Content impacting a guide
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants