gpu: document 7.79.0 system-probe workaround - #39083
Draft
matthewnewman43 wants to merge 1 commit into
Draft
Conversation
Contributor
Preview links (active after the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the Agent v7.79.0 workaround for GPU Monitoring: set
gpu_monitoring.system_probe_deprecated: trueinsystem-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 thegpu-monitoring-public-doc-changesskill (web-ui#340806).Merge readiness
For Datadog employees:
<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./reviewto 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 asystem_probe_deprecatedflag), notfalse— worth a second look from someone who knows the Agent-side semantics.