Build and operate the data processing systems behind analytics and ML on Google Cloud, including BigQuery, Dataflow, and Pub/Sub, and track your readiness for the Professional Data Engineer exam.
Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Concept
alerting policy
Topic in 1 exam domain
- alerting policy · Concept
- alerting policy · Feature
Also called: alert policy, altering policy, chart for an alerting policy, metric-based alerting policies, patch alert, patch alerts, SLO-based alerting policies
A configuration that describes a set of conditions to monitor and specifies when to send notifications if those conditions are met.
Where this appears on the exam
1 subdomain in 1 of 5 domains
Related topics
FoundationsThis topicWorks alongsideBuilds on theseAppliedCloud LoggingServicetagsFeatureSLOConceptTerraformConceptBigQueryServiceKnowledge CatalogService
alerting policyConcept
Compute EngineServicePub/SubServiceDatastreamServiceCloud MonitoringServiceGKEServiceCloud SQLServiceMonitoring Query LanguageFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- alerting policy is part of Cloud Monitoring From the official documentation: “The Google Cloud console lets you view, list, edit, copy, and delete your alerting policies in Cloud Monitoring.”
- tags secures alerting policy From the official documentation: “To learn how to control access to your alerting policies with Tags, see [Use Tags to control access to resources](/monitoring/docs/access-control-with-tags).”
- alerting policy works with Cloud Logging From the official documentation: “The alerting policy can monitor time-series data stored by Monitoring or logs stored by Cloud Logging.”
- alerting policy configures Cloud Monitoring From the official documentation: “Alerting policies are a way to configure Monitoring to notify you when something, like reaching 85% of your limit on a quota, happens.”
- alerting policy works with Datastream From the official documentation: “You can use Datastream to monitor the data and events that a stream processes and configure alerting policies to track replication health.”
- alerting policy depends on SLO From the official documentation: “Set up alerting policies to notify you when performance does not meet the SLOs.”
- Monitoring Query Language configures alerting policy From the official documentation: “You can implement the same latency alert policy using a Monitoring Query Language (MQL) query.”
- Terraform configures alerting policy From the official documentation: “You can also configure a new alerting policy by using the Google Cloud console, the [Cloud Monitoring API](/monitoring/api/v3), the [Google Cloud CLI](/sdk/gcloud/reference/monitoring/policies) and [Terraform](/monitoring/alerts/terraform).”
- BigQuery works with Datastream From the official documentation: “Datastream supports three types of partitioning for BigQuery tables:”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- 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”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- 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.”
- Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
- Terraform configures Compute Engine From the official documentation: “Provisioning Compute Engine virtual machines (VMs) with Terraform lets you evaluate Google Distributed Cloud in high availability (HA) mode without physical hardware.”
- 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 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 Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud SQL works with Datastream From the official documentation: “The change data capture pipeline uses VPC peering to establish a connection between Datastream and private IP Cloud SQL.”
- Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
- 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 Logging works with Knowledge Catalog From the official documentation: “Knowledge Catalog sends logs for service operations and job executions to Cloud Logging.”
- Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
- 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.”
- Datastream works with Knowledge Catalog From the official documentation: “Datastream also integrates with Knowledge Catalog for centralized metadata and lineage management across Google Cloud.”
- 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.”
- Knowledge Catalog works with Pub/Sub From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
- 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 Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
- Cloud Monitoring works with Knowledge Catalog From the official documentation: “Cloud Logging and Cloud Monitoring let you track billable token consumption for Knowledge Catalog (formerly Dataplex Universal Catalog) data insights scans.”
- Cloud Monitoring works with tags From the official documentation: “[Tags](/resource-manager/docs/tags/tags-overview) lets you restrict who can edit or delete specific Cloud Monitoring dashboards and alerting policies.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Cloud SQL works with tags From the official documentation: “This page describes Google Cloud tags and how to use them with Cloud SQL.”
- Cloud SQL works with Terraform From the official documentation: “For more information about using Cloud SQL with Terraform, see [Cloud SQL Database Instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance) in the Terraform documentation.”
- GKE works with Terraform From the official documentation: “Terraform is a popular open source IaC tool created by HashiCorp that supports a wide range of Cloud services, including GKE.”
- Monitoring Query Language is part of Cloud Monitoring From the official documentation: “Monitoring Query Language reference Review the reference guide for the Monitoring Query Language (MQL).”
- Pub/Sub works with tags From the official documentation: “This page describes Google Cloud tags and how to use them with Pub/Sub. Tags can be applied to Pub/Sub topics, subscriptions, and snapshots.”
- Terraform configures Knowledge Catalog From the official documentation: “Automate your infrastructure by [provisioning Knowledge Catalog resources with Terraform](/knowledge-catalog/docs/terraform) to manage your data quality specifications and metadata enrichment at scale.”
How learners score on this topic
Last updated