Update doc for synthetics-private-locations#601
Merged
Conversation
melkouri
marked this pull request as ready for review
June 30, 2026 14:50
|
aletournel
reviewed
Jun 30, 2026
|
|
||
| 1. **Confirm the PL appears in both orgs.** Check the Synthetics → Settings → Private | ||
| Locations page in each org. The PL should be listed with the same name in both. | ||
| 2. **Confirm the worker reports.** The PL should show as healthy in both orgs once the |
Member
There was a problem hiding this comment.
I don't agree with it because a PL can only be reporting to main DCs (and so one org) at a time. During the exercice only the DC where the override CNAME was point to, had an "healthy" PL
aletournel
reviewed
Jun 30, 2026
| worker starts polling. If it only reports in one, double-check that the CNAME's current | ||
| DNS target is the region you expect. | ||
| 3. **Run a test.** Create a test in either org targeting the replicated PL, unpause it, | ||
| and confirm results appear. During steady state, results land in your primary region; |
Member
There was a problem hiding this comment.
Same the result will appear only in the org/main DC that the CNAME used in datadogHostOverride parameter is resolving to.
aletournel
reviewed
Jun 30, 2026
Comment on lines
+67
to
+88
| --datadog-host-override <your-failover-cname>.synthetics.datadoghq.com | ||
| ``` | ||
|
|
||
| ### The `--datadog-host-override` flag | ||
|
|
||
| When you replicate a PL into the destination org, the tool needs to know which intake | ||
| hostname the destination-side PL should report to. You pass this via the | ||
| `--datadog-host-override` flag (or `DD_DATADOG_HOST_OVERRIDE` env var). | ||
|
|
||
| The value should be the **CNAME** that your DNS controls — the one whose target you flip | ||
| when failing over from one region to another. Example: | ||
|
|
||
| ```bash | ||
| --datadog-host-override <your-failover-cname>.synthetics.datadoghq.com | ||
| ``` | ||
|
|
||
| That CNAME gets stored as `datadogHostOverride` in the destination PL's config, which the | ||
| worker then picks up. | ||
|
|
||
| If you don't pass the flag, the destination PL gets created without a `datadogHostOverride`, | ||
| which means the worker will fall back to the standard region intake for the secondary org. | ||
| That's usually **not** what you want for a failover setup — pass the flag. |
Member
There was a problem hiding this comment.
As discussed this part maybe simplified or removed as we probably don't need to take care of the datadogHostOverride during the sync.
The next section Configuring datadogHostOverride on your PL workers is what actually matter
…erride from sync command - PL worker reports to only one datacenter at a time (the one the CNAME resolves to), not both simultaneously - Remove --datadog-host-override flag from datadog-sync-cli examples; datadogHostOverride is configured on the worker, not the CLI - Fix verifying steps to reflect that only the active region's org shows the PL as healthy Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
…fiers Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
heyronhay
approved these changes
Jul 1, 2026
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
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?
Adds documentation for using Synthetics Private Locations with the Disaster Recovery (DDR) setup.
Description of the Change
Adds
docs/synthetics-private-locations.md, a guide explaining how to replicate Synthetics Private Locations from a source to a destination org usingdatadog-sync-cli, and how to configure the PL worker'sdatadogHostOverridefor failover. Updates the README to listsynthetics_private_locationsas a supported resource with a link to the new guide.