Dash0 Raises $110M Series B at $1B Valuation

Last updated: May 7, 2026

GCP Resources

Resource equality rules and naming conventions for Google Cloud Run, Pub/Sub, and Cloud Storage.

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

Tip

GCP resource detectors in OpenTelemetry SDKs automatically populate project, region, and service information. Enable the GCP resource detector for automatic attribute population.

Equality Rules

GCP resources are identified using service-specific attributes that uniquely identify each resource instance.

  • Google Cloud Run: cloud.platform == "gcp_cloud_run" + cloud.account.id + cloud.region (or cloud.availability_zone) + faas.name. All instances of the same Cloud Run service in the same region and account are grouped together. Alternatively, can be identified by cloud.provider == "gcp" + cloud.resource_id matching //run.googleapis.com/... pattern.
  • Google Cloud Pub/Sub: cloud.provider == "gcp" + cloud.resource_id (Pub/Sub resource identifier matching //pubsub.googleapis.com/... pattern)
  • Google Cloud Storage: cloud.provider == "gcp" + cloud.resource_id (bucket resource identifier matching //storage.googleapis.com/... pattern)
Note

Cloud Run resources are identified by service name (like AWS Lambda), not per-instance. All instances of the same service share the same resource identity. GCP services can be identified either through platform-specific equality rules (Cloud Run using faas.name) or through the generic cloud.resource_id pattern matching approach (for Pub/Sub, Cloud Storage, and as an alternative for Cloud Run).

Naming Rules

GCP resource names are derived from service-specific attributes that provide human-readable identification.

ConditionName
cloud.platform == "gcp_cloud_run" + faas.name set<faas.name>:<cloud.region> or <faas.name>
cloud.resource_id matches //pubsub.googleapis.com/...Resource name extracted from cloud.resource_id
cloud.resource_id matches //storage.googleapis.com/...Bucket name extracted from cloud.resource_id
cloud.resource_id matches //run.googleapis.com/...Service/job name extracted from cloud.resource_id

Typing Rules

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

ConditionTypeUI Label
cloud.platform == "gcp_cloud_run"gcp.cloud.runCloud Run
cloud.resource_id matches //run.googleapis.com/...gcp.cloud.runCloud Run
cloud.resource_id matches //storage.googleapis.com/...gcp.cloud.storageCloud Storage
cloud.resource_id matches //pubsub.googleapis.com/...gcp.pubsubPub/Sub

Examples

  • Cloud Run Service: For a service named api-service in region us-central1, the name will be api-service and 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 type gcp.pubsub
  • GCS Bucket: For cloud.resource_id = //storage.googleapis.com/my-data-bucket, the name will be my-data-bucket and type gcp.cloud.storage

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 for Pub/Sub topics and Cloud Storage buckets to enable resource correlation

Further Reading

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

Dash0 Guides & Knowledge

OpenTelemetry Resources