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

[Go] feat: update docs for dd-trace-go/v2 #25897

Open
wants to merge 57 commits into
base: master
Choose a base branch
from

Conversation

darccio
Copy link
Member

@darccio darccio commented Oct 24, 2024

What does this PR do? What is the motivation?

Updates Go docs to dd-trace-go/v2 changes.

Merge instructions

  • Please merge after reviewing

@github-actions github-actions bot added Guide Content impacting a guide FAQ Content impacting a FAQ labels Oct 24, 2024
Copy link
Contributor

github-actions bot commented Oct 24, 2024

Preview links (active after the build_preview check completes)

New or renamed files

Removed or renamed files (these should redirect)

Modified Files

@bm1549 bm1549 marked this pull request as ready for review November 27, 2024 19:17
@bm1549 bm1549 requested review from a team as code owners November 27, 2024 19:17
@neko-dd neko-dd added the editorial review Waiting on a more in-depth review label Nov 27, 2024
@neko-dd
Copy link
Contributor

neko-dd commented Nov 27, 2024

Created DOCS-9639 for docs team review.

Copy link
Contributor

@bm1549 bm1549 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I partially reviewed this, but wanted to share some general feedback here

  1. I saw no indication of how we will be supporting v1 after the v2 release, which will be a common question from our customers. We need to get in front of this and be clear about what will be back-ported (security issues, bugs, new feature, etc) and when v1 will be EOL, if ever
  2. Many of the changes make v2 seem like a second-class option, rather than the new primary option. It's in preview right now so that'll change over time, but many of the docs say use this link (unless you're v2, then use this other link). If we're looking for adoption, this is not the way to go
  3. We're indicating that there's a v2 option on many pages, but it's very likely that a customer landing on the page won't know what version they're using now, let alone which one they should be using. We shouldn't put an upgrade guide everywhere, but putting it in a few targeted places would go a long way
  4. We have some pages created as duplicates of older pages with v2 added in place of v1 - let's avoid that by utilizing tabs for v1 and v2 (preview). Over time, we can switch the tabs to be v2 and v1 (legacy), but we'll need to maintain these long term so need to handle that up front
  5. Although the updates to other language pages are probably fine, they should be reverted since the documentation team prefers our translators to be the ones updating those

content/en/containers/amazon_ecs/apm.md Outdated Show resolved Hide resolved
content/en/containers/docker/apm.md Outdated Show resolved Hide resolved
content/en/data_streams/go.md Outdated Show resolved Hide resolved
content/en/data_streams/go.md Outdated Show resolved Hide resolved
content/en/database_monitoring/connect_dbm_and_apm.md Outdated Show resolved Hide resolved
content/en/profiler/enabling/go.md Outdated Show resolved Hide resolved
content/en/profiler/enabling/go.md Show resolved Hide resolved
content/en/profiler/enabling/go.md Outdated Show resolved Hide resolved
@hannahkm hannahkm requested a review from a team as a code owner December 5, 2024 18:56
Signed-off-by: Brian Deutsch <[email protected]>
@bgdeutsch bgdeutsch requested a review from a team as a code owner December 18, 2024 19:24
@github-actions github-actions bot added the Architecture Everything related to the Doc backend label Dec 18, 2024
Copy link
Contributor

@brett0000FF brett0000FF left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making these updates! I found a few more things to fix.

In addition to my suggested changes:

@hannahkm
Copy link
Contributor

hannahkm commented Dec 19, 2024

@brett0000FF Yes, opentracing has been removed entirely in v2, so we deleted it from the docs. Let me know if we might want to add that back!

@hannahkm hannahkm requested a review from brett0000FF December 19, 2024 18:31
Copy link
Contributor

@brett0000FF brett0000FF left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note I am going to apply the changes suggested in this review myself shortly. 🕐

Copy link
Contributor

@bm1549 bm1549 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, just had a couple of minor suggestions and then this is good to ship 🚢

content/en/profiler/enabling/go.md Outdated Show resolved Hide resolved
content/en/profiler/enabling/go.md Outdated Show resolved Hide resolved
content/en/serverless/aws_lambda/installation/go.md Outdated Show resolved Hide resolved
content/en/database_monitoring/connect_dbm_and_apm.md Outdated Show resolved Hide resolved
content/en/database_monitoring/connect_dbm_and_apm.md Outdated Show resolved Hide resolved
content/en/tracing/trace_pipeline/ingestion_mechanisms.md Outdated Show resolved Hide resolved
content/en/tracing/trace_pipeline/ingestion_mechanisms.md Outdated Show resolved Hide resolved
Copy link
Contributor

@bm1549 bm1549 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pending the last few comments, approved!

Amazing work Dario and Hannah for the thorough doc updates!!!

@hannahkm hannahkm requested a review from a team as a code owner January 2, 2025 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Architecture Everything related to the Doc backend editorial review Waiting on a more in-depth review FAQ Content impacting a FAQ Guide Content impacting a guide
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants