Best Practices

Docs

Docs
(current)
VMware Communities

Twitter Facebook LinkedIn 微博

Consider the following best practices when you configure service level objectives (SLOs) in Tanzu Service Mesh.

What to read next

Best Practice 1: Set High-Level Objectives for Production Environments
A common measure of the health of a service is latency percentile values. Of the three latency percentiles available to use with Tanzu Service Mesh SLOs, the p99 latency is the most appropriate service level indicator (SLI) for production environments because this metric most fully covers the experience of the users of a service.
Best Practice 2: Use the P90 Latency for SLI Development Environments
In Best Practice 1, we suggested using the p99 latency to define an SLI. Development environments do not need to have service qualities as high as that of production environments and so can use the p90 latencies for an SLI measurement.
Best Practice 3: Use a p50 Latency SLI Where High Latencies Doesn’t Mean Lower Service Quality
For environments where the response times are the least critical, the p50 latency SLI might be the most appropriate to use.
Best Practice 4: Don't Use Lower Values for p99 Latencies than p50 or p90 Latencies
This topic illustrates an example of how not to use service level indicators (SLIs).

Share on Social Media?

:

|

x

" "?