Google Cloud supported services

Dynatrace version 1.230+

This section refers to Google Cloud service metrics that are available with Google Cloud version 1.0 integration.

Prerequisites

Deploy Dynatrace integration

Supported services for metrics

After deploying the Dynatrace integration, you can get insights into Google Cloud services metrics collected from the Google Operations API to ensure health of your cloud infrastructure.

Below, see the list of Google Cloud supported services.

Services

Supported entities1

Supported logs

Logs entities

cloudml_job, cloudml_model_version

yes

cloudml_job, cloudml_model_version

alloydb_database, alloydb_instance

yes

alloydb_database, alloydb_instance

no

apigee_environment, apigee_proxy, apigee_target

no

gae_app

yes

gae_app

no

bigquery_bigengine_model

no

bigtable_cluster, bigtable_table

no

no

cloud_function

yes

cloud_function

no

nat_gateway

yes

nat_gateway

cloud_function, cloud_run_revision

yes

cloud_run_revision

gcs_bucket

yes

gcs_bucket

cloud_tasks_queue

yes

cloud_tasks_queue

cloud_composer_environment

yes

cloud_composer_environment

autoscaler, gce_instance, instance_group, tpu_worker

yes

autoscaler, gce_autoscaler, gce_instance_group, gce_instance, tpu_worker

no

storage_transfer_job, transfer_service_agent

yes

storage_transfer_job

no

cloud_dataproc_cluster

yes

cloud_dataproc_cluster

no

filestore_instance

no

no

firestore_database

no

interconnect, interconnect_attachment, gce_router, vpn_gateway

yes

gce_router, vpn_gateway

k8s_cluster, k8s_container, k8s_node, k8s_pod

yes

k8s_cluster, k8s_container, k8s_node, k8s_pod

https_lb, internal_http_lb_rule, internal_network_lb_rule, network_lb_rule, tcp_ssl_proxy_rule

yes

http_load_balancer, internal_http_lb_rule, internal_network_lb_rule, network_lb_rule, tcp_ssl_proxy_rule

microsoft_ad_domain

no

redis_instance

yes

redis_instance

netapp_volumes_replication, netapp_volumes_storage_pool, netapp_volumes_volume

no

network_security_policy

yes

network_security_policy

uptime_url

yes

uptime_url

pubsub_snapshot, pubsub_subscription, pubsub_topic

yes

pubsub_snapshot, pubsub_subscription, pubsub_topic

subscription_partition, topic_partition

no

spanner_instance

yes

spanner_instance

cloudsql_database

yes

cloudsql_database

vpc_access_connector

yes

vpc_access_connector

no

vertex_ai_deployment_resource_pool,
vertex_ai_endpoint,
vertex_ai_feature_online_store,
vertex_ai_feature_store,
vertex_ai_pipeline_job,
vertex_ai_index, vertex_ai_index_endpoint,
vertex_ai_publisher_model,
vision_ai_instance,
vision_ai_stream

yes

vertex_ai_deployment_resource_pool,
vertex_ai_endpoint,
vertex_ai_feature_store,
vertex_ai_pipeline_job,
vertex_ai_index_endpoint

1

Services might have one entity, several entities, or none. For each entity, you can see metrics, properties, logs, errors, and many more in Dynatrace Clouds app.

Check available metrics

To check available metrics for a service, you need to

  1. Find the extension in the Hub and select it to open the overview page. See example: Google Cloud Functions.
  2. Scroll down to the bottom of the overview page of the extension to find the Feature sets section.
  3. In the table, select the default_metrics dropdown.
  4. Now, you can check all available metrics for the chosen service.

Monitoring consumption

Metric ingestion

All cloud services consume DDUs. The amount of DDU consumption per service instance depends on the number of monitored metrics and their dimensions (each metric dimension results in the ingestion of 1 data point; 1 data point consumes 0.001 DDUs). For details, see Extending Dynatrace (Davis data units).

Log ingestion

DDU consumption applies to cloud Log Monitoring. See DDUs for Log Monitoring for details.

Related topics