Skip to content

Document optional BigQuery Location field - #39764

Open
lisaah wants to merge 1 commit into
masterfrom
dd/lisa.huynh/bigquery-experiment-location-field
Open

Document optional BigQuery Location field#39764
lisaah wants to merge 1 commit into
masterfrom
dd/lisa.huynh/bigquery-experiment-location-field

Conversation

@lisaah

@lisaah lisaah commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Documents the new optional Location field in the BigQuery warehouse connection settings for Datadog Experiments, added in https://github.com/ddoghq/dd-source/pull/78991.

Customers whose BigQuery dataset lives in a non-default region need a way to tell Datadog where to submit experiment queries. This adds that field to the existing setup steps.

Changes:

  • Added a Location (optional) bullet to the Dataset and GCS Bucket field list in the BigQuery branch of ## Step 3: Configure experiment settings in hugo/content/en/experiments/guide/connecting_a_data_warehouse.mdoc.md.
  • The entry explains what to enter (the location of the dataset created in Step 1, for example europe-west2), that Datadog submits experiment queries in that location, and that leaving it blank lets BigQuery infer the location.

Testing:

  • Verified the new bullet matches the surrounding field-list format, including the page's existing Field (optional): convention used by the Copy IAM role ARN field in the Redshift branch, and the [Step 1](#create-a-bigquery-dataset) anchor already used by the sibling Dataset field.
  • Checked the copy against the substitution and temporal-word tables in CLAUDE.md (no ensure, via, just, will, currently, and so on). Vale is not installed in this environment, so this check was manual.
  • Confirmed the change is scoped to the BigQuery {% if equals($database, "bigquery") %} block and does not affect the Databricks, Redshift, or Snowflake branches.
  • Left the screenshot alt text unchanged, since the existing image does not show the new field.

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Drafted with Bits Code, then reviewed against the page's existing field-list conventions and the repo style guide.

Additional notes

The field label is documented as Location, matching the short labels used by the sibling Dataset and GCS Bucket fields. Please confirm this matches the label shipped in the UI.


PR by Bits - View session in Datadog

Comment @DataDog to request changes

@datadog-datadog-prod-us1

Copy link
Copy Markdown
Contributor

View session in Datadog

Bits Code status: ✅ Done

CI Auto-fix: Disabled | Enable

Comment @DataDog to request changes

@lisaah
lisaah requested a review from a team as a code owner September 8, 2026 04:13
@lisaah
lisaah requested a review from a team as a code owner September 8, 2026 04:13
@datadog-datadog-us1-prod

Copy link
Copy Markdown
Contributor

I can only run on private repositories.

@github-actions github-actions Bot added Guide Content impacting a guide cdocs labels Sep 8, 2026
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@drichards-87 drichards-87 self-assigned this Sep 8, 2026
@drichards-87 drichards-87 removed their assignment Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bits AI cdocs Guide Content impacting a guide

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants