DOCS-10575-DDR #29293

iadjivon · 2025-05-12T19:24:53Z

What does this PR do? What is the motivation?

New DDR doc.
Editorial Review: https://datadoghq.atlassian.net/browse/DOCS-11215

Merge instructions

Merge readiness:

Ready for merge

For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass in 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.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

/merge

Additional notes

github-actions · 2025-05-12T19:28:25Z

Preview links (active after the `build_preview` check completes)

New or renamed files

https://docs-staging.datadoghq.com/ida.adjivon/DOCS-10575-DiRec-for-okr11/agent/guide/datadog-disaster-recovery

datadog-datadog-prod-us1 · 2025-05-12T19:55:05Z

_{No data reported at this time.

This comment will be updated automatically if new data arrives.

🔗 Commit SHA: 6a55768 | Docs | Was this helpful? Give us feedback!}

jhgilbert · 2025-05-12T21:14:14Z

Hi @iadjivon! I see you noted this is a work in progress -- I added the "work in progress" label to keep this PR out of the oncall review queue. Thank you!

…jivon/DOCS-10575-DiRec-for-okr11

content/en/agent/guide/datadog-disaster-recovery.md

…jivon/DOCS-10575-DiRec-for-okr11

heyronhay

Some comments - looks pretty great overall, though!

content/en/agent/guide/datadog-disaster-recovery.md

github-actions · 2025-05-28T01:59:33Z

📝 Documentation Team Review Required

This pull request requires approval from the @DataDog/documentation team before it can be merged.

Please ensure your changes follow our documentation guidelines and wait for a team member to review and approve your changes.

content/en/agent/guide/datadog-disaster-recovery.md

michael-richey

looking good

content/en/agent/guide/datadog-disaster-recovery.md

janine-c

Thanks for your patience on this review, Ida! This is really coming together. Let me know if you have any questions about my comments or if you want to have a chat! Nailing down the structure for a complicated procedure always takes some thought, and this one is a doozy all put together 🙂

janine-c · 2025-07-09T18:51:00Z

content/en/agent/guide/datadog-disaster-recovery.md

+Datadog Agent version **7.54 or above** is required for Datadog Disaster Recovery. 
+
+### Supported telemetry types and products
+The Agent-based failover description provided on this page supports failover of the following telemetry types and products:


The Agent-based failover description provided on this page confused me a little bit. I'm not sure what the description is; it something you can link to? Or maybe you can rephrase to something like The Agent-based failover supports...?

content/en/agent/guide/datadog-disaster-recovery.md

janine-c · 2025-07-09T23:39:21Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+If you're also sending telemetry to Datadog using cloud provider integrations, you must add your cloud provider accounts in the DDR org. 
+
+Datadog does not use cloud providers to receive telemetry data while the DDR site is passive.


Can you explain what "passive" means here?

When it is not actively in failover. But I am confirming with the team. BRB on this.

content/en/agent/guide/datadog-disaster-recovery.md

janine-c · 2025-07-09T23:40:56Z

content/en/agent/guide/datadog-disaster-recovery.md

