SLO

Related topics

• SLO is part of service level agreement From the official documentation: “An SLA can contain many SLOs.”
• service level indicator is part of SLO From the official documentation: “An SLO specifies an SLI and a target value that measures success of the service in the compliance period.”
• SLO depends on service level indicator From the official documentation: “Define SLOs based on those SLIs.”
• alerting policy depends on SLO From the official documentation: “Set up alerting policies to notify you when performance does not meet the SLOs.”
• compliance period is part of SLO From the official documentation: “In addition to defining a target for an SLI, an SLO specifies a period of time in which the SLI is being measured.”
• error budget depends on SLO From the official documentation: “A useful SLO targets less than 100%, because the SLO determines your error budget.”
• Request-based SLOs is part of SLO From the official documentation: “The type of SLO. There are two types of SLOs: - Request-based SLOs - Windows-based SLOs”
• SLO depends on compliance period From the official documentation: “In addition to defining a target for an SLI, an SLO specifies a period of time in which the SLI is being measured.”
• SLO is part of Traffic Director From the official documentation: “This page describes how to create an alerting policy in Cloud Monitoring for a service level objective (SLO) that you create in Cloud Service Mesh.”
• Windows-based SLOs is part of SLO From the official documentation: “The type of SLO. There are two types of SLOs: - Request-based SLOs - Windows-based SLOs”
• alerting policy is part of Cloud Monitoring From the official documentation: “The Google Cloud console lets you view, list, edit, copy, and delete your alerting policies in Cloud Monitoring.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Cloud Trace From the official documentation: “To identify requests with high latency using Cloud Logging, apply the `traceSampled=true` filter to correlate logs in Cloud Logging with traces in Cloud Trace.”
• Cloud Logging works with Traffic Director From the official documentation: “Cloud Service Mesh supports MeshConfig telemetry API to enable and disable Cloud Logging and Cloud Monitoring for GKE workloads.”
• Cloud Monitoring works with Traffic Director From the official documentation: “Cloud Service Mesh supports MeshConfig telemetry API to enable and disable Cloud Logging and Cloud Monitoring for GKE workloads.”
• Cloud Trace works with Traffic Director From the official documentation: “Integrate with Cloud Trace, which is an optional feature in Cloud Service Mesh.”
• alerting policy works with Cloud Logging From the official documentation: “The alerting policy can monitor time-series data stored by Monitoring or logs stored by Cloud Logging.”
• alerting policy configures Cloud Monitoring From the official documentation: “Alerting policies are a way to configure Monitoring to notify you when something, like reaching 85% of your limit on a quota, happens.”
• alerting policy works with Cloud Trace From the official documentation: “Cloud Monitoring alerting policies let you track Cloud Trace monthly span volume, API quota limits, and span ingestion rates so that you receive notifications before exceeding quotas or incurring unexpected ingestion costs.”
• alerting policy depends on error budget From the official documentation: “You can create an alerting policy based on the rate of consumption of your [error budget](/service-mesh/legacy/in-cluster/observability/design-slo#error_budgets).”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging is an alternative to Cloud Trace From the official documentation: “You can use Cloud Trace or Cloud Logging to understand how long a particular request has taken.”
• Cloud Logging is an alternative to Google Cloud CLI From the official documentation: “This section shows you how to verify the encryption key that was used during cluster creation. You can perform this verification using Cloud Logging or by using the Google Cloud CLI.”
• Cloud Trace is part of Traffic Director From the official documentation: “Integrate with Cloud Trace, which is an optional feature in Cloud Service Mesh.”
• error budget works with service level objective From the official documentation: “The error budget for an SLO represents the total amount of time that a service can be noncompliant before it is in violation of its SLO.”
• Google Cloud CLI configures alerting policy From the official documentation: “You can also configure a new alerting policy by using the Google Cloud console, the [Cloud Monitoring API](/monitoring/api/v3), the [Google Cloud CLI](/sdk/gcloud/reference/monitoring/policies) and [Terraform](/monitoring/alerts/terraform).”
• Google Cloud CLI configures Cloud Logging From the official documentation: “You can update your cluster's [Cloud Logging](/kubernetes-engine/multi-cloud/docs/aws/how-to/cloud-logging) configuration settings with the Google Cloud CLI.”
• Google Cloud CLI configures Traffic Director From the official documentation: “To configure Google Cloud's managed load-balancing products and Cloud Service Mesh, you can use the Google Cloud CLI and Compute Engine APIs.”
• Request-based SLOs is an alternative to Windows-based SLOs From the official documentation: “The type of SLO. There are two types of SLOs: - Request-based SLOs - Windows-based SLOs”
• service level agreement works with service level objective From the official documentation: “An SLA is a contract with the users of your service that typically specifies the consequences of not meeting the SLOs.”
• service level indicator is part of service level objective From the official documentation: “Click **Set your service-level indicator (SLI)** to select the type of service level indicator (SLI) to track for this SLO.”
• service level objective is part of service level agreement From the official documentation: “The compliance period is particularly important when an SLO is included in a service level agreement (SLA) with your users.”
• service level objective depends on service level indicator From the official documentation: “Create service-level objectives (SLOs) based on custom or predefined service-level indicators (SLIs) for any of your services.”