8000 DOCS-10575-DDR by iadjivon · Pull Request #29293 · DataDog/documentation · GitHub
[go: up one dir, main page]

Skip to content

DOCS-10575-DDR #29293

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

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

DOCS-10575-DDR #29293

wants to merge 15 commits into from

Conversation

iadjivon
Copy link
Contributor
@iadjivon iadjivon commented May 12, 2025

What does this PR do? What is the motivation?

New DDR doc.
This is a work in progress, but would appreciate any initial feedback!

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

@iadjivon iadjivon requested a review from a team as a code owner May 12, 2025 19:24
@github-actions github-actions bot added the Guide Content impacting a guide label May 12, 2025
@iadjivon iadjivon added the okr11 label May 12, 2025
Copy link
Contributor

Preview links (active after the build_preview check completes)

New or renamed files

@datadog-datadog-prod-us1
Copy link

Datadog Summary

✅ Code Quality    ✅ Code Security    ✅ Dependencies


Was this helpful? Give us feedback!

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

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!

< 8000 input type="hidden" name="_method" value="put" autocomplete="off" />


curl -v -H "Content-Type: application/json" -H
"dd-api-key:${CRDR_DD_API_KEY}" -H
"dd-application-key:${CRDR_DD_APP_KEY}" --data "${CONNECTION}" --request POST ${CRDR_DD_API_URL}/api/v2/hamr
Copy link
@michael-richey michael-richey May 19, 2025 8000

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change from CRDR_ to PRIMARY_

```shell
export DDR_DD_API_KEY=<>
export DDR_DD_APP_KEY=
export DDR_DD_API_URL=https://api.datadoghq.com\

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These need to be PRIMARY_ not DDR_.
The URL shouldn't have a back slash at the end.
The URL should be api site of their primary org

export DDR_ORG_ID=<DDR_ORG_PUBLIC_ID>
export PRIMARY_ORG_ID=<PRIMARY_ORG_PUBLIC_ID>
export USER_EMAIL=<USER_EMAIL>
export CONNECTION='{"data":{"id":"'${DDR_ORG_ID}'","type":"hamr_org_connections","attributes":{"TargetOrgUuid":"'${PRIMARY_ORG_ID}'","HamrStatus":1,"ModifiedBy":"'${USER_EMAIL}'","IsPrimary":true}}}'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is slightly simpler and does the same thing:

export CONNECTION='{"data":{"id":"'${PRIMARY_ORG_ID}'","type":"hamr_org_connections","attributes":{"TargetOrgUuid":"'${DDR_ORG_ID}'","HamrStatus":1,"ModifiedBy":"'${USER_EMAIL}'"}}}'

Copy link
Contributor
@heyronhay heyronhay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments - looks pretty great overall, though!


## Overview
Datadog Disaster Recovery (DDR) provides you with observability continuity in rare outage events that may impact a cloud service provider region or Datadog services running within a cloud provider region. In such cases, DDR enables your organization to meet critical observability, availability, and business continuity goals. You can also recover live observability at an alternate, functional Datadog site in typically under an hour with DDR. <br><br>
Additionally, Datadog Disaster Recover allows you to periodically conduct disaster recovery drills to not only test your ability to recover from outage events but to also meet your business and regulatory compliance needs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recover -> Recovery

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datadog Disaster Recovery (DDR) provides you with observability continuity during events that may impact a cloud service provider region or Datadog services running within a cloud provider region. Using DDR, you can recover live observability at an alternate, functional Datadog site in typically under two hours with DDR, enabling you to meet your critical observability availability goals.

DDR allows you to periodically conduct disaster rec 8000 overy drills to not only test your ability to recover from outage events but to also meet your business and regulatory compliance needs.

| EU1 | `https://app.datadoghq.eu` | `datadoghq.eu` | EU (Germany) |
| AP1 | `https://ap1.datadoghq.com` | `ap1.datadoghq.com` | Japan |

For example, if you are hosted in `US1` (https://app.datadoghq.com), you may choose to select the `US5` Datadog site **which is hosted on GCP Central US and is geographically separated from your primary organization**(`INCLUDE THIS?`). This ensures observability continuity in the event of a regional disaster.<br><br>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think instead of giving out geographical data, we should instead say, "contact your CSM if you need help choosing a site" or something

{{% collapse-content title=" 3. Confirm the public IDs of your orgs" level="h5" %}}
Once the Datadog team has completed the configuration of the designated orgs, they will share with you the public IDs of the primary org and the DDR org. You can confirm these IDs using the cURL commands from the Datadog [public API endpoint][8]:

**Note:** If any of your sites is in a region other than the `US1` region, you would need to specify the <SITE> parameter.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'<SITE>' isn't showing up in the rendered doc.

{{% collapse-content title=" 5. Create your Datadog API and App key for syncing" level="h5" %}}
At the secondary Datadog site, create a set of `API key` **and** `App key`. You will use these keys in _steps 7_ to copy dashboards and monitors between Datadog sites.

For your Agents, Datadog can copy API key signatures to the secondary backup account for you to prevent you from maintaining another set of API keys for your Agent.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to highlight this somehow and also include a statement to contact their CSM for help

Copy link
Contributor

📝 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Guide Content impacting a guide okr11 WORK IN PROGRESS No review needed, it's a wip ;)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0