+## Setup 
+To enable Datadog Disaster Recovery:
+
+1. [Configure Datadog Disaster Recovery](#configure-datadog-disaster-recovery)


I found the numbering system here a little confusing; each of these headings has a number, but only in this list, and then each of the sub-items has a number as well. So if someone messages their colleague to say something like "I'm stuck on step 3," it might be hard for the colleague to figure out where they are. It could be helpful to consider combining letters and numbers, so someone could refer to "3a" instead or something like that.

I might put some time into thinking about exactly which steps need to happen in sequence, and thus definitively need numbers associated with them. Particularly in the "Configure your DDR organization" section, it seems as though the accordions can happen in virtually any order. I wonder if it would make sense to just make the headings numbered, and remove numbers from the accordions, so the overall page might feel a little less overwhelming.

Very great point!!

janine-c · 2025-07-10T00:20:02Z

content/en/agent/guide/datadog-disaster-recovery.md

+[4]: https://docs.datadoghq.com/getting_started/site/#access-the-datadog-site
+[5]: https://github.com/DataDog/datadog-sync-cli/blob/main/README.md 
+[6]: https://docs.datadoghq.com/logs/log_configuration/attributes_naming_convention/#overview
+[7]: https://docs.datadoghq.com/agent/remote_config/?tab=configurationyamlfile
+[8]: https://docs.datadoghq.com/api/latest/organizations/#get-organization-information 
+[9]: https://docs.datadoghq.com/account_management/saml/#overview


Suggested change

[4]: https://docs.datadoghq.com/getting_started/site/#access-the-datadog-site

[5]: https://github.com/DataDog/datadog-sync-cli/blob/main/README.md

[6]: https://docs.datadoghq.com/logs/log_configuration/attributes_naming_convention/#overview

[7]: https://docs.datadoghq.com/agent/remote_config/?tab=configurationyamlfile

[8]: https://docs.datadoghq.com/api/latest/organizations/#get-organization-information

[9]: https://docs.datadoghq.com/account_management/saml/#overview

[4]: /getting_started/site/#access-the-datadog-site

[5]: https://github.com/DataDog/datadog-sync-cli/blob/main/README.md

[6]: /logs/log_configuration/attributes_naming_convention/#overview

[7]: /agent/remote_config/?tab=configurationyamlfile

[8]: /api/latest/organizations/?code-lang=curl#get-organization-information

[9]: /account_management/saml/#overview

We tend to use relative links for linking within the docs. Absolute links still work, so it's not a huge deal, but I like to keep our approach consistent.

Additionally, for [8], the paragraph that introduces the link says you have to use the cURL command, so this links directly to the cURL tab.

content/en/agent/guide/datadog-disaster-recovery.md

janine-c · 2025-07-10T00:27:33Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+{{% /collapse-content %}}
+
+{{% collapse-content title=" 8. Update your Datadog Agent configuration" level="h5" %}}


Suggested change

{{% collapse-content title=" 8. Update your Datadog Agent configuration" level="h5" %}}

{{% collapse-content title=" 8. Send telemetry to your DDR org" level="h5" %}}

I think this title gets to the heart of what the user is trying to accomplish a little better. It can be a little confusing to get a step to update the config towards the end of a process, so this can help clarify that.

Also, this seems like another recommended step that isn't labelled as such?

Lastly, I wasn't sure whether this should say DDR org or DDR site. I see they're both used in this topic, and am not sure if there's a difference? Maybe if they're interchangeable, we should just pick one and stick with it. The latter only appears in a few places, so at least that would be easy 🙂

janine-c · 2025-07-10T21:56:15Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+{{% /collapse-content %}}
+
+{{% collapse-content title=" 10. Activate and test DDR failover in cloud integrations" level="h5" %}}


There seems to be a mismatch between the title and the content for this accordion. The content doesn't seem to address activating or testing failovers for cloud integrations, so I got confused about what I was supposed to take away. Does it mean you have to contact your CSM or support to be able to do these things? Or can you do them on the landing page? If the latter, it seems odd that there are no instructions?

content/en/agent/guide/datadog-disaster-recovery.md

merge master

merge with master

…reated but no longer in use.

iadjivon

Added edits! Let me know what you think!
Thanks for this thorough review! 🥰

content/en/agent/guide/datadog-disaster-recovery.md

iadjivon · 2025-07-14T20:10:15Z

content/en/agent/guide/datadog-disaster-recovery.md

+## Setup 
+To enable Datadog Disaster Recovery:
+
+1. [Configure Datadog Disaster Recovery](#configure-datadog-disaster-recovery)


Very great point!!

iadjivon · 2025-07-14T21:04:03Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+If you're also sending telemetry to Datadog using cloud provider integrations, you must add your cloud provider accounts in the DDR org. 
+
+Datadog does not use cloud providers to receive telemetry data while the DDR site is passive.


When it is not actively in failover. But I am confirming with the team. BRB on this.

iadjivon · 2025-07-14T21:09:26Z

content/en/agent/guide/datadog-disaster-recovery.md

+### Retrieve the public IDs and link your organization
+{{% collapse-content title=" 2. Retrieve the public IDs of your orgs and link the DDR org to the primary org" level="h5" %}}
+
+#### Retrieve the public IDs


modified this, lmk what you

janine-c

This is really coming together! The structure makes a lot more sense to me. I have some comments; as always, always happy to chat more about them if you like!

janine-c · 2025-07-23T23:10:13Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+
+## Prerequisites 
+Datadog Disaster Recovery requires Datadog Agent version **7.54 or above**. The APM product support requires a **v7.68 or above**.


Suggested change

Datadog Disaster Recovery requires Datadog Agent version **7.54 or above**. The APM product support requires a **v7.68 or above**.

Datadog Disaster Recovery requires Datadog Agent **v7.54+**. The APM product support requires **v7.68+**.

I noticed that we had a couple of different ways of writing out versions, so I tried to standardize it a bit with the table below. If you think it's harder to read, especially with the + in the middle of a sentence, feel free to modify!

janine-c · 2025-07-23T23:17:42Z

content/en/agent/guide/datadog-disaster-recovery.md

+  - Go to [Get Started with Datadog](https://app.datadoghq.com/signup)
+  - Choose a different Datadog site than your primary (for example if you're on `US1`, choose `EU` or `US5`)
+  - Follow the prompts to create an account


Suggested change

- Go to [Get Started with Datadog](https://app.datadoghq.com/signup)

- Choose a different Datadog site than your primary (for example if you're on `US1`, choose `EU` or `US5`)

- Follow the prompts to create an account

1. Go to [Get Started with Datadog](https://app.datadoghq.com/signup). You may need to logout of your current session, or use incognito mode to access this page.

2. Choose a different Datadog site than your primary (for example, if you're on `US1`, choose `EU` or `US5`).

3. Follow the prompts to create an account.

I'm wondering if you see the same thing that I do - if I go to the Get Started with Datadog in a browser where I'm already logged in, I go to the app homepage and not the signup page. And I think users with primary accounts would see the same thing, right? Unless maybe it's on my end?

content/en/agent/guide/datadog-disaster-recovery.md

janine-c · 2025-07-23T23:26:04Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+{{% collapse-content title="Retrieve the public IDs and link your DDR and primary orgs " level="h5" %}}
+
+After the Datadog team has set your DDR org, use the cURL commands from the Datadog [public API endpoint][8] to retrieve the public IDs of the primary and DDR org. 


I still don't think you can use this endpoint if you don't have the public ID, since the ID is a path parameter you need to make the call? In other words, if you don't have the public ID, what are you going to do with the API?

@janine-c is correct here, you have to already have your public_id to use this endpoint.

janine-c · 2025-07-24T18:26:20Z

content/en/agent/guide/datadog-disaster-recovery.md

+To link your DDR and primary orgs, run these commands replacing the placeholders for their values:
+
+<div class="alert alert-warning"> For security reasons, Datadog is unable to link the orgs on your behalf. </div>


Maybe switch these two around, so the alert doesn't get in between the intro and the commands?

janine-c · 2025-07-24T23:40:45Z

content/en/agent/guide/datadog-disaster-recovery.md

+</div>
+
+#### Verify availability at the DDR site
+Verify that your DDR org is accessible and that your Dashboards and Monitors are copied from your primary org to your DDR org.


Suggested change

Verify that your DDR org is accessible and that your Dashboards and Monitors are copied from your primary org to your DDR org.

Verify that your DDR org is accessible and that your dashboards and monitors are copied from your primary org to your DDR org.

janine-c · 2025-07-24T23:42:56Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+##### Cloud integrations failover


Suggested change

##### Cloud integrations failover

Doesn't seem necessary to just have this one heading in the collapsible?

janine-c · 2025-07-24T23:45:13Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+{{% /collapse-content %}}
+
+{{% collapse-content title="Activate and test DDR failover in cloud integrations" level="h5" %}}


This section doesn't contain information on how to activate and test cloud integrations, which makes it a little confusing. The verbs that indicate what a section contains are very important so users can figure out how the docs align with their objectives. Here, there's a blurb that talks about how failing over cloud integrations is separate in the DDR org, somehow...but I still don't understand what a user is supposed to do with that information if they want to activate and test the failover for their integrations. Do they have to contact their CSM/support for help if they want to test it? If so, we should state that explicitly.

@michael-richey is there an activation step/button for integrations available in the disaster recovery landing page in the DDR region?

If there is, @janine-c , would adding that clarify the paragraph here?

Yeah I think it could! Basically, the problem I'm trying to avoid here is making users think there's an action to carry out ("ooh, activate and test! I'll feel so much more secure in my approach once I've done that!") and then not give them clear instructions on that action. It looks like we're kind of hinting at something they can do on the disaster recovery landing page, but it's vague and I'm not sure what it really does. Some clarity here about what to expect and what to look for to indicate the test was a success would really help! Otherwise, users might think they've successfully performed the test, but we don't want them to find out that they didn't during an incident!

I can walk either of you through this if you want a live demo, but it's confusing and a little dangerous so maybe that's why we're trying to push them to talk to someone? Integrations need to be configured in both Orgs. Then there is literally a button on the disaster recovery landing page that acts as the Frankenstein switch mentioned above. When they hit that button integration telemetry stops going to R1 (that's the dangerous part they really need to understand) and starts going to R2.

janine-c · 2025-07-24T23:46:18Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+<!-- ------------------------------- -->
+
+### 3. Test	Run failover tests in various environments


Suggested change

### 3. Test Run failover tests in various environments

### 3. Test run failover tests in various environments

janine-c · 2025-07-24T23:52:29Z

content/en/agent/guide/datadog-disaster-recovery.md

+
+### 2. Set up access, integrations, syncing, and agents
+
+{{% collapse-content title="Create your Datadog API and App key for syncing" level="h5" %}}


I just realized that the step where they create the keys and the step where they use them are kind of far away from each other. I don't know if they're in this order for a specific reason, but I would suggest putting them next to each other if you can:

It can be reassuring to a user to use something right after they make it, so the process makes intuitive sense

Putting the steps close to each other makes it more likely that they still have the keys open in the window or copied to their clipboard, which makes it more convenient

iadjivon added 4 commits May 8, 2025 17:28

created doc and confirmed it staging preview link with local host

4bf125e

added the first couple of of set up steps

f61d670

added the first couple of of set up steps-pt2

cd23790

completed the DDR docs

66d0b67

iadjivon requested a review from a team as a code owner May 12, 2025 19:24

github-actions bot added the Guide Content impacting a guide label May 12, 2025

iadjivon added the okr11 label May 12, 2025

iadjivon added 2 commits May 12, 2025 15:47

small edits

62b7799

small edits

92d0933

jhgilbert added the WORK IN PROGRESS No review needed, it's a wip ;) label May 12, 2025

iadjivon added 5 commits May 14, 2025 18:07

added all of the steps and moved the reformatted the page.

b7bf7b6

added all of the steps and moved the reformatted the page.

274673d

Merge branch 'master' of github.com:DataDog/documentation into ida.ad…

75d083b

…jivon/DOCS-10575-DiRec-for-okr11

added a toc for the set up section

3c4baf8

changes

5874173

michael-richey reviewed May 19, 2025

View reviewed changes

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

michael-richey reviewed May 19, 2025

View reviewed changes

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

michael-richey reviewed May 19, 2025

View reviewed changes

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

iadjivon added 4 commits May 19, 2025 14:20

Merge branch 'master' of github.com:DataDog/documentation into ida.ad…

6407e78

…jivon/DOCS-10575-DiRec-for-okr11

added m.r. comments from his review of the doc

a8dd5c4

Merge branch 'master' of github.com:DataDog/documentation into ida.ad…

f8b10e0

…jivon/DOCS-10575-DiRec-for-okr11

removed US FED from the table

7875bcd

heyronhay requested changes May 23, 2025

View reviewed changes

bawsome reviewed Jun 2, 2025

View reviewed changes

michael-richey reviewed Jun 2, 2025

View reviewed changes

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

michael-richey reviewed Jun 2, 2025

View reviewed changes

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

michael-richey reviewed Jun 27, 2025

View reviewed changes

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

content/en/agent/guide/datadog-disaster-recovery.md Outdated Show resolved Hide resolved

iadjivon added 2 commits June 27, 2025 15:26

Merge branch 'master' into ida.adjivon/DOCS-10575-DiRec-for-okr11

c0a7dbd

changes from PM review

a9fa479

iadjivon requested a review from janine-c June 30, 2025 17:40

janine-c reviewed Jul 10, 2025

View reviewed changes

iadjivon added 9 commits July 14, 2025 15:40

Merge branch 'master' into ida.adjivon/DOCS-10575-DiRec-for-okr11

9b02569

merge master

the numbering in setup

2f0220e

removed numbers from the collapseable content

9c9e8c4

removed the toc from the setup, and addedc numbers instead

a20c4fa

wip

feeb57a

Merge branch 'master' into ida.adjivon/DOCS-10575-DiRec-for-okr11

053c138

merge with master

changed TO failover_apm in all places

e8f8486

specified the agent version needed by each product/telemetry

4d5ef96

added the extra failover to the helm/operator config

0ee88af

iadjivon force-pushed the ida.adjivon/DOCS-10575-DiRec-for-okr11 branch from 3ea082d to 0ee88af Compare July 17, 2025 18:27

iadjivon added 3 commits July 18, 2025 16:12

removed test content

b6de481

Merge branch 'master' into ida.adjivon/DOCS-10575-DiRec-for-okr11

40b13c2

merge with master

added suggestions from review and deleted shortcode file previously c…

402ee8b

…reated but no longer in use.

github-actions bot removed the Architecture Everything related to the Doc backend label Jul 22, 2025

iadjivon added 4 commits July 22, 2025 12:14

deleted test edits

5c1529c

edits for the links

b7cc915

fixed some vale issues

aa34fb4

changes

7565559

iadjivon commented Jul 22, 2025

View reviewed changes

iadjivon requested a review from janine-c July 22, 2025 18:18

janine-c reviewed Jul 24, 2025

View reviewed changes

iadjivon added 2 commits July 28, 2025 22:25

changes

8a2bf56

changes from review

6a55768

iadjivon requested review from michael-richey and janine-c July 29, 2025 16:41


		If you're also sending telemetry to Datadog using cloud provider integrations, you must add your cloud provider accounts in the DDR org.

		Datadog does not use cloud providers to receive telemetry data while the DDR site is passive.


		{{% /collapse-content %}}

		{{% collapse-content title=" 8. Update your Datadog Agent configuration" level="h5" %}}

	{{% collapse-content title=" 8. Update your Datadog Agent configuration" level="h5" %}}
	{{% collapse-content title=" 8. Send telemetry to your DDR org" level="h5" %}}


		{{% /collapse-content %}}

		{{% collapse-content title=" 10. Activate and test DDR failover in cloud integrations" level="h5" %}}



		## Prerequisites
		Datadog Disaster Recovery requires Datadog Agent version 7.54 or above. The APM product support requires a v7.68 or above.


		{{% collapse-content title="Retrieve the public IDs and link your DDR and primary orgs " level="h5" %}}

		After the Datadog team has set your DDR org, use the cURL commands from the Datadog [public API endpoint][8] to retrieve the public IDs of the primary and DDR org.

		To link your DDR and primary orgs, run these commands replacing the placeholders for their values:

		<div class="alert alert-warning"> For security reasons, Datadog is unable to link the orgs on your behalf. </div>

	Verify that your DDR org is accessible and that your Dashboards and Monitors are copied from your primary org to your DDR org.
	Verify that your DDR org is accessible and that your dashboards and monitors are copied from your primary org to your DDR org.


		{{% /collapse-content %}}

		{{% collapse-content title="Activate and test DDR failover in cloud integrations" level="h5" %}}


		<!-- ------------------------------- -->

		### 3. Test Run failover tests in various environments


		### 2. Set up access, integrations, syncing, and agents

		{{% collapse-content title="Create your Datadog API and App key for syncing" level="h5" %}}

DOCS-10575-DDR #29293

Are you sure you want to change the base?

DOCS-10575-DDR #29293

Uh oh!

Conversation

iadjivon commented May 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do? What is the motivation?

Merge instructions

Additional notes

Uh oh!

github-actions bot commented May 12, 2025

Preview links (active after the build_preview check completes)

New or renamed files

Uh oh!

datadog-datadog-prod-us1 bot commented May 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jhgilbert commented May 12, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

heyronhay left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📝 Documentation Team Review Required

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

michael-richey left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

janine-c left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

iadjivon left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

iadjivon commented May 12, 2025 •

edited

Loading

Preview links (active after the `build_preview` check completes)

datadog-datadog-prod-us1 bot commented May 12, 2025 •

edited

Loading

github-actions bot commented May 28, 2025 •

edited

Loading

janine-c Jul 23, 2025 •

edited by iadjivon

Loading

michael-richey Jul 29, 2025 •

edited

Loading