Monitor Google Cloud projects using auto-discovery
Early Adopter
Starting from the Google Cloud Monitor integration version 1.3.0+, you can extend your metric coverage beyond the predefined set of services supported by extensions.
- For a complete list of supported services, see Google Cloud supported service metrics.
To monitor any metric from any Google resource not covered by those services, follow the instructions on this page to activate auto-discovery.
Possible auto-discovery scenarios depend on the services from which you want to monitor metrics:
Expand metrics for already supported services
Integrate any service based on the resource name
Before you begin
This guide is a component of the main Dynatrace Google Cloud Metric and Log Integration setup, and focuses solely on auto-discovery configuration.
Minimum version
If Google Cloud integration has been previously set up using a version earlier than 1.3.0, you need to run a fresh deployment of the complete solution using version 1.3.0+.
Set up auto-discovery monitoring
Ensure permissions
If you are managing permissions manually, ensure the following permissions are added to the Dynatrace Google Cloud Metrics Monitor role.
monitoring.metricDescriptors.list
monitoring.monitoredResourceDescriptors.get
monitoring.monitoredResourceDescriptors.list
Enable auto-discovery metric enrichment
To enable the auto-discovery metric enrichment, edit the following parameter in values.yaml
:
metricAutodiscovery: "true"
Expand metrics for already supported services
Within the scope of standard supported services, a predetermined set of metrics is routinely sent to Dynatrace. For details on how to enable those services, see Choose services for metrics monitoring.
Auto-discovery mode, however, brings more flexibility by allowing the collection of all available metrics for a particular service.
Enable auto-discovery
To enable it, you need to modify the values.yaml
file by searching for the specific service as follows:
- service: cloud_service_nameallowAutodiscovery: True
Supported services
Expand the following table for a list of resources currently monitored by supported services that can be extended with auto-discovery.
Monitored resource | Service name |
---|---|
alloydb.googleapis.com/Database | Google AlloyDB |
alloydb.googleapis.com/Instance | Google AlloyDB |
api | Google Cloud APIs |
apigee.googleapis.com/Environment | Google Apigee |
apigee.googleapis.com/Proxy | Google Apigee |
apigee.googleapis.com/ProxyV2 | Google Apigee |
apigee.googleapis.com/TargetV2 | Google Apigee |
assistant_action_project | Google Assistant Smart Home |
autoscaler | Google Compute Engine |
aws_ec2_instance | Google Compute Engine |
baremetalsolution.googleapis.com/Instance | Google Compute Engine |
bigquery_biengine_model | Google BigQuery |
bigquery_project | Google BigQuery |
bigtable_cluster | Google Cloud Bigtable |
bigtable_table | Google Cloud Bigtable |
cloud_composer_environment | Google Cloud Composer |
cloud_dataproc_cluster | Google Dataproc |
cloud_dlp_project | Google Cloud Data Loss Prevention |
cloud_function | Google Cloud Functions |
cloud_run_job | Google Cloud Run |
cloud_run_revision | Google Cloud Run |
cloud_tasks_queue | Google Cloud Tasks |
cloudiot_device_registry | Google Cloud IoT Core |
cloudml_job | Google AI Platform |
cloudml_model_version | Google AI Platform |
cloudsql_database | Google Cloud SQL |
cloudsql_instance_database | Google Cloud SQL |
cloudvolumesgcp-api.netapp.com/CloudVolume | NetApp on Google Cloud |
consumed_api | Google Cloud APIs |
consumer_quota | Google Cloud APIs |
dataflow_job | Google Dataflow |
datastore_request | Google Firestore in Datastore mode |
dns_query | Google Cloud DNS |
filestore_instance | Google Cloud Filestore |
firebase_domain | Google Firebase |
firebase_namespace | Google Firebase |
firestore.googleapis.com/Database | Google Cloud Filestore |
firestore_instance | Google Cloud Filestore |
gae_app | Google App Engine |
gae_instance | Google App Engine |
gce_router | Google Hybrid Connectivity |
gce_zone_network_health | Google Network Topology |
gcs_bucket | Google Cloud Storage |
https_lb_rule | Google Cloud Load Balancing |
instance_group | Google Compute Engine |
interconnect | Google Hybrid Connectivity |
interconnect_attachment | Google Hybrid Connectivity |
internal_http_lb_rule | Google Cloud Load Balancing |
internal_tcp_lb_rule | Google Cloud Load Balancing |
internal_udp_lb_rule | Google Cloud Load Balancing |
istio_control_plane | Google Kubernetes Engine |
k8s_container | Google Kubernetes Engine |
k8s_node | Google Kubernetes Engine |
k8s_pod | Google Kubernetes Engine |
loadbalancing.googleapis.com/ExternalNetworkLoadBalancerRule | Google Cloud Load Balancing |
microsoft_ad_domain | Google Managed Microsoft AD |
nat_gateway | Google Cloud Router |
netapp_cloud_volume | NetApp on Google Cloud |
network_security_policy | Google Network Security |
produced_api | Google Cloud APIs |
producer_quota | Google Cloud APIs |
pubsub_snapshot | Google Pub/Sub |
pubsub_subscription | Google Pub/Sub |
pubsub_topic | Google Pub/Sub |
pubsublite_subscription_partition | Google Pub/Sub Lite |
pubsublite_topic_partition | Google Pub/Sub Lite |
recaptchaenterprise.googleapis.com/Key | Google reCAPTCHA Enterprise |
redis_instance | Google Memorystore |
spanner_instance | Google Cloud Spanner |
tcp_lb_rule | Google Cloud Load Balancing |
tcp_ssl_proxy_rule | Google Cloud Load Balancing |
tpu_worker | Google Compute Engine |
transfer_service_agent | Google Cloud Storage Transfer Service |
udp_lb_rule | Google Cloud Load Balancing |
vpc_access_connector | Google Virtual Private Cloud |
vpn_gateway | Google Hybrid Connectivity |
Integrate any service based on resource name
For situations where the extended monitoring capabilities of supported services are insufficient, Google Cloud auto-discovery provides a solution to monitor any service offered by Google.
Limitations
Auto-discovery mode is designed to detect only metrics linked to a single resource.
These metrics are not attached to any supported service, so there will be no entity or any enrichment extracted from them.
Configure parameter values
The helm deployment package contains the autodiscovery-values.yaml
file with the necessary configuration for this scenario. Edit this file to set the required and optional parameter values as follows.
Parameter name | Description | Default value |
---|---|---|
autodiscoveryQueryInterval | required Auto-discovery polling interval in minutes. Minimum value: 60 . | 60 |
autodiscoveryIncludeAlphaMetrics | optional When set to true , it enables the automatic discovery of experimental Google Cloud metrics withthe 'Alpha' label. | true |
autodiscoveryAddLabels | optional When set to true , it appends the label [Autodiscovered] to metric names during automatic discovery. | true |
autodiscoveryResourcesYaml | optional Configuration file for auto-discovery resources. | |
autodiscoveryBlockListYaml | optional Configuration file for auto-discovery metrics name prefixes that shoud not be included. |
Select resources
Specify the metrics to be sent to Dynatrace by listing the resource types of the monitored resources in the autodiscoveryResourcesYaml
section. To identify the resources for monitoring within your project, see Google Cloud metrics.
Example:
autodiscoveryResourcesYaml: |autodicovery_config:searched_resources:- memcache_node
Disable selected metrics
To exclude specific metrics, list their prefixes in the autodiscoveryBlockListYaml
section. Any matching metric will be excluded.
Example:
autodiscoveryBlockListYaml: |block_list:- memcache.googleapis.com/node/