Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to use Cloud Deploy and
Google Cloud Observability to set up
alerting policies so you are notified for specific events and conditions in
Cloud Deploy.
Alerts for Cloud Deploy are generated using
platform logs stored by Cloud Logging.
Google Cloud Observability supports alerts generated using time-series data from
Cloud Monitoring, but Cloud Deploy alerts are
based on logs only.
Cloud Deploy alert policies are per delivery pipeline.
What are alerts?
Alerts are notifications from Google Cloud Observability under certains conditions.
You specify those conditions in an alerting policy. The
Google Cloud Observability documentation describes alerting and
alerting policies in more detail. This document describes the specific
Cloud Deploy activities for which you can set up alerting policies.
Available alerts
You can set up alerting policies for the following circumstances, specific to
Cloud Deploy:
The render operation, for a given release,
has failed.
For every release, all manifests, service definitions, and any other configs
that must be rendered, are rendered for all targets before anything is
deployed. This alert notifies you if a release's render operation fails.
A rollout has failed.
This alert notifies you when a rollout within this delivery pipeline fails.
You can then take action, as described in the article
Manage rollouts.
When using a canary deployment strategy, each canary increment is a phase in
the rollout for that release and target. Advancing those stages can be done
manually or automatically. If there's a rollout waiting for a stage to be
advanced, this alert lets you know.
Open the Delivery pipeline details page for the pipeline for which you
want to create an alert policy.
Click the Recommended alerts button.
The Alert policy templates dialog is displayed, showing the alert-policy
templates that are available for Cloud Deploy.
Select each policy template you want to use for this delivery pipeline.
You can also click Show options to set options for the template, and to
see current log messages related to that policy template.
Under Configure notifications, select the notification channel or
channels the notifications will be sent to.
If you don't already have notification channels configured, you can click
Manage notification channels.
By default, a maximum of 1 alert per policy is sent every 5 minutes. You can
configure this in the Show options sections of each alert policy template.
For more information about setting up alerting policies and notification
channels, see the Alerting overview.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eCloud Deploy utilizes platform logs within Google Cloud Logging to generate alerts, enabling notifications for specific events and conditions, as opposed to relying on time-series data from Cloud Monitoring.\u003c/p\u003e\n"],["\u003cp\u003eAlert policies in Cloud Deploy are specific to each delivery pipeline, and can be configured to notify on events like a release's render operation failure, a failed rollout, a pending rollout approval, or when a canary deployment strategy needs phase advancement.\u003c/p\u003e\n"],["\u003cp\u003eSetting up alerting policies requires the proper permissions from Google Cloud Observability, and can be done directly through the Google Cloud console, as well as through the Cloud Monitoring API or the Google Cloud Observability Terraform provider.\u003c/p\u003e\n"],["\u003cp\u003eUsers can configure notification channels to receive alerts, and the frequency of alerts is set to a maximum of one alert per policy every five minutes by default, but can be modified within the alert policy template options.\u003c/p\u003e\n"],["\u003cp\u003eThe delivery pipeline in question has an option to subscribe to service notification via pub/sub topics.\u003c/p\u003e\n"]]],[],null,["# Create Cloud Deploy alerts\n\nThis page describes how to use Cloud Deploy and\n[Google Cloud Observability](https://cloud.google.com/products/operations) to set up\nalerting policies so you are notified for specific events and conditions in\nCloud Deploy.\n\nAlerts for Cloud Deploy are generated using\n[platform logs](/deploy/docs/platform-logs) stored by Cloud Logging.\nGoogle Cloud Observability supports alerts generated using time-series data from\nCloud Monitoring, but Cloud Deploy alerts are\n[based on logs only](/logging/docs/alerting/log-based-alerts).\n\nCloud Deploy alert policies are per delivery pipeline.\n| **Note:** In addition to the alerts described in this article, you can [subscribe to Cloud Deploy service notifications](/deploy/docs/subscribe-deploy-notifications) using Pub/Sub topics.\n\nWhat are alerts?\n----------------\n\nAlerts are notifications from Google Cloud Observability under certains conditions.\nYou specify those conditions in an alerting policy. The\n[Google Cloud Observability documentation](/monitoring/alerts) describes alerting and\nalerting policies in more detail. This document describes the specific\nCloud Deploy activities for which you can set up alerting policies.\n\nAvailable alerts\n----------------\n\nYou can set up alerting policies for the following circumstances, specific to\nCloud Deploy:\n\n- The [render](/deploy/docs/terminology#render) operation, for a given release,\n has failed.\n\n For every release, all manifests, service definitions, and any other configs\n that must be rendered, are rendered for all targets before anything is\n deployed. This alert notifies you if a release's render operation fails.\n- A rollout has failed.\n\n This alert notifies you when a rollout within this delivery pipeline fails.\n You can then take action, as described in the article\n [Manage rollouts](/deploy/docs/deployment-strategies/manage-rollout).\n- A rollout requires\n [approval](/deploy/docs/promote-release#manage_approvals_for_a_delivery_pipeline).\n\n One of your targets is configured to require approval, and the release is now\n being promoted to that target, but approval is pending.\n- A rollout with a [canary deployment strategy](/deploy/docs/deployment-strategies/canary)\n requires [phase advancement](/deploy/docs/deployment-strategies/manage-rollout#advance_rollout).\n\n When using a canary deployment strategy, each canary increment is a phase in\n the rollout for that release and target. Advancing those stages can be done\n manually or automatically. If there's a rollout waiting for a stage to be\n advanced, this alert lets you know.\n\nWhat permissions do you need?\n-----------------------------\n\nThe person using the Google Cloud console to set up alerting policies must\nhave the\n[permissions that Google Cloud Observability requires](/monitoring/alerts/using-alerting-ui#before_you_begin).\n\nConfigure Cloud Deploy alerts\n-----------------------------\n\nTo create an alert for a delivery pipeline:\n\n1. Open the **Delivery pipeline details** page for the pipeline for which you\n want to create an alert policy.\n\n2. Click the **Recommended alerts** button.\n\n The **Alert policy templates** dialog is displayed, showing the alert-policy\n templates that are available for Cloud Deploy.\n3. Select each policy template you want to use for this delivery pipeline.\n\n You can also click **Show options** to set options for the template, and to\n see current log messages related to that policy template.\n4. Under **Configure notifications**, select the notification channel or\n channels the notifications will be sent to.\n\n If you don't already have notification channels configured, you can click\n **Manage notification channels**.\n\nBy default, a maximum of 1 alert per policy is sent every 5 minutes. You can\nconfigure this in the **Show options** sections of each alert policy template.\n\nFor more information about setting up alerting policies and notification\nchannels, see the [Alerting overview](/monitoring/alerts).\n\n### Other ways to set up alerts\n\nBesides creating alert policies using the Google Cloud console, you can\n[use the Cloud Monitoring API](/monitoring/alerts/policies-in-api) or\n[the Google Cloud Observability Terraform provider](/monitoring/alerts/terraform).\n\nWhat's next\n-----------\n\n- [Learn more about Google Cloud Observability](/monitoring/alerts) alerts.\n\n- [Read about Cloud Deploy platform logs](/deploy/docs/platform-logs)."]]