Skip to content

Update datadog-disaster-recovery.md #35439

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.

Sign up for GitHub

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

Merged
iadjivon merged 7 commits into from
Mar 23, 2026
Merged

Update datadog-disaster-recovery.md #35439

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
9184598
Update datadog-disaster-recovery.md
iadjivon Mar 20, 2026
0ed44d7
Update datadog-disaster-recovery.md
iadjivon Mar 20, 2026
7f5f610
Apply suggestion from @iadjivon
iadjivon Mar 20, 2026
1c2378c
Apply suggestions from code review
iadjivon Mar 23, 2026
c30fb6e
Apply suggestion from @iadjivon
iadjivon Mar 23, 2026
2875aa1
Update content/en/agent/guide/datadog-disaster-recovery.md
iadjivon Mar 23, 2026
033df2d
Update content/en/agent/guide/datadog-disaster-recovery.md
iadjivon Mar 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions content/en/agent/guide/datadog-disaster-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,9 @@ Email your new org name to your [Customer Success Manager](mailto:success@datado

After the Datadog team has set your DDR org, use 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>` with your orgs' values:
To link your DDR org to your primary org:
- Add the `disaster_recovery_status_write` scope to your application key in the primary org.
- Run the following commands, replacing the placeholders with the appropriate values.


```shell
Expand All @@ -90,8 +92,8 @@ export PRIMARY_ORG_ID=<PRIMARY_ORG_PUBLIC_ID>
export USER_EMAIL=<USER_EMAIL>
export CONNECTION='{"data":{"id":"'${PRIMARY_ORG_ID}'","type":"hamr_org_connections","attributes":{"TargetOrgUuid":"'${DDR_ORG_ID}'","HamrStatus":1,"ModifiedBy":"'${USER_EMAIL}'", "IsPrimary":true}}}'

curl -v -H "Content-Type: application/json" -H
"dd-api-key:${PRIMARY_DD_API_KEY}" -H
curl -v -H "Content-Type: application/json" -H \
"dd-api-key:${PRIMARY_DD_API_KEY}" -H \
"dd-application-key:${PRIMARY_DD_APP_KEY}" --data "${CONNECTION}" --request POST ${PRIMARY_DD_API_URL}/api/v2/hamr
```
After linking your orgs, only the failover org displays this banner:
Expand Down Expand Up @@ -364,3 +366,4 @@ During testing, integration telemetry is spread over both organizations. If you
[16]: https://app.datadoghq.com/organization-settings/application-keys
[17]: https://docs.datadoghq.com/agent/configuration/dual-shipping/?tab=helm
[18]: https://docs.datadoghq.com/agent/fleet_automation/#overview
[19]: /account_management/rbac/permissions/#disaster-recovery
Loading