DOCS-10575-DDR #29293
DOCS-10575-DDR #29293
Conversation
Preview links (active after the
|
Datadog Summary✅ Code Quality ✅ Code Security ✅ Dependencies Was this helpful? Give us feedback! |
|
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
|
|
||
| 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 |
There was a problem hiding this comment.
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\ |
There was a problem hiding this comment.
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}}}' |
There was a problem hiding this comment.
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}'"}}}'
…jivon/DOCS-10575-DiRec-for-okr11
…jivon/DOCS-10575-DiRec-for-okr11
|
|
||
| ## 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. |
There was a problem hiding this comment.
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> |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
'<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. |
There was a problem hiding this comment.
I think we need to highlight this somehow and also include a statement to contact their CSM for help
📝 Documentation Team Review RequiredThis 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. |
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:
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:
Additional notes