Find definitions of key terms used in Tanzu Service Mesh service level objectives (SLOs).
- API
-
Application programming interface.
- Autoscaling Policy (Autoscaler)
-
Defines the scale conditions for a service. When a set metric value, such as CPU Usage, latency, or memory, is violated, the scaling policy comes into action.
- GNS-scoped SLO
-
An SLO policy that is applied to services insides a global namespace.
- Org-scoped SLO
-
An SLO policy that is applied to services directly in cluster namespaces.
- p50 Latency
-
The 50th percentile latency. Fifty percent of all requests to the service take less time (measured in milliseconds) than the value (in milliseconds) stated for this metric.
- p90 Latency
-
The 90th percentile latency. Ninety percent of all requests to the service take less time (measured in milliseconds) than the value (in milliseconds) stated for this metric.
- p99 Latency
-
The 99th percentile latency. Ninety-nine percent of all requests to the service take less time (measured in milliseconds) than the value (in milliseconds) stated for this metric.
- Service Level Objective (SLO)
-
A target value or a range of values for a service level that is measured by a service level indicator (SLI). A natural structure for SLOs is SLI ≤ target, or lower bound ≤ SLI ≤ upper bound. For example, we might decide that we will return search results "quickly," adopting an SLO that our average search request latency must be less than 100 milliseconds.
- SLO
-
See Service Level Objective (SLO).
- SLI
-
Service level indicator. A measure that quantifies service-level attributes, such as resource use, requests, errors, and latencies, that form part of the SLO.
