[PANA-6501] Add browser-intake domains to allowedRegions exact_domains#35325
Merged
[PANA-6501] Add browser-intake domains to allowedRegions exact_domains#35325
Conversation
The Product Analytics server-side events API endpoint uses browser-intake-*
domains (e.g., browser-intake-datadoghq.com) which don't follow the standard
{subdomain}.{site} pattern. The API reference template resolves region support
by matching endpoint server domains against allowedRegions in params.yaml.
Since browser-intake domains didn't match any allowedRegions[].domain (primary
pass) or allowedRegions[].exact_domains (fallback pass), the endpoint resolved
to zero regions. The template then rendered a hidden "Not supported in the
{REGION} region" span for each region, and since the docs site defaults to
showing the US region, users saw "Not supported in the US region".
This adds the browser-intake-* domains to exact_domains for each region so
the fallback matching pass correctly maps each intake domain to its region.
Also fixes a pre-existing YAML formatting issue in the EU region's
exact_domains list (missing list prefix).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
onceLearner
approved these changes
Mar 17, 2026
genesor
pushed a commit
that referenced
this pull request
Apr 19, 2026
#35325) The Product Analytics server-side events API endpoint uses browser-intake-* domains (e.g., browser-intake-datadoghq.com) which don't follow the standard {subdomain}.{site} pattern. The API reference template resolves region support by matching endpoint server domains against allowedRegions in params.yaml. Since browser-intake domains didn't match any allowedRegions[].domain (primary pass) or allowedRegions[].exact_domains (fallback pass), the endpoint resolved to zero regions. The template then rendered a hidden "Not supported in the {REGION} region" span for each region, and since the docs site defaults to showing the US region, users saw "Not supported in the US region". This adds the browser-intake-* domains to exact_domains for each region so the fallback matching pass correctly maps each intake domain to its region. Also fixes a pre-existing YAML formatting issue in the EU region's exact_domains list (missing list prefix). Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
2 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.
Problem
The Product Analytics server-side events API endpoint uses browser-intake-* domains (e.g., browser-intake-datadoghq.com) which don't follow the standard {subdomain}.{site} pattern. The API reference template resolves region support by matching endpoint server domains against allowedRegions in params.yaml. Since browser-intake domains didn't match any allowedRegions[].domain (primary pass) or allowedRegions[].exact_domains (fallback pass), the endpoint resolved to zero regions. The template then rendered a hidden "Not supported in the {REGION} region" span for each region, and since the docs site defaults to showing the US region, users saw "Not supported in the US region".
Fix
This adds the browser-intake-* domains to exact_domains for each region so the fallback matching pass correctly maps each intake domain to its region.
Also fixes a pre-existing YAML formatting issue in the EU region's exact_domains list (missing list prefix).
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass 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.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
AI assistance
Additional notes