[GCP-3635] Clarify Additional Locations field for GCP region filtering#36729
Merged
Conversation
Explain that the region filter uses an exact match against the GCP-reported label, and that nuanced region/zone/location values not shown in the checkboxes should be entered in the Additional Locations field. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Preview links (active after the
|
Drop the zonal example from the Additional Locations note (one example is enough), and remove the stray comma in the collapse section title. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Now that the zonal example is removed, the description lists only region and location values. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cswatt
approved these changes
May 15, 2026
buraizu
approved these changes
May 15, 2026
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? What is the motivation?
Addresses GCP-3635
Customers configuring region filtering on the Google Cloud integration sometimes have region, zone, or location label values that don't match the standard checkboxes (for example,
us-centralinstead ofus-central1). The previous copy mentioned the Additional Locations field only briefly and didn't explain that the filter is an exact match, so customers weren't realizing they could resolve mismatches by entering the precise label value there.This PR rewords the region-filtering section to:
us-central,us-central1-f) so customers know to use the precise value from their resources.Preview link: https://docs-staging.datadoghq.com/sujay.desai/gcp-3635-region-filter-docs/getting_started/integrations/google_cloud/?tab=orglevel#google-cloud-integrations