[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-11 (世界標準時間)。"],[[["Cloud 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."],["Alert 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."],["Setting 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."],["Users 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."],["The delivery pipeline in question has an option to subscribe to service notification via pub/sub topics."]]],[]]