Creating SLOs

Note: This guide only supports Cloud Service Mesh with Istio APIs and doesnot support Google Cloud APIs. For more information see,Cloud Service Mesh overview.

This page describes how to create a service level objective (SLO) in theGoogle Cloud console. For information on creating a SLO programmatically,seeWorking with the SLO API

For an overview and information on designing SLOs, see the following:

• Service level objectives overview
• Designing SLOs

To create an SLO:

1. Go to theHealth tab for a service:

   1. In the Google Cloud console, go toCloud Service Mesh.

      Go to Cloud Service Mesh

   2. Select the Google Cloud project from the drop-down list on the menu bar.

   3. Click the service that you want to create an SLO for.

   4. In the left navigation bar, clickHealth.

2. Click theCreate an SLO link.

3. ClickSet your service-level indicator (SLI) to select the type of service level indicator (SLI)to track for this SLO. Choose one of the following:

   • Availability: The ratio of the number of successfulresponses to the number of all responses. Requests that fail before theyreach the Envoy sidecar proxy for your service (because of networking orDNS failures, for example) aren't included in this ratio.
   • Latency: The ratio of the number of calls that are below thespecifiedLatency Threshold to the number of all calls.

4. For latency SLIs, enter theLatency Threshold in milliseconds.

5. In thePerformance Goal section, enter a percentage in theGoalfield to set the performance target for the SLI.Cloud Service Mesh uses this value to calculate theerror budgetyou have for this SLO.

6. In theCompliance Period section, select thePeriod Type and thePeriod Length. SeeCompliance periodsfor more information on these settings.

7. Alternatively, in theSet your SLI section, you may selectWindows-based SLI. A windowed SLI can help you catchperiods of time when the service won't meet the SLOCompliance target(such as when there are spikes in the number of requests that increaselatency for a short period of time). When you select this option, you mustspecify:

   • 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."
   • Duration: Set the length of each window, over which SLOperformance will be measured in increments during the compliance period.

   For example, suppose you have anAvailability SLO with aRolling7 day period, and anSLO Goal of99%. Then you addaGoodness criterion of95% and aDuration of5 minutes.To be compliant, the service needs95% of all5 minute windowsover the last7 days to be available at least99% of the time.

8. Optionally, clickName your SLO to change the default SLO displayname. Cloud Service Mesh supplies a default name that describes theSLO based on the settings.

9. ClickSubmit.

What's next

• Monitoring SLOs
• Creating an alerting policy on an SLO