Skip to content

[DOCS-15344] Migrate Live Debugger to Cdocs - #39022

Open
domalessi wants to merge 8 commits into
masterfrom
domalessi/live-debugger-cdocs
Open

[DOCS-15344] Migrate Live Debugger to Cdocs#39022
domalessi wants to merge 8 commits into
masterfrom
domalessi/live-debugger-cdocs

Conversation

@domalessi

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Fixes DOCS-15344

Migrates the Live Debugger page to Cdocs with a language dropdown (Java, Python, .NET, Node.js, Ruby, PHP, Go). Language-specific enablement instructions live in Markdoc partials; shared content stays in the parent page.

Also removes the orphaned Spanish translation file flagged by the Cdocs pre-commit hook.

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Claude Code assisted with Cdocs migration structure, Markdoc conversion, and partial extraction.

Additional notes

  • DI migration tracked separately in DOCS-15345.

Made with Cursor

Adds a prog_lang dropdown for enablement instructions and moves
language-specific setup content into Markdoc partials.

Co-authored-by: Cursor <cursoragent@cursor.com>
@domalessi
domalessi requested review from a team as code owners August 7, 2026 19:44
@github-actions github-actions Bot added Architecture Everything related to the Doc backend cdocs labels Aug 7, 2026
@domalessi domalessi added the WORK IN PROGRESS No review needed, it's a wip ;) label Aug 7, 2026
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

New or renamed files

Removed or renamed files (these should redirect)

Remove partials in favor of conditional blocks in the parent cdoc.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions github-actions Bot removed the Architecture Everything related to the Doc backend label Aug 7, 2026
domalessi and others added 2 commits August 7, 2026 15:54
Move duplicated in-app instructions into one conditional block for
Java, Python, .NET, and Node.js.

Co-authored-by: Cursor <cursoragent@cursor.com>
Remove dropdown instruction text and in-app version table.
Enablement section now focuses on setup steps only.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jhgilbert jhgilbert added the astro-reorg-no-conflicts Needs manual conflict resolution after replatforming reorg label Aug 7, 2026
domalessi and others added 4 commits September 2, 2026 14:32
Co-authored-by: Cursor <cursoragent@cursor.com>
Split host vs Datadog requirements and separate in-app, env-var, and enablement-mode setup so each language shows a clear path.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@domalessi domalessi added editorial review Waiting on a more in-depth review and removed WORK IN PROGRESS No review needed, it's a wip ;) labels Sep 3, 2026
@domalessi

Copy link
Copy Markdown
Contributor Author

Editorial review: https://datadoghq.atlassian.net/browse/DOCS-15611

Comment on lines +68 to +71
- **[Datadog Java SDK][30]**, version 1.64.0 or higher strongly recommended (JDK 8 or higher); versions below 1.64.0 may result in unexpected errors and a degraded experience
- Minimum for [in-app enablement](#enable-in-app): 1.48.0
- Minimum for [manual enablement](#enable-with-environment-variables): 1.42.0
- **[Datadog Agent][2]**, version 7.49.0 or higher

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- **[Datadog Java SDK][30]**, version 1.64.0 or higher strongly recommended (JDK 8 or higher); versions below 1.64.0 may result in unexpected errors and a degraded experience
- Minimum for [in-app enablement](#enable-in-app): 1.48.0
- Minimum for [manual enablement](#enable-with-environment-variables): 1.42.0
- **[Datadog Agent][2]**, version 7.49.0 or higher
- [Datadog Java SDK][30], version 1.64.0 or higher strongly recommended (JDK 8 or higher); versions below 1.64.0 may result in unexpected errors and a degraded experience
- Minimum for [in-app enablement](#enable-in-app): 1.48.0
- Minimum for [manual enablement](#enable-with-environment-variables): 1.42.0
- [Datadog Agent][2], version 7.49.0 or higher

Bolding link text doubles up on emphasis.

Comment on lines +173 to +178
Update `system-probe.yaml` (located alongside `datadog.yaml`) with the following. For more information, see [Agent configuration files][37].

```yaml
dynamic_instrumentation:
enabled: true
```

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Update `system-probe.yaml` (located alongside `datadog.yaml`) with the following. For more information, see [Agent configuration files][37].
```yaml
dynamic_instrumentation:
enabled: true
```
Update `system-probe.yaml` (located alongside `datadog.yaml`) with the following:
```yaml
dynamic_instrumentation:
enabled: true
```
For more information, see [Agent configuration files][37].

Moving the cross-reference after the code block keeps the colon-then-fence pattern consistent with the Environment variable and Helm tabs.


#### Enable with environment variables {% #enable-with-environment-variables %}

{% if includes($prog_lang, ["java", "python", "dot_net", "node_js"]) %}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Go is included in the outer if here and has an in-app minimum (2.6.0) listed in Requirements, but it's excluded from this framing sentence, so a Go reader jumps straight from the "Enable with environment variables" heading to the shared code block with no lead-in.

Is that intentional? If so, it might be worth a short Go-specific sentence so the section doesn't read as if a line went missing.

Comment on lines +412 to +413
- **Configuration scope:** Live Debugger and Dynamic Instrumentation are enabled or disabled together for the same service and environment.
- **Rate limits:**

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- **Configuration scope:** Live Debugger and Dynamic Instrumentation are enabled or disabled together for the same service and environment.
- **Rate limits:**
- **Configuration scope**: Live Debugger and Dynamic Instrumentation are enabled or disabled together for the same service and environment.
- **Rate limits**:

Keeping this consistent with other bullets on the page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

astro-reorg-no-conflicts Needs manual conflict resolution after replatforming reorg cdocs editorial review Waiting on a more in-depth review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants