-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
base: master
Are you sure you want to change the base?
Conversation
Created DOCS-9639 for docs team review. |
There was a problem hiding this 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
- I saw no indication of how we will be supporting
v1
after thev2
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 - 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 sayuse this link (unless you're v2, then use this other link)
. If we're looking for adoption, this is not the way to go - 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
- 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
andv2 (preview)
. Over time, we can switch the tabs to bev2
andv1 (legacy)
, but we'll need to maintain these long term so need to handle that up front - 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/profiler/guide/isolate-outliers-in-monolithic-services.md
Outdated
Show resolved
Hide resolved
...ent/en/security/application_security/software_composition_analysis/setup/compatibility/go.md
Outdated
Show resolved
Hide resolved
This reverts commit 310bd89.
Signed-off-by: Brian Deutsch <[email protected]>
…atform/apmlp-29/v2-docs
There was a problem hiding this 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:
- Could we please revert the contents in https://github.com/DataDog/documentation/pull/25897/files#r1876820184, except for the changes we actually need? I don't want to accidentally overwrite the existing page.
- Question: I noticed we removed the OpenTracing docs. I know these were deprecated, but I wanted to double check this was intentional.
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/custom_instrumentation/go/migration.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/custom_instrumentation/go/migration.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/custom_instrumentation/go/migration.md
Outdated
Show resolved
Hide resolved
@brett0000FF Yes, |
There was a problem hiding this 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. 🕐
content/en/tracing/trace_collection/custom_instrumentation/go/migration.md
Outdated
Show resolved
Hide resolved
...ent/en/security/application_security/software_composition_analysis/setup/compatibility/go.md
Outdated
Show resolved
Hide resolved
content/en/security/application_security/threats/setup/compatibility/go.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/custom_instrumentation/go/dd-api.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this 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/security/application_security/threats/setup/threat_detection/go.md
Outdated
Show resolved
Hide resolved
content/en/security/application_security/threats/setup/threat_detection/go.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/custom_instrumentation/go/otel.md
Outdated
Show resolved
Hide resolved
…detection/go.md Co-authored-by: Brian Marks <[email protected]>
Co-authored-by: Brian Marks <[email protected]>
sort import lines and fix typos Co-authored-by: Brian Marks <[email protected]>
There was a problem hiding this 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!!!
content/en/tracing/trace_collection/custom_instrumentation/go/migration.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/custom_instrumentation/go/migration.md
Outdated
Show resolved
Hide resolved
add v2 doc links Co-authored-by: Brian Marks <[email protected]>
What does this PR do? What is the motivation?
Updates Go docs to
dd-trace-go/v2
changes.Merge instructions