diff options
| author | Paul Buetow <paul@buetow.org> | 2025-12-24 00:56:20 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-12-24 00:56:20 +0200 |
| commit | c2338a3772fe8bf2b49ce102a36ed6ea1e1a9fdd (patch) | |
| tree | a0bf59e187a7dc663a34d50a57b728194805b531 | |
| parent | 344a2ea0ebf0aec75eac7a89bb9662b70834fd76 (diff) | |
Update content for gemtext
| -rw-r--r-- | gemfeed/DRAFT-x-rag-observability-hackathon.gmi | 2 | ||||
| -rw-r--r-- | gemfeed/DRAFT-x-rag-observability-hackathon.gmi.tpl | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/gemfeed/DRAFT-x-rag-observability-hackathon.gmi b/gemfeed/DRAFT-x-rag-observability-hackathon.gmi index c68c4c1e..7b03217c 100644 --- a/gemfeed/DRAFT-x-rag-observability-hackathon.gmi +++ b/gemfeed/DRAFT-x-rag-observability-hackathon.gmi @@ -824,7 +824,7 @@ For X-RAG specifically, potential SLOs might include: * `Search latency`: 99th percentile search response time under 3 seconds * `Uptime`: 99.9% availability of the search API endpoint -* `Response quality`: Percentage of searches returning relevant results (though this is harder to measure automatically and might require user feedback or evaluation frameworks) +* `Response quality`: How good was the search? There are some metrics which could be used... SLAs (Service Level Agreements) are often confused with SLOs, but they're different. An SLA is a contractual commitment to customers—a legally binding promise with consequences (refunds, credits, penalties) if you fail to meet it. SLOs are internal engineering targets; SLAs are external business promises. Typically, SLAs are less strict than SLOs: if your internal target is 99.9% availability (SLO), your customer contract might promise 99.5% (SLA), giving you a buffer before you owe anyone money. diff --git a/gemfeed/DRAFT-x-rag-observability-hackathon.gmi.tpl b/gemfeed/DRAFT-x-rag-observability-hackathon.gmi.tpl index df53d1bd..93108f7a 100644 --- a/gemfeed/DRAFT-x-rag-observability-hackathon.gmi.tpl +++ b/gemfeed/DRAFT-x-rag-observability-hackathon.gmi.tpl @@ -786,7 +786,7 @@ For X-RAG specifically, potential SLOs might include: * `Search latency`: 99th percentile search response time under 3 seconds * `Uptime`: 99.9% availability of the search API endpoint -* `Response quality`: Percentage of searches returning relevant results (though this is harder to measure automatically and might require user feedback or evaluation frameworks) +* `Response quality`: How good was the search? There are some metrics which could be used... SLAs (Service Level Agreements) are often confused with SLOs, but they're different. An SLA is a contractual commitment to customers—a legally binding promise with consequences (refunds, credits, penalties) if you fail to meet it. SLOs are internal engineering targets; SLAs are external business promises. Typically, SLAs are less strict than SLOs: if your internal target is 99.9% availability (SLO), your customer contract might promise 99.5% (SLA), giving you a buffer before you owe anyone money. |