-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[Live Debugger] Add instructions for Go (limited preview) #32935
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
base: master
Are you sure you want to change the base?
Conversation
Preview links (active after the
|
2509435 to
4b518dc
Compare
b4fe31c to
6a8ea0f
Compare
|
Created DOCS-13027 for docs review. |
shatzi
left a comment
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 good. small comment on installation structure
|
|
||
| Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. | ||
|
|
||
| ## Installation |
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.
Unlike other languages, where we only ask users to upgrade the agent, for Go we also need to set configs on both the agent and the tracer. Both use DD_DYNAMIC_INSTRUMENTATION_ENABLED, which could be confusing.
I suggest we add a subtitle structure under Installation:
## Installation
### Data Agent configuration
### Application/Tracing Library configurationThere 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.
Good point, done
b7bbd68 to
de12155
Compare
|
Integrated the runtime toggle fix. |
https://datadoghq.atlassian.net/browse/DEBUG-4711
What does this PR do? What is the motivation?
Update docs for Live Debugger for Go for limited preview.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes