New doc for service override removal #33535
Open
+112
−59
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
domalessi
commented
Dec 22, 2025
domalessi
commented
Dec 22, 2025
| | With service overrides | `service:my-service-mysql` or `service:mysql` | None | | ||
| | Without service overrides | `service:myservice` | `@peer.db.name:user-db`, `@peer.db.system:mysql` | | ||
|
|
||
| ## Remove overrides progressively |
Contributor
Author
There was a problem hiding this comment.
@marianafrangos I pulled this content over from the Service Overrides Guide.
- Is this still the recommended flow for removing service overrides, whether you do it in the UI or through config/env var setting? Or does it apply only to env var setting?
- Are any of these steps essentially overridden by the new UI functionality? For example, I know the UI will show affected dashboards, so you don't have to dig around to find that yourself. Do we want to direct folks to the new UI features for some of these steps, even if they're going the env var route?
Contributor
Preview links (active after the
|
drichards-87
approved these changes
Dec 23, 2025
Contributor
drichards-87
left a comment
drichards-87
left a comment
There was a problem hiding this comment.
Looks good overall. I just left one comment and a suggestion. PR is approved.
Co-authored-by: DeForest Richards <[email protected]>
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.
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