[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-11。"],[],[],null,["# Creating SLOs\n=============\n\n| **Note:** This guide only supports Cloud Service Mesh with Istio APIs and does not support Google Cloud APIs. For more information see, [Cloud Service Mesh overview](/service-mesh/docs/overview).\n\nThis page describes how to create a service level objective (SLO) in the\nGoogle Cloud console. For information on creating a SLO programmatically,\nsee\n[Working with the SLO API](/stackdriver/docs/solutions/slo-monitoring/api/api-structures)\n\nFor an overview and information on designing SLOs, see the following:\n\n- [Service level objectives overview](/service-mesh/docs/observability/slo-overview)\n- [Designing SLOs](/service-mesh/docs/observability/design-slo)\n\nTo create an SLO:\n\n1. Go to the **Health** tab for a service:\n\n 1. In the Google Cloud console, go to **Cloud Service Mesh**.\n\n [Go to Cloud Service Mesh](https://console.cloud.google.com/kubernetes/services)\n 2. Select the Google Cloud project from the drop-down list on the menu bar.\n\n 3. Click the service that you want to create an SLO for.\n\n 4. In the left navigation bar, click **Health**.\n\n2. Click the **Create an SLO** link.\n\n3. Click **Set your service-level indicator (SLI)** to select the type of service level indicator (SLI)\n to track for this SLO. Choose one of the following:\n\n - **Availability**: The ratio of the number of successful responses to the number of all responses. Requests that fail before they reach the Envoy sidecar proxy for your service (because of networking or DNS failures, for example) aren't included in this ratio.\n - **Latency** : The ratio of the number of calls that are below the specified **Latency Threshold** to the number of all calls.\n4. For latency SLIs, enter the **Latency Threshold** in milliseconds.\n\n5. In the **Performance Goal** section, enter a percentage in the **Goal**\n field to set the performance target for the SLI.\n Cloud Service Mesh uses this value to calculate the\n [error budget](/service-mesh/docs/observability/design-slo#error_budgets)\n you have for this SLO.\n\n6. In the **Compliance Period** section, select the **Period Type** and the\n **Period Length** . See\n [Compliance periods](/service-mesh/docs/observability/design-slo#compliance_periods)\n for more information on these settings.\n\n7. Alternatively, in the **Set your SLI** section, you may select **Windows-based** SLI. A windowed SLI can help you catch\n periods of time when the service won't meet the SLO **Compliance target**\n (such as when there are spikes in the number of requests that increase\n latency for a short period of time). When you select this option, you must\n specify:\n\n - **Goodness criterion**: Set a threshold for the percentage of \"good performance\" that must be met in order for a given window to count as \"good.\"\n - **Duration**: Set the length of each window, over which SLO performance will be measured in increments during the compliance period.\n\n For example, suppose you have an **Availability** SLO with a\n **Rolling** **7** day period, and an **SLO Goal** of **99** %. Then you add\n a **Goodness criterion** of **95** % and a **Duration** of **5** minutes.\n To be compliant, the service needs **95** % of all **5** minute windows\n over the last **7** days to be available at least **99**% of the time.\n8. Optionally, click **Name your SLO** to change the default SLO display\n name. Cloud Service Mesh supplies a default name that describes the\n SLO based on the settings.\n\n9. Click **Submit**.\n\nWhat's next\n-----------\n\n- [Monitoring SLOs](/service-mesh/docs/observability/monitor-slo)\n- [Creating an alerting policy on an SLO](/service-mesh/docs/observability/alert-policy-slo)"]]