diff options
| author | Marcin Owsiany <porridge@google.com> | 2017-10-16 16:23:58 +0200 |
|---|---|---|
| committer | Marcin Owsiany <porridge@google.com> | 2017-10-16 16:23:58 +0200 |
| commit | 9c6f8d429c4c64d3631ea7d2a5e70b29e6c8f123 (patch) | |
| tree | b4af10a7a61b58c69539e5ef3d0ca7b4b11ad3ec | |
| parent | 07e214b0d24b9f0f09819778ccbf2559c33d3ff5 (diff) | |
Split paragraphs.
| -rw-r--r-- | sig-scalability/extending_slo.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sig-scalability/extending_slo.md b/sig-scalability/extending_slo.md index 7cbc0f25..c0d4e603 100644 --- a/sig-scalability/extending_slo.md +++ b/sig-scalability/extending_slo.md @@ -9,6 +9,7 @@ which are enough to guarantee that cluster doesn't feel completely dead, but not We're going to define more SLOs based on most important indicators, and standardize the format in which we speak about our objectives. Our SLOs need to have two properties: - They need to be testable, i.e. we need to have a benchmark to measure if it's met, - They need to be expressed in a way that's possible to understand by a user not intimately familiar with the system internals, i.e. formulation can't depend on some arcane knowledge. + On the other hand we do not require that: - SLOs are possible to monitor in a running cluster, i.e. not all SLOs need to be easily translatable to SLAs. Being able to benchmark is enough for us. |