Manage GCP connections via gcloud CLI and dtctl

• Latest Dynatrace
• How-to guide
• Updated on Oct 29, 2026

The commands on this page use the variables from Environment variables.

Update monitoring settings

To modify a monitoring configuration, export it as YAML, edit the file, and apply the changes.

Discover available options

List available GCP regions:

dtctl get gcp monitoring-locations

List available feature sets (services to monitor):

dtctl get gcp monitoring-feature-sets

Custom resources and metrics

Ingest metrics from Google Cloud resource types not covered by the default feature sets, either by enabling auto-discovery for them or by selecting specific individual metrics.

To customize resources, export your configuration to YAML, add the resources section under value.googlecloud, and apply. Example:

value:
  googlecloud:
    # ... existing configuration ...
    resources:
      # Auto-discovery: collect all available metrics for this resource type
      - resourcetype: gcs_bucket
        autodiscoveryenabled: true

      # Specific metrics only
      - resourcetype: pubsub_topic
        autodiscoveryenabled: false
        metrics:
          - name: pubsub.googleapis.com/topic/send_request_count
            metriclabels:
              - response_class
            type: CUSTOM
          - name: pubsub.googleapis.com/topic/message_sizes
            type: CUSTOM

      # Auto-discovery with exclusions
      - resourcetype: gce_instance
        autodiscoveryenabled: true
        autodiscoveryexcludemetrictype:
          - compute.googleapis.com/instance/disk/*

Expand monitoring scope

To add projects, folders, or organizations to an existing connection, grant the required roles to your monitoring service account on each new scope. Use the same commands as in the initial setup, and repeat them for each new project, folder, or organization:

If your monitoring configuration filters projects or folders (projectfiltering, folderfiltering), add the new scope there too — see Update monitoring settings.

Enable log forwarding

Log forwarding requires deploying a Cloud Logging sink, Pub/Sub topic, and Dataflow streaming job in your Google Cloud project. Follow the Set up log forwarding steps from the initial setup guide.

After the infrastructure is deployed, update the monitoring configuration to enable log forwarding by setting the relevant property in config.yaml and applying via dtctl apply -f config.yaml.

Enable or update asset inventory feed

To deploy the asset inventory feed for the first time, follow the Set up the asset inventory feed steps from the initial setup guide.

To update an existing feed — add or remove tracked asset types — address the feed by the scope where you created it. Each command takes exactly one of --project, --folder, or --organization. If you created feeds in more than one scope, repeat the commands for each scope.

# Choose the scope of the feed you want to update (use exactly one)
SCOPE_FLAG="--project=${PROJECT_ID}"            # project-scope feed
# SCOPE_FLAG="--folder=${FOLDER_ID}"            # folder-scope feed
# SCOPE_FLAG="--organization=${ORG_ID}"         # organization-scope feed

gcloud asset feeds update dt-asset-feed-${MCONFIG_ID} \
    ${SCOPE_FLAG} \
    --add-asset-types="<asset-type>"    # for example, a type from the Cloud Asset supported-types list

To remove an asset type:

gcloud asset feeds update dt-asset-feed-${MCONFIG_ID} \
    ${SCOPE_FLAG} \
    --remove-asset-types="<asset-type>"

Verify the current feed configuration:

gcloud asset feeds describe dt-asset-feed-${MCONFIG_ID} ${SCOPE_FLAG}

Rotate Log Ingest token

If your Log Ingest token has expired or been revoked:

Pause and resume monitoring

To pause monitoring without deleting the configuration, disable it:

dtctl disable gcp monitoring <configuration-id>

This disables the configuration and its credentials. To resume, enable it again:

dtctl enable gcp monitoring <configuration-id>

Update the extension

The GCP monitoring extension (com.dynatrace.extension.da-gcp) is installed from the Dynatrace Hub. Monitoring configurations are version-pinned — installing a newer extension version does not automatically migrate existing configurations. You must explicitly update them.

1. Check the latest installed version

EXT="com.dynatrace.extension.da-gcp"
LATEST=$(dtctl get extension "$EXT" --no-agent -o json \
  | jq -r '.[].version' | sort -V | tail -1)
echo "Latest installed: $LATEST"

2. Install a new version from Hub

If you haven't activated the extension yet, see Prerequisites.

# Install latest available
dtctl create extension --hub-extension "$EXT"

# Install a specific version
dtctl create extension --hub-extension "$EXT" --version 1.2.0

3. Migrate monitoring configurations to the new version

EXT="com.dynatrace.extension.da-gcp"
LATEST=$(dtctl get extension "$EXT" --no-agent -o json \
  | jq -r '.[].version' | sort -V | tail -1)

dtctl get extension-configs "$EXT" --no-agent -o json | jq -c '.[]' | while read -r cfg; do
  ID=$(echo "$cfg" | jq -r '.objectId')
  CURRENT=$(echo "$cfg" | jq -r '.value.version')

  if [ "$CURRENT" = "$LATEST" ]; then
    echo "SKIP $ID (already $LATEST)"
    continue
  fi

  echo "UPGRADE $ID: $CURRENT → $LATEST"
  TMPFILE=$(mktemp /tmp/extcfg_XXXXXX.json)
  echo "$cfg" | jq --arg v "$LATEST" '.value.version = $v' > "$TMPFILE"
  dtctl apply extension-config "$EXT" -f "$TMPFILE"
  rm "$TMPFILE"
done

Delete a connection

Delete the Dynatrace connection and its monitoring configuration in the Settings app. See Delete a connection.