Open
Conversation
Removed private flag and preview callout for GPU Monitoring.
Removed private attribute from GPU Monitoring Fleet page.
Updated the setup instructions for GPU Monitoring, clarifying the requirements and integrations for non-Kubernetes and uniform Kubernetes environments.
Removed 'private: true' from GPU Monitoring summary.
Contributor
Preview links (active after the
|
git-thuerk-done
requested changes
Apr 20, 2026
Contributor
git-thuerk-done
left a comment
git-thuerk-done
left a comment
There was a problem hiding this comment.
Hi left some feedback!
|
|
||
| ## Set up GPU Monitoring on a non-Kubernetes environment or uniform Kubernetes cluster | ||
| ## Setting up GPU Monitoring | ||
| Setting up GPU Monitoring does not require DCGM at all. You will need to opt-in to the collection of GPU Monitoring metrics at the Agent depending on your environment: non-Kubernetes/uniform Kubernetes cluster or mixed cluster. |
Contributor
There was a problem hiding this comment.
Suggested change
| Setting up GPU Monitoring does not require DCGM at all. You will need to opt-in to the collection of GPU Monitoring metrics at the Agent depending on your environment: non-Kubernetes/uniform Kubernetes cluster or mixed cluster. | |
| Configuring GPU Monitoring does not require DCGM. You need to opt-in to the collection of GPU Monitoring metrics at the Agent depending on your environment: non-Kubernetes/uniform, Kubernetes cluster, or mixed cluster. |
| ## Setting up GPU Monitoring | ||
| Setting up GPU Monitoring does not require DCGM at all. You will need to opt-in to the collection of GPU Monitoring metrics at the Agent depending on your environment: non-Kubernetes/uniform Kubernetes cluster or mixed cluster. | ||
|
|
||
| Once you've enabled the collection of GPU Monitoring metrics, you can opt-in to enabling several integrations for more advanced insights: |
Contributor
There was a problem hiding this comment.
Suggested change
| Once you've enabled the collection of GPU Monitoring metrics, you can opt-in to enabling several integrations for more advanced insights: | |
| After you've enabled the collection of GPU Monitoring metrics, you can opt-in to enable several integrations for more advanced insights: |
| [6]: https://github.com/DataDog/helm-charts/blob/main/charts/datadog/README.md | ||
| [7]: /containers/docker/ | ||
| [8]: /agent/supported_platforms/linux/ | ||
| [9]: https://docs.datadoghq.com/getting_started/integrations/aws/ |
Contributor
There was a problem hiding this comment.
Suggested change
| [9]: https://docs.datadoghq.com/getting_started/integrations/aws/ | |
| [9]: /getting_started/integrations/aws/ |
| [7]: /containers/docker/ | ||
| [8]: /agent/supported_platforms/linux/ | ||
| [9]: https://docs.datadoghq.com/getting_started/integrations/aws/ | ||
| [10]:https://docs.datadoghq.com/getting_started/integrations/google_cloud/?tab=orglevel |
Contributor
There was a problem hiding this comment.
Suggested change
| [10]:https://docs.datadoghq.com/getting_started/integrations/google_cloud/?tab=orglevel | |
| [10]: /getting_started/integrations/google_cloud/?tab=orglevel |
| [8]: /agent/supported_platforms/linux/ | ||
| [9]: https://docs.datadoghq.com/getting_started/integrations/aws/ | ||
| [10]:https://docs.datadoghq.com/getting_started/integrations/google_cloud/?tab=orglevel | ||
| [11]:https://docs.datadoghq.com/getting_started/integrations/azure/?tab=createanappregistration |
Contributor
There was a problem hiding this comment.
Suggested change
| [11]:https://docs.datadoghq.com/getting_started/integrations/azure/?tab=createanappregistration | |
| [11]: /getting_started/integrations/azure/?tab=createanappregistration |
| [9]: https://docs.datadoghq.com/getting_started/integrations/aws/ | ||
| [10]:https://docs.datadoghq.com/getting_started/integrations/google_cloud/?tab=orglevel | ||
| [11]:https://docs.datadoghq.com/getting_started/integrations/azure/?tab=createanappregistration | ||
| [12]:https://docs.datadoghq.com/getting_started/integrations/oci/ |
Contributor
There was a problem hiding this comment.
Suggested change
| [12]:https://docs.datadoghq.com/getting_started/integrations/oci/ | |
| [12]: /getting_started/integrations/oci/ |
| [10]:https://docs.datadoghq.com/getting_started/integrations/google_cloud/?tab=orglevel | ||
| [11]:https://docs.datadoghq.com/getting_started/integrations/azure/?tab=createanappregistration | ||
| [12]:https://docs.datadoghq.com/getting_started/integrations/oci/ | ||
| [13]:https://docs.datadoghq.com/infrastructure/process?tab=linuxwindows#installation |
Contributor
There was a problem hiding this comment.
Suggested change
| [13]:https://docs.datadoghq.com/infrastructure/process?tab=linuxwindows#installation | |
| [13]: /infrastructure/process?tab=linuxwindows#installation |
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
2 participants
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.
What does this PR do? What is the motivation?
We're GAing GPU Monitoring Weds 4/22 so I'd like to remove all preview mentions in the doc and make the docs public instead of private.
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.
AI assistance
Additional notes