-
Notifications
You must be signed in to change notification settings - Fork 1.2k
DOCS-11557: update live processes page #30643
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
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
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 great! I have some very tiny readability feedback, but otherwise
value: "true" | ||
``` | ||
{{% /tab %}} | ||
In Datadog Agent v7.65.0+, optimized process collection is enabled by default. If you are using an earlier version of the Datadog Agent (v7.53.0+, but lower than v7.65.0), follow these steps to enable optimized process collection: |
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.
In Datadog Agent v7.65.0+, optimized process collection is enabled by default. If you are using an earlier version of the Datadog Agent (v7.53.0+, but lower than v7.65.0), follow these steps to enable optimized process collection: | |
In Datadog Agent v7.65.0+, optimized process collection is enabled by default. If you are using an earlier version of the Datadog Agent (starting with v7.53.0, but lower than v7.65.0), follow these steps to enable optimized process collection: |
I find these kinds of tricky ranges a little easier to parse if they stick to either words or symbols to get the range across. Maybe this helps?
enabled: true | ||
``` | ||
|
||
In `system-probe.yaml`: |
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.
This seems a little odd without a verb (I'm assuming it's an instruction to add something, even if it's not explicitly stated?), but that's super nitpicky.
run_in_core_agent: | ||
enabled: false | ||
``` | ||
In `system-probe.yaml`: |
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.
Same comment about this not having a verb, so it looks like it's only implicitly but not explicitly a step, but it's by no means all that important
What does this PR do? What is the motivation?
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