Add permissions section for adaptive sampling #32234
Open
Conversation
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
Added permissions section for adaptive sampling configuration, detailing user roles and access restrictions.
Preview links (active after the
|
domalessi
reviewed
Oct 16, 2025
Comment on lines
+137
to
+138
| By default, only users with the `Datadog Admin` role can modify adaptive sampling configurations or onboard services to adaptive sampling. | ||
| To make changes, ensure your user account is upgraded to the default `Datadog Admin` role. |
There was a problem hiding this comment.
I think the second sentence is implied by the first.
Suggested change
| By default, only users with the `Datadog Admin` role can modify adaptive sampling configurations or onboard services to adaptive sampling. | |
| To make changes, ensure your user account is upgraded to the default `Datadog Admin` role. | |
| By default, only users with the `Datadog Admin` role can modify adaptive sampling configurations or onboard services to adaptive sampling. |
| If your organization uses custom roles, assign your user to a custom role that includes `APM Remote Configuration Write` and `APM Service Ingest Write` [permissions.][4] | ||
|
|
||
| ### Restrict access | ||
| Use [granular access controls][19] to manage who can modify a specific service’s adaptive sampling configuration. You can restrict access based on roles, teams or individual users. |
There was a problem hiding this comment.
Suggested change
| Use [granular access controls][19] to manage who can modify a specific service’s adaptive sampling configuration. You can restrict access based on roles, teams or individual users. | |
| Use [granular access controls][19] to manage who can modify a service's adaptive sampling configuration. You can restrict access based on roles, teams, or individual users. |
|
|
||
| 2. Click **Restrict access**. | ||
|
|
||
| 3. Select the teams, roles or users to grant access. |
There was a problem hiding this comment.
Suggested change
| 3. Select the teams, roles or users to grant access. | |
| 3. Select the teams, roles, or users to grant access to. |
|
|
||
| 4. Click **Add**. | ||
|
|
||
| Note: Only users with the `remote_config_write` permission can restrict access to the adaptive sampling configuration of individual services. |
There was a problem hiding this comment.
Suggested change
| Note: Only users with the `remote_config_write` permission can restrict access to the adaptive sampling configuration of individual services. | |
| **Note**: Only users with the `remote_config_write` permission can restrict access to the adaptive sampling configuration of individual services. |
There was a problem hiding this comment.
I'd recommend moving this note higher up. I think it's important people are aware of this limitation prior to going through the steps.
| ### Restrict access | ||
| Use [granular access controls][19] to manage who can modify a specific service’s adaptive sampling configuration. You can restrict access based on roles, teams or individual users. | ||
|
|
||
| {{< img src="/tracing/guide/adaptive_sampling/add_restriction.png" alt="Restrict permission" style="width:100%;">}} |
There was a problem hiding this comment.
The images aren't rendering. I don't see them in the /tracing/guide/adaptive_sampling folder either on my local machine... Did you mean to add the images to this PR?
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.
Added permissions section for adaptive sampling configuration, detailing user roles and access restrictions.
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