GCP Resources

This page documents how Dash0 identifies and names Google Cloud Platform resources using GCP semantic conventions from OpenTelemetry.

Full Resource Names

Most GCP resources are identified through cloud.resource_id, which carries the Cloud Asset Inventory full resource name. Dash0 recognizes the following formats.

Equality Rules

GCP resources are identified either by their platform-specific attributes or by their globally unique cloud.resource_id. Rules are evaluated in order, and the first match wins.

• Cloud Run through cloud.platform: cloud.platform == "gcp_cloud_run" + cloud.account.id + cloud.region (or cloud.availability_zone) + faas.name. This is the same rule that covers AWS Lambda. All instances of the same Cloud Run service in the same region and account are grouped together. Missing cloud.account.id or region attributes do not break the rule, they contribute a fixed placeholder to the identity instead.
• Any GCP resource with a full resource name: cloud.provider == "gcp" + cloud.resource_id. This covers Cloud Run services and jobs, Pub/Sub topics and subscriptions, Cloud Storage buckets, and Cloud SQL instances, since the full resource name is globally unique on its own.
• Fallback on cloud.resource_id alone: applied when cloud.provider is absent, and only after the service.namespace + service.name + service.instance.id triplet has been tried.
• Fallback on the account: cloud.account.id + cloud.provider + cloud.platform. Resources that match nothing more specific collapse into a single per-project resource.

Naming Rules

Names are also resolved by first match. The faas.name rules rank above the cloud.resource_id rules, so a Cloud Run service that reports faas.name is named from that attribute even when it also carries a full resource name.

If the prefix matches but no name can be extracted from the full resource name, Dash0 falls back to a fixed service display name: Google Cloud Run, Google Pub/Sub, Google Cloud Storage, or Google Cloud SQL. These fallbacks rank below service.name, so a resource that reports a service name keeps it. The last resort is gcp:<cloud.account.id>.

Typing Rules

GCP resource types are assigned based on the cloud.platform attribute or the cloud.resource_id prefix.

Resources that match none of these fall back to the cloud.account type.

Pub/Sub topics and subscriptions share the gcp.pubsub type, and Cloud Run services and jobs share the gcp.cloud.run type. Dash0 distinguishes them in the UI through the resource name and the full resource name.

Examples

• Cloud Run Service: For a service named api-service in region us-central1, the name will be api-service:us-central1 and the type gcp.cloud.run
• Cloud Run Job: For cloud.resource_id = //run.googleapis.com/projects/my-project/locations/us-central1/jobs/nightly-export, the name will be nightly-export and the type gcp.cloud.run
• Pub/Sub Topic: For cloud.resource_id = //pubsub.googleapis.com/projects/my-project/topics/events-topic, the name will be events-topic and the type gcp.pubsub
• Pub/Sub Subscription: For cloud.resource_id = //pubsub.googleapis.com/projects/my-project/subscriptions/events-worker, the name will be events-worker and the type gcp.pubsub
• GCS Bucket: For cloud.resource_id = //storage.googleapis.com/my-data-bucket, the name will be my-data-bucket and the type gcp.cloud.storage
• Cloud SQL Instance: For cloud.resource_id = //cloudsql.googleapis.com/projects/my-project/instances/orders-db, the name will be orders-db and the type gcp.cloud.sql

Best Practices

• Use GCP resource detectors to automatically populate project, region, and service information
• Include cloud.account.id and cloud.region for proper resource identification and multi-region deployments
• Set faas.name for Cloud Run services to ensure proper resource grouping
• Set cloud.resource_id to the full resource name for Pub/Sub, Cloud Storage, and Cloud SQL to enable resource correlation
• Set cloud.provider to gcp so resources match the GCP equality rule instead of falling through to the generic rules
• Keep the region consistent across data paths. A resource reported with a zonal region from one source and a regional one from another can fragment when the region is part of its identity

Further Reading

For more information on resource equality and GCP-specific configurations, explore the following resources.

Related Topics in This Section

• About Resources: Overview of resources in Dash0
• Explore Resources: Get started exploring resources in Dash0
• Why Resource Equality?: Practical examples of resource fragmentation scenarios

Dash0 Guides & Knowledge

• What are OpenTelemetry Resources?: Deep dive into how resources describe which system is generating telemetry data
• Service Attributes Best Practices: Learn what resource attributes are and how they can be categorized
• Kubernetes Attributes Best Practices: Best practices for Kubernetes resource attributes

OpenTelemetry Resources

• GCP Semantic Conventions: Official specification for GCP resource attributes
• FaaS Semantic Conventions: Cloud Run and serverless attributes
• Messaging Semantic Conventions: Pub/Sub messaging attributes
• OpenTelemetry SDKs: Language-specific SDK documentation

Google Cloud Resources

• Full resource names: Format of the identifiers used in cloud.resource_id
• Supported asset types: Cloud Asset Inventory asset type reference