Migrate to GCP integration version 1.0

Dynatrace version 1.230+

The new version of the GCP integration (v.1.0) uses Extensions 2.0 and introduces custom topology for a number of GCP services.

List of services with custom topology

Google Compute Engine
Google Cloud Storage
Google Cloud Functions
Google Cloud Run
Google App Engine
Google Cloud Tasks
Google Cloud SQL
Google Cloud Datastore
Google Load Balancing
Google Cloud NAT Gateway
Google Filestore
Google Kubernetes Engine
Google Pub/Sub
Google Pub/Sub Lite
Google Memorystore
Google Spanner

Note that your existing metric dimension names will change when you switch to GCP integration using Dynatrace Extensions 2.0. Dimension name changes affect all configured managements zones, custom alerts, and custom dashboards in your environment. To restore proper functionality for these entities, please follow the instructions below.

Note: Upgrading existing dynatrace-gcp-monitor installations from earlier versions is not supported. You need to first delete your existing deployment and then install the GCP integration v.1.0. For instructions, see below.

Delete existing deployment

Remove dashboards and/or alerts

Install new GCP deployment

Update dimensions

Delete existing deployment

For Kubernetes container deploymentFor GC Function deployment

Find out what release version you're using.
```
plaintext
helm ls -n dynatrace
```
Uninstall the release.

Note: Be sure to replace <release-name> with the release name from the previous output.
```
plaintext
helm uninstall <release-name> -n dynatrace
```

Uninstall the release.

bash
wget https://raw.githubusercontent.com/dynatrace-oss/dynatrace-gcp-monitor/master/scripts/uninstall.sh -O uninstall.sh ; chmod a+x uninstall.sh ; ./uninstall.sh

Remove the activation-config.yaml service configuration file.

Remove dashboards and/or alerts

You need to manually remove any dashboards or alerts created manually during the previous installation.

Install new GCP deployment

To install the new GCP deployment, see Set up the Dynatrace GCP metric and log integration (v.1.0) on a new GKE Autopilot cluster.

Update dimensions

If you created your own dashboards, alerts, or management zones based on GCP metrics, you need to manually update the dimensions according to the list below in order to get links for entities.

List of dimension changes

Old dimension name	New dimension name
`project_id`	`gcp.project.id`
`region`	`gcp.region`
`zone`	`gcp.region`
`instance_id`	`gcp.instance.id`
`autoscaler_id`	`gcp.instance.id`
`model_id`	`gcp.instance.id`
`queue_id`	`gcp.instance.id`
`device_registry_id`	`gcp.instance.id`
`job_id`	`gcp.instance.id`
`version_id`	`gcp.instance.id`
`database_id`	`gcp.instance.id`
`volume_id`	`gcp.instance.id`
`router_id`	`gcp.instance.id`
`instance_group_id`	`gcp.instance.id`
`interconnect`	`gcp.instance.id`
`attachment`	`gcp.instance.id`
`volume_id`	`gcp.instance.id`
`snapshot_id`	`gcp.instance.id`
`subscription_id`	`gcp.instance.id`
`topic_id`	`gcp.instance.id`
`key_id`	`gcp.instance.id`
`worker_id`	`gcp.instance.id`
`agent_id`	`gcp.instance.id`
`gateway_id`	`gcp.instance.id`
`name`	`gcp.instance.name`
`autoscaler_name`	`gcp.instance.name`
`environment_name`	`gcp.instance.name`
`cluster_name gcp.instance.name`	`gcp.instance.name`
`function_name gcp.instance.name`	`gcp.instance.name`
`revision_name`	`gcp.instance.name`
`job_name`	`gcp.instance.name`
`instance_name`	`gcp.instance.name`
`domain_name`	`gcp.instance.name`
`table_name`	`gcp.instance.name`
`firewall_name`	`gcp.instance.name`
`bucket_name`	`gcp.instance.name`
`container_name`	`gcp.instance.name`
`url_map_name`	`gcp.instance.name`
`instance_group_name`	`gcp.instance.name`
`load_balancer_name`	`gcp.instance.name`
`canonical_service_name`	`gcp.instance.name`
`node_name`	`gcp.instance.name`
`pod_name`	`gcp.instance.name`
`broker_name`	`gcp.instance.name`
`revision_name`	`gcp.instance.name`
`trigger_name`	`gcp.instance.name`
`fqdn`	`gcp.instance.name`
`target_domain_name`	`gcp.instance.name`
`gateway_name`	`gcp.instance.name`
`policy_name`	`gcp.instance.name`
`proxy_name`	`gcp.instance.name`
`load_balancer_name`	`gcp.instance.name`
`backend_target_name`	`gcp.instance.name`
`connector_name`	`gcp.instance.name`
`gateway_name`	`gcp.instance.name`

To update dimensions for dashboards
1. In the Dynatrace menu, go to Dashboards.
2. Select the dashboard for which you want to update dimensions, and then select More (…) > Configure.
3. Select Dashboard JSON.
4. In the "splitBy" section, replace the old dimensions with the new values as determined from the list of dimension changes.
5. Select Save changes.

Alternatively, you can replace the dimensions by configuring each dashboard tile of a selected dashboard in Data explorer.

To update dimensions for alerts
1. In the Dynatrace menu, go to Settings.
2. In Anomaly detection, select Metric events.
3. Select the event for which you want to update dimensions.
4. In the Add dimension filter field, select the new dimension keys and enter the corresponding dimension values as determined from the list of dimension changes.
5. Select Save changes.
To update dimensions for management zones
1. In the Dynatrace menu, go to Settings.
2. In Preferences, select Management zones.
3. Select Edit for the management zone for which you want to update dimensions.
4. Select Edit to edit an existing rule.
5. In Conditions, edit the DIMENSION value according to the List of dimension changes.
6. Select Save changes.