labels

Related topics

• labels is part of BigQuery From the official documentation: “BigQuery supports adding labels to resources.”
• labels configures reservation From the official documentation: “When you add a label to a reservation, it is included in your billing data.”
• BigQuery works with labels From the official documentation: “Labels are exported to BigQuery with the corresponding Google Cloud resources and their usage.”
• Cloud Logging works with labels From the official documentation: “[Labels](/resource-manager/docs/creating-managing-labels) can track your resource spend in Cloud Billing, and provide extra insights in Cloud Logging.”
• labels is part of Cloud Trace From the official documentation: “Labels and attributes in Cloud Trace let you attach key-value metadata—such as HTTP status codes, region names, or custom application properties—to your spans so that you can filter, group, and troubleshoot requests.”
• labels configures Compute Engine From the official documentation: “Labels that are applied to the workstation and propagated to the underlying Compute Engine resources.”
• labels configures Google Kubernetes Engine (GKE) From the official documentation: “To register agents deployed on [Google Kubernetes Engine (GKE)](/kubernetes-engine/docs/tutorials/agentic-adk-vertex), add the required Kubernetes [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) and…”
• labels configures revision From the official documentation: “Labels are key/value pairs that are applied to the service and revisions.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• BigQuery works with Cloud Run functions From the official documentation: “Learn how to write an HTTP Cloud Run function that submits a query to BigQuery.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
• Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Run functions works with Cloud Storage From the official documentation: “(GCF translates GCS notifications to HTTP requests internally)”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• 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.”
• Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Audit Logs works with Cloud Logging From the official documentation: “- For real-time analysis, alerting, and visualization, stream the audit logs to [Logging](/logging/docs/overview).”
• Cloud Logging works with Cloud Run functions From the official documentation: “Cloud Run functions is configured to use Cloud Logging automatically.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Cloud Trace From the official documentation: “To identify requests with high latency using Cloud Logging, apply the `traceSampled=true` filter to correlate logs in Cloud Logging with traces in Cloud Trace.”
• Cloud Logging works with Google Kubernetes Engine From the official documentation: “By default, GKE clusters send system log data and system metric data to Logging and Monitoring.”
• 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.”
• revision is part of Cloud Run From the official documentation: “Each deployment of the Cloud Run service creates a new immutable revision.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• 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 depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• 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 Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
• Cloud Audit Logs secures BigQuery From the official documentation: “For BigQuery, [Cloud Audit Logs](/logging/docs/audit) is used for both data access logs and audit logs, which are enabled by default.”
• Cloud Audit Logs works with Cloud Run From the official documentation: “The sample code shows you how to read Cloud Storage events using Cloud Audit Logs in a service deployed to Cloud Run.”
• Cloud Audit Logs works with Cloud Run functions From the official documentation: “Cloud Audit Logs for Cloud Run functions let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Audit Logs works with Cloud Trace From the official documentation: “Cloud Audit Logs for Cloud Trace let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Audit Logs works with Compute Engine From the official documentation: “Compute Engine creates system events in the [Cloud Audit Logs](/logging/docs/audit) for an instance for maintenance events.”
• Cloud Audit Logs works with Google Kubernetes Engine From the official documentation: “For clusters on patch versions 1.21.9 and 1.22.3 or later with Cloud Logging [enabled](/stackdriver/docs/solutions/gke/installing#installing), GKE provides a [Cloud Audit Logs log](/kubernetes-engine/docs/how-to/audit-logging#viewing_your_projects_admin_activity_log) to…”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging is an alternative to Cloud Trace From the official documentation: “You can use Cloud Trace or Cloud Logging to understand how long a particular request has taken.”
• Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Cloud Run is an alternative to Cloud Run functions From the official documentation: “The blueprint supports the following use cases: - Deploying a serverless architecture using Cloud Run functions (this document) - [Deploying a serverless architecture using Cloud Run](/architecture/blueprints/serverless-blueprint)”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• 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 is an alternative to Google Kubernetes Engine (GKE) From the official documentation: “The architecture shows [Cloud Run](/run/docs/configuring/services/gpu-best-practices) and [GKE](/kubernetes-engine/docs/concepts/machine-learning/inference) as alternative runtimes for the AI model that you choose to use.”
• Cloud Run functions is part of Cloud Run From the official documentation: “| Cloud Run functions | Standalone functions on Cloud Run. |”
• Cloud Run functions depends on Cloud Storage From the official documentation: “Cloud Run functions uses the config in Cloud Storage to determine what actions to take for each stateful MIG.”
• Cloud Run functions works with Cloud Trace From the official documentation: “Trace data is collected when your Cloud Run function executes. To view trace data, use the Google Cloud console or the Cloud Trace API.”
• Cloud Run functions is an alternative to Compute Engine From the official documentation: “Cloud Run functions and App Engine don't offer a two-way configurable firewall, so you must either create compensating controls or deploy the tokenization service on Compute Engine or Google Kubernetes Engine.”
• Cloud Run functions is an alternative to Google Kubernetes Engine From the official documentation: “Cloud Run functions and App Engine don't offer a two-way configurable firewall, so you must either create compensating controls or deploy the tokenization service on Compute Engine or Google Kubernetes Engine.”
• Cloud Run functions works with VPC Service Controls From the official documentation: “For example, you can use this scenario to enable a Cloud Function to access data protected by VPC Service Controls.”
• Cloud Storage works with Google Kubernetes Engine From the official documentation: “Often, media-related data residing in Cloud Storage is processed by applications running in Compute Engine or Google Kubernetes Engine, and the output of this process is written back to Cloud Storage.”
• Cloud Trace depends on Cloud Storage From the official documentation: “To determine the prompts and responses to display for a span, Cloud Trace issues queries to read log data and to read data stored in a Cloud Storage bucket.”
• Cloud Trace works with VPC Service Controls From the official documentation: “Cloud Trace is a VPC Service Controls-supported service.”