DAG

Related topics

• Cloud Composer works with DAG From the official documentation: “You'll also upload the DAG to your Managed Airflow environment.”
• Cloud Run functions works with DAG From the official documentation: “For example, you can [use Cloud Run functions to trigger Airflow DAGs](/composer/docs/composer-2/triggering-with-gcf) when a specified event occurs.”
• DAG works with Dataflow From the official documentation: “Now you will reference the files you created earlier to create a DAG that kicks off the Dataflow workflow.”
• DAG works with Pub/Sub From the official documentation: “You can then create a DAG that pulls Pub/Sub messages and then handles these messages.”
• 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.”
• 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 Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• 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 Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Storage 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 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.”
• 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 Run functions depends on Pub/Sub From the official documentation: “The Pub/Sub message triggers Cloud Run functions.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• 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 Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
• 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 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 Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Cloud Run functions From the official documentation: “This hands-on lab shows you how to view your Cloud Run functions with their execution times, execution counts, and memory usage in the Google Cloud console. These metrics are also available in Cloud Monitoring.”
• 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 Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• 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 VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
• Cloud Composer works with Cloud Logging From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
• Cloud Composer depends on Cloud Monitoring From the official documentation: “Managed Airflow uses global endpoints for Cloud Monitoring (`monitoring.googleapis.com`) because some Monitoring APIs don't fully support regional endpoints.”
• Cloud Composer works with Cloud Monitoring From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
• Cloud Composer is an alternative to Cloud Run From the official documentation: “If you already have a Managed Airflow environment, you can orchestrate your DPMS metadata exports and imports by running an Airflow DAG on that environment (as shown in Figure 2). This use of an Airflow DAG would be in place of the Cloud Run method mentioned earlier.”
• Cloud Composer works with Cloud Storage From the official documentation: “When you create an environment, Managed Airflow [creates a Cloud Storage bucket](/composer/docs/composer-1/cloud-storage) and associates this bucket with your environment.”
• Cloud Composer works with VPC Service Controls From the official documentation: “- **VPC SC**: To deploy Managed Airflow environments inside a security perimeter, see [Configuring VPC SC](/composer/docs/composer-1/configure-vpc-sc). When used with Managed Airflow, VPC Service Controls have several [known…”
• 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 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 Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
• 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 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 is an alternative to Dataflow From the official documentation: “- Perform file validation by using [Cloud Run functions](/functions/docs/concepts/overview) (for example, based on file upload events) or within [Dataflow](/dataflow/docs/overview) pipelines.”
• 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.”
• Dataflow works with VPC Service Controls From the official documentation: “To customize DNS resolution when using Dataflow with VPC Service Controls, use Cloud DNS [private zones](/dns/docs/overview#dns-private-zones) instead of using custom BIND servers.”
• Pub/Sub depends on Cloud Run functions From the official documentation: “After you have set up Cloud Run functions to process model output and generate events, you can set up event notification with Pub/Sub.”
• VPC Service Controls secures Cloud Composer From the official documentation: “If you want to protect your environment with VPC Service Controls, then make sure that both host and service projects are located in the same service perimeter For more information, see [Perimeters for environments with Shared VPC and…”
• VPC Service Controls secures Cloud Monitoring From the official documentation: “VPC Service Controls provides additional security for Cloud Monitoring to help mitigate the risk of data exfiltration.”
• VPC Service Controls secures Cloud Run From the official documentation: “To learn more about the security features that Cloud Run provides, use the following resources: - [Access control with Identity and Access Management (IAM)](/run/docs/securing/managing-access) - [Per-service identity](/run/docs/securing/service-identity) - [Google Cloud Armor…”
• VPC Service Controls secures Cloud Run functions From the official documentation: “[VPC Service Controls](/vpc-service-controls) creates a security perimeter that isolates your Cloud Run functions services and resources by setting up authorization, access controls, and [secure data exchange](/vpc-service-controls/docs/secure-data-exchange).”