Try it free

Manage GCP connections via Settings app

  • Latest Dynatrace
  • How-to guide

Go to Settings Settings > Collect and capture > Cloud and virtualization > Google Cloud to manage your connections.

Update monitoring settings

To change metrics, filters, enrichment rules, or the monitored scope:

  1. Select the connection name, or select and choose Manage.
  2. Modify the desired settings.
  3. Select Save to apply changes.

Changes to Dynatrace-side settings take effect immediately. Some changes also require updates to your Google Cloud resources—see the sections below.

Expand monitoring scope

To add projects, folders, or organizations to an existing connection:

  1. Edit the connection and update the monitored scope settings.
  2. Select Save.
  3. Grant the required IAM roles to the service account on each new project or folder.

roles/browser at folder level is required for folder filtering. Granting it only at project level is not sufficient.

Enable log forwarding

Log forwarding requires Google Cloud infrastructure (Cloud Logging sink, Pub/Sub, Dataflow job) that is not deployed automatically when you toggle the setting.

  1. Edit the connection and enable Log forwarding.
  2. Select Save.
  3. Deploy the log forwarding infrastructure:
    • Via Terraform: set logs_enabled = true in terraform.tfvars and re-apply—see Via Terraform.
    • Via gcloud CLI: follow the manual log forwarding setup—see Via gcloud CLI and dtctl.

Enable or update asset inventory feed

The asset inventory feed requires Google Cloud infrastructure (Cloud Asset feed, Pub/Sub topic and subscription) that must be deployed separately.

  1. Edit the connection and enable Asset inventory feed.
  2. Select Save.
  3. Deploy or update the feed infrastructure:
    • Via Terraform: set asset_feed_enabled = true in terraform.tfvars and re-apply—see Via Terraform.
    • Via gcloud CLI: follow the manual asset feed setup—see Via gcloud CLI and dtctl.

Rotate Log Ingest token

If your Log Ingest token has expired or been revoked:

  1. In Dynatrace, create a new platform token with the data-acquisition:logs:ingest scope.
  2. Update the token in the deployed Google Cloud infrastructure:
    • Via Terraform: update the token variable and re-apply—see Via Terraform.
    • Via gcloud CLI: update the Secret Manager secret and restart the Dataflow job—see Via gcloud CLI and dtctl.

Pause and resume monitoring

Temporarily disable a connection to stop data collection without deleting it.

  1. Select on the right-hand side of the connection row.
  2. Select Disable or Enable.

When a connection is disabled:

  • Dynatrace stops polling metrics and topology from Google Cloud.
  • Log and asset inventory forwarding (if configured) continues until you disable the Google Cloud infrastructure.
  • The connection configuration is preserved.
  • Historical data already ingested remains in Dynatrace.

To resume monitoring, select Enable from the same menu.

Update the extension

Use Extensions Extensions to install a newer version of the GCP monitoring extension and manage individual monitoring configurations.

Install a newer extension version

  1. Go to Extensions Extensions > Discover.
  2. Search for Google Cloud Monitoring and select the extension tile.
  3. Select Available versions and install the latest version.

Monitoring configurations are version-pinned—installing a newer version does not automatically migrate existing configurations. After installing, migrate the configurations in one of these ways:

  • In Extensions Extensions, select Upgrade all configurations.
  • Use dtctl.

Delete a connection

If you created the connection with the Terraform bundle, don't delete it here. Run terraform destroy instead—it removes the connection, the monitoring configuration, and the Google Cloud resources that Terraform created together. See Via Terraform. Deleting a Terraform-managed connection in the Settings app leaves Terraform's state inconsistent.

For connections you created in the Settings app or with dtctl, delete the Dynatrace connection before removing Google Cloud resources. Deleting GCP resources first causes authentication failures and makes it harder to track what remains to clean up.

Deleting a connection in Dynatrace doesn't remove anything in Google Cloud. You must also delete the Google Cloud resources that were created for the connection. Deleting them is your responsibility.

  1. Go to Settings Settings > Collect and capture > Cloud and virtualization > Google Cloud.
  2. Select on the right of the connection row, then select Delete and confirm.

When a connection is deleted:

  • Dynatrace stops polling metrics and topology from Google Cloud.
  • Historical data already ingested remains in Dynatrace (subject to retention policies).
  • Google Cloud resources (service account, IAM bindings, forwarding infrastructure) are not automatically removed.

To clean up Google Cloud resources:

  • Deployed with Terraform: run terraform destroy. It removes the resources that Terraform created. Adapt the cleanup to your own changes, because Terraform doesn't know about resources you added or changed yourself, such as log sinks. See Via Terraform.
  • Deployed manually with the gcloud CLI: delete the resources you created yourself. See Via gcloud CLI and dtctl.
Related tags
Infrastructure Observability