Topic

Related topics

• Topic is part of Pub/Sub From the official documentation: “Lists all Pub/Sub topics.”
• Cloud Monitoring works with Topic From the official documentation: “Cloud Monitoring provides a number of metrics to monitor topics.”
• Compute Engine works with Topic From the official documentation: “For example, instances of a service may be deployed on Compute Engine in multiple zones but subscribe to a common topic.”
• Dataflow job works with Topic From the official documentation: “To create and launch the Dataflow job that generates synthetic data for your Kafka topic:”
• Google-owned and Google-managed encryption key secures Topic From the official documentation: “Specifies that the topic is encrypted using Google-owned and Google-managed encryption keys.”
• schema works with Topic From the official documentation: “You can [associate the schema with a topic](/pubsub/docs/associate-schema-topic).”
• schema configures Topic From the official documentation: “These samples show how to process messages when subscribing to [topics configured with schema](/pubsub/docs/associate-schema-topic).”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• CMEK secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• CMEK secures BigQuery From the official documentation: “Enable CMEK for BigQuery Tables”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• 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 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).”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Dataflow From the official documentation: “Dataflow is fully integrated with Cloud Monitoring.”
• Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported logs.”
• 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 Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• CMEK works with Dataflow From the official documentation: “The region for your CMEK and the [region](/dataflow/docs/resources/locations) for your Dataflow job must be the same.”
• CMEK secures GKE From the official documentation: “Enable CMEK on GKE Node Pool Boot Disks”
• Dataflow depends on Compute Engine From the official documentation: “When Dataflow runs a pipeline, the processing is distributed across multiple Compute Engine virtual machines (VMs), also known as workers.”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• 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 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 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 Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging works with Dataflow From the official documentation: “You can control the volume of Dataflow logs ingested by Cloud Logging by following the [Filter logs documentation](/dataflow/docs/guides/filter-logs).”
• Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
• 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.”
• CMEK configures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• CMEK secures Cloud Run From the official documentation: “You use the CMEK keys to help protect your data in Artifact Registry and in Cloud Run.”
• CMEK secures Compute Engine From the official documentation: “Enable CMEK on Compute Engine Persistent Disks”
• CMEK is an alternative to Google-owned and Google-managed encryption key From the official documentation: “You can choose whether to use a Google-owned and Google-managed encryption key (GMEK) or Customer-managed encryption key (CMEK) approach to encrypt and decrypt your API data at rest.”
• CMEK works with Pub/Sub From the official documentation: “By using Pub/Sub with CMEK, you are able to meet locality rules about encryption while still maintaining high availability.”
• Pub/Sub works with schema From the official documentation: “A schema is a contract between the publisher and subscriber that Pub/Sub enforces.”