Conversation
evazorro
added this pull request to stack #40104
September 21, 2026 20:30
Contributor
Preview links (active after the
|
evazorro
commented
Sep 22, 2026
evazorro
force-pushed
the
eva/DOCS-15755-ddr-revisions-4
branch
from
September 23, 2026 16:14
8740250 to
f11b0b7
Compare
evazorro
force-pushed
the
eva/DOCS-15755-ddr-revisions-4
branch
from
September 24, 2026 15:18
ded8c69 to
13e8511
Compare
1 task
evazorro
marked this pull request as ready for review
September 24, 2026 15:33
michael-richey
approved these changes
Sep 24, 2026
domalessi
approved these changes
Sep 24, 2026
domalessi
left a comment
domalessi
left a comment
Contributor
There was a problem hiding this comment.
A few inline tweaks. Otherwise, looks great!
Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com>
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
3 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?
The Datadog Disaster Recovery (DDR) team has a revised version of the setup docs drafted in Google Docs and vetted by Legal. I'm transferring those changes over to the official documentation, doing it in pieces so that the diffs are smaller and easier to review.
This PR updates part 2 of the setup procedure: Configure access, integrations, and sync
Merge readiness
AI assistance
Made the changes myself (including a few tweaks beyond what was in the google doc), then had Codex review and point out places for improvement.
Additional notes