[[["容易理解","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-09-04 (世界標準時間)。"],[],[],null,["# Creating an alerting policy\n\nThis document describes how to create an alerting policy to monitor the\nerror budget of an SLO associated with a service.\nTo monitor the error budget for your SLO, you can create one or more alerting\npolicies for the SLO. The purpose of the alerting policy is to\nwarn you when the service is consuming the error budget too quickly.\n\nYou can have up to 2,000 alerting policies in a\nmetrics scope.\n\nFor general information on SLO-based alerting policies, see\n[Alerting on your burn rate](/stackdriver/docs/solutions/slo-monitoring/alerting-on-budget-burn-rate).\n\nTo create an alerting policy for an SLO associated with a service, start\nby doing the following:\n\n- On the **Services Overview** page, click the name of the service for\n which you want to create an alerting policy.\n\n- In the **Current status** pane, locate the entry for the SLO you want\n to monitor. Click *notifications* **Create SLO alert**.\n\nClicking **Create SLO alert** takes to you the condition editor for a SLO-based\nalerting policy.\n\nCreating the condition\n----------------------\n\nWhen you click **Create SLO alert** , an in-context pane, **Set SLO\nalert conditions**, opens for creating a SLO-based condition for an alerting\npolicy. The following screenshot shows an example:\n\nBecause you clicked **Create SLO alert** from a specific SLO in a\nspecific service, the configuration pane is pre-populated with best-practice\nvalues for your SLO. The value of the **Target** field is the SLO for which\nyou are creating the alerting policy.\n\nThe condition must have a name. The **Display name** field is pre-populated\nwith a suggestion based on the configuration of the SLO. You can change this\nvalue by clicking on the text box.\n\nThe **Lookback duration** field specifies how far back in time to retrieve the\nburn-rate data. This value is also used as the evaluation period for\ncalculating the error-budget consumption. This field has a default value, but\nyou can change it. See\n[Alerting policies and lookback periods](/stackdriver/docs/solutions/slo-monitoring/alerting-on-budget-burn-rate#alert-lookbacks) for more information.\n\nThe **Burn rate threshold** field specifies the rate of error-budget\nconsumption for which you want to be notified. This field has a default value,\nbut you can change it. Set this value so that, as long as the rate of\nerror-budget consumption stays below this threshold, you will not exhaust\nyour error budget during the SLO compliance period.\n\nThe condition describes the behavior of the alerting policy, and SLOs\noften have two, a \"fast burn\" and a \"slow burn\"\npolicy. For more information, see [Types of error-budget alerts](/stackdriver/docs/solutions/slo-monitoring/alerting-on-budget-burn-rate#burn-rates).\n\nWhen you are satisfied with the condition, click **Next** to proceed to\nthe next pane, **Who should be notified?**\n\nSetting up notifications\n------------------------\n\nIn this step, you specify notification channels for the alerting policy.\nNotification channels tell Cloud Monitoring how to notify you\nthat the alerting policy has fired. This step is optional:\n\nAfter selecting a notification channel or deciding to skip the step,\nclick **Next** to proceed to the next pane, **What are the steps to fix\nthe issue?**\n\nSetting up documentation\n------------------------\n\nIn this step, you can provide information that is included in notifications.\nThis documentation can describe the alerting policy and provide troubleshooting\ninformation to the recipient of the notification.\n\nDocumentation is optional but strongly recommended. This information can\nhelp guide the troubleshooting process once an alert has fired.\n\nWhen you are satisfied with the documentation, click **Save** to finish\nthe creation of the alerting policy.\n\nNotification channels and documentation are standard parts of an alerting\npolicy in Cloud Monitoring; for more information about them, see the\ngeneral documentation for [Creating an alerting policy](/monitoring/alerts/using-alerting-ui#create-policy)."]]