Skip to content
Draft
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions content/en/getting_started/integrations/google_cloud.md
Original file line number Diff line number Diff line change
Expand Up @@ -340,6 +340,14 @@ To apply granular metric filtering for enabled services, click on the service in

{{% /collapse-content %}}

{{% collapse-content title="Limit metric collection by Google Cloud region, and by global resources" level="h4" %}}

Under the **Metric Collection** tab in Datadog's [Google Cloud integration page][11], deselect which region for Datadog to exclude from metrics collection.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could it be multiple regions?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good call can update since there may be multiple regions to deselect.


Additionally, users can specify additional locations not listed and disable any global metrics not associated with a region.

{{% /collapse-content %}}

{{% collapse-content title="Limit metric collection by host or Cloud Run instance" level="h4" %}}
1. Assign a tag (such as `datadog:true`) to the hosts or Cloud Run instances you want to monitor with Datadog.
2. Under the **Metric Collection** tab in Datadog's [Google Cloud integration page][11], enter the tags in the **Limit Metric Collection Filters** textbox. Only hosts that match one of the defined tags are imported into Datadog. You can use wildcards (`?` for single character, `*` for multi-character) to match many hosts, or `!` to exclude certain hosts. This example includes all `c1*` sized instances, but excludes staging hosts:
Expand Down
Loading