OpenTelemetry

Related topics

• Cloud Trace works with OpenTelemetry From the official documentation: “Instrument your application to use OpenTelemetry. For more information, see [Instrument for Trace](/trace/docs/setup).”
• Cloud Monitoring works with OpenTelemetry From the official documentation: “For more details on collecting and exporting OpenTelemetry data to Cloud Monitoring or Cloud Trace, see [Choose an instrumentation approach](/stackdriver/docs/instrumentation/choose-approach).”
• Google Cloud Managed Service for Prometheus is an alternative to OpenTelemetry From the official documentation: “If you want your application-generated metric and trace data to include application labels, then instrument your application with OpenTelemetry or use Google Cloud Managed Service for Prometheus.”
• Config Sync depends on OpenTelemetry From the official documentation: “Config Sync uses [OpenTelemetry](https://opentelemetry.io/) to record and export its metrics, which you can view with [Metrics Explorer](/monitoring/charts/metrics-explorer) or by [using the Cloud Monitoring API](/monitoring/custom-metrics/reading-metrics).”
• OpenTelemetry works with OpenTelemetry Collector From the official documentation: “**Backend Agnostic**: Emits standard OpenTelemetry spans. You can export traces directly to [Cloud Trace](https://cloud.google.com/trace), an on-premises OpenTelemetry Collector, or third-party observability platforms.”
• OpenTelemetry works with OpenTelemetry SDK From the official documentation: “The Cloud Storage client libraries supports trace data collection using the [OpenTelemetry SDK](https://opentelemetry.io/docs/languages/) to set up the following components required to collect and propagate trace data:”
• OpenTelemetry works with Spanner From the official documentation: “Spanner client libraries also provide statistics and traces using the OpenTelemetry observability framework.”
• OpenTelemetry works with User-defined metrics From the official documentation: “To instrument your code and collect user-defined metrics, we recommend using [OpenTelemetry](https://opentelemetry.io), though you can also use Prometheus or the Cloud Monitoring API directly.”
• Policy Controller depends on OpenTelemetry From the official documentation: “To create and record these metrics, Policy Controller uses [OpenTelemetry](https://opentelemetry.io/).”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Service Mesh works with Cloud Trace From the official documentation: “Integrate with Cloud Trace, which is an optional feature in Cloud Service Mesh.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Service Mesh works with Prometheus From the official documentation: “By default environments that install Cloud Service Mesh with Istio CA report metrics to Prometheus.”
• GKE works with Google Cloud Managed Service for Prometheus From the official documentation: “Google Cloud Managed Service for Prometheus is enabled for<br>GKE clusters by default.”
• BigQuery works with Spanner From the official documentation: “Federated analytics seamlessly combine data from Spanner and other sources in BigQuery.”
• Cloud Run works with Cloud Service Mesh From the official documentation: “This section shows you how to troubleshoot common errors with Cloud Service Mesh and Cloud Run.”
• Cloud Monitoring works with Config Sync From the official documentation: “Config Sync supports exporting metrics to Cloud Monitoring only from GKE clusters.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Google Kubernetes Engine From the official documentation: “Connecting Cloud Run services to Cloud Service Mesh lets you securely route traffic to workloads on GKE.”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Google Kubernetes Engine From the official documentation: “When Google Kubernetes Engine (GKE) [system metrics](/kubernetes-engine/docs/how-to/configure-metrics#system-metrics) are enabled, Cloud Monitoring collects the following metrics.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with OpenTelemetry Collector From the official documentation: “Set up the [OpenTelemetry Collector as a sidecar agent in Cloud Run](/run/docs/tutorials/custom-metrics-sidecar).”
• Cloud Service Mesh works with Google Kubernetes Engine From the official documentation: “A GKE Cluster with Cloud Service Mesh enabled”
• Cloud Trace is part of Cloud Service Mesh From the official documentation: “Integrate with Cloud Trace, which is an optional feature in Cloud Service Mesh.”
• Cloud Trace is an alternative to OpenTelemetry Collector From the official documentation: “To send traces to an external managed tracing backend or a self-hosted OpenTelemetry Collector instead of Cloud Trace:”
• Config Sync works with GKE From the official documentation: “This quickstart shows you how to use Config Sync to implement a GitOps approach for managing your Google Kubernetes Engine clusters.”
• Config Sync works with Policy Controller From the official documentation: “If you're using Policy Controller with Config Sync, you should be aware of the following interactions with resources stored in your source of truth, like a Git repository, that are synced by Config Sync:”
• Google Cloud Managed Service for Prometheus works with Google Kubernetes Engine From the official documentation: “This document describes how to configure your Google Kubernetes Engine deployment so that you can use Google Cloud Managed Service for Prometheus to collect metrics from Istio.”
• Google Kubernetes Engine depends on BigQuery From the official documentation: “This happens because Google Kubernetes Engine depends on BigQuery and Managed Service for Apache Airflow inherits this dependency from the Kubernetes Engine API.”
• Policy Controller works with Prometheus From the official documentation: “By default, Policy Controller attempts to export metrics to both Prometheus and Cloud Monitoring.”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• BigQuery works with Cloud Trace From the official documentation: “To create an alerting policy that triggers if there are errors exporting [Cloud Trace](/trace/docs) data to BigQuery, use the following settings.”
• BigQuery works with GKE From the official documentation: “Subsequently, by integrating BigQuery with GKE, you can use BigQuery to efficiently handle massive datasets (like Google Analytics) and the model's natural language understanding capabilities to generate meaningful insights.”
• Cloud Monitoring works with Google Cloud Managed Service for Prometheus From the official documentation: “Managed Service for Prometheus shares the data-storage backend, Monarch, with Cloud Monitoring.”
• Cloud Monitoring works with Policy Controller From the official documentation: “By default, Policy Controller attempts to export metrics to both Prometheus and Cloud Monitoring.”
• Cloud Monitoring works with Prometheus From the official documentation: “When you configure Prometheus with [Stackdriver Prometheus sidecar (deprecated)](https://github.com/Stackdriver/stackdriver-prometheus-sidecar), metrics exported by Prometheus are converted to Cloud Monitoring metric types with simple [metric…”
• Cloud Monitoring is an alternative to Prometheus From the official documentation: “Configure your own alerting policies in Cloud Monitoring or in Prometheus for issues affecting your workloads or local environment.”
• Cloud Run works with Google Cloud Managed Service for Prometheus From the official documentation: “You deployed a Cloud Run service that reports custom OTLP metrics to Google Cloud Managed Service For Prometheus.”
• Cloud Run is an alternative to Google Kubernetes Engine From the official documentation: “**Agent and tool runtimes**: hosting and executing agents or MCP servers on runtimes such as Agent Runtime on Gemini Enterprise Agent Platform, Cloud Run, or Google Kubernetes Engine (GKE) incurs standard compute and runtime charges for those services.”
• Cloud Run works with Spanner From the official documentation: “Use Spanner [client libraries](/spanner/docs/reference/libraries) from Cloud Run.”
• Cloud Service Mesh works with Google Cloud Managed Service for Prometheus From the official documentation: “| Google Cloud Managed Service for Prometheus, not including the Cloud Service Mesh dashboard | \* | \* |”
• Cloud Service Mesh depends on Google Kubernetes Engine From the official documentation: “Cloud Service Mesh service security is supported only with GKE.”
• Config Sync is part of GKE From the official documentation: “Config Sync and fleet team management features are available as part of GKE.”
• Config Sync works with Google Cloud Managed Service for Prometheus From the official documentation: “Config Sync metrics use [Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus) to load metrics into Cloud Monitoring.”
• Config Sync is part of Google Kubernetes Engine From the official documentation: “Config Sync is a [GitOps](https://opengitops.dev/) service included with Google Kubernetes Engine (GKE) that automatically syncs configurations and policies across your Kubernetes clusters from a central source of truth, such as a Git repository.”
• GKE works with Spanner From the official documentation: “Connect Spanner with a Google Kubernetes Engine (GKE) cluster”
• Google Cloud Managed Service for Prometheus is part of Cloud Monitoring From the official documentation: “Google Cloud Managed Service for Prometheus is part of Cloud Monitoring and is available as an option for system components.”
• Google Cloud Managed Service for Prometheus is part of GKE From the official documentation: “GKE clusters that use Autopilot include a Google Cloud Managed Service for Prometheus instance.”
• Google Cloud Managed Service for Prometheus works with Prometheus From the official documentation: “[Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus) describes how to collect Prometheus metrics from applications running on Google Kubernetes Engine and Kubernetes.”
• Policy Controller configures Cloud Service Mesh From the official documentation: “To prevent misconfiguration and automatically validate Cloud Service Mesh policies, mesh administrators can use [Policy Controller](https://cloud.google.com/anthos-config-management/docs/concepts/policy-controller) to [enforce…”
• Policy Controller secures Cloud Service Mesh From the official documentation: “To prevent misconfiguration and automatically validate Cloud Service Mesh policies, mesh administrators can use [Policy Controller](https://cloud.google.com/anthos-config-management/docs/concepts/policy-controller) to [enforce…”
• Policy Controller is part of GKE From the official documentation: “Policy Controller is available as part of GKE, but you can use Open Policy Agent - Gatekeeper instead of Policy Controller for your implementation.”
• Policy Controller depends on GKE From the official documentation: “Policy Controller is available if you use Google Kubernetes Engine.”
• Policy Controller configures GKE From the official documentation: “Policy Controller | Lets you define and enforce policies that govern your<br>GKE clusters.”