Skip to content

gpu: document 7.79.0 system-probe workaround - #39083

Draft
matthewnewman43 wants to merge 1 commit into
masterfrom
matthew.newman/gpu-779-system-probe-deprecated
Draft

gpu: document 7.79.0 system-probe workaround#39083
matthewnewman43 wants to merge 1 commit into
masterfrom
matthew.newman/gpu-779-system-probe-deprecated

Conversation

@matthewnewman43

@matthewnewman43 matthewnewman43 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Documents the Agent v7.79.0 workaround for GPU Monitoring: set gpu_monitoring.system_probe_deprecated: true in system-probe.yaml.

What does this PR do? What is the motivation?

Adds a sub-bullet under Minimum version requirements on the GPU Monitoring setup page covering an Agent v7.79.0 edge case that requires a system-probe config change.

This sits alongside the existing v7.82.0 kernel-panic clause rather than replacing it — the two are separate issues.

Paired with: web-ui#340804 — the in-product banner asserting the same claim, behind gpu-monitoring-agent-version-779-deprecation. Both were produced by the gpu-monitoring-public-doc-changes skill (web-ui#340806).

Merge readiness

  • Ready for merge

Not ready to merge. The symptom wording ("a known issue affecting GPU Monitoring") is a placeholder pending a precise description of the failure mode. Do not merge until that is replaced.

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

Drafted with Claude Code, which located the target section, checked the wording against the repo style guide, and prepared the paired in-product change. Reviewed by a human before submission.

Additional notes

The value is true (enabling a system_probe_deprecated flag), not false — worth a second look from someone who knows the Agent-side semantics.

@github-actions

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@jhgilbert jhgilbert added the astro-reorg-no-conflicts Needs manual conflict resolution after replatforming reorg label Aug 10, 2026
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants