From 5caa9f584278b72d28a737e04ca31aabd18d652b Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Mon, 1 Jul 2024 15:29:21 -0700 Subject: [PATCH] [8.14](backport #3953) Clarify descriptions of APM indicators for SLOs (#4018) * Clarify descriptions of APM indicators for SLOs (#3953) --------- Co-authored-by: Gil Raphaelli (cherry picked from commit 4770b0c9c69e294fd599a9bd5f3c21a5df0c9f5e) --- docs/en/observability/slo-create.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/en/observability/slo-create.asciidoc b/docs/en/observability/slo-create.asciidoc index 911ba63cbb..00052f5ba3 100644 --- a/docs/en/observability/slo-create.asciidoc +++ b/docs/en/observability/slo-create.asciidoc @@ -139,7 +139,7 @@ When defining a histogram metric SLI, set the following fields: [[apm-latency-sli]] === APM latency -Create an indicator based on the APM data that you received from your instrumented services and a latency threshold. +Create an indicator based on latency data received from your instrumented services and a latency threshold. *Example:* You can define an indicator on an APM service named `banking-service` for the `production` environment, and the transaction name `POST /deposit` with a latency threshold value of 300ms. @@ -147,7 +147,8 @@ Create an indicator based on the APM data that you received from your instrument [[apm-availability-sli]] === APM availability -Create an indicator based on the APM data received from your instrumented services. +Create an indicator based on the availability of your instrumented services. +Availability is determined by calculating the percentage of successful transactions (`event.outcome : "success"`) out of the total number of successful and failed transactions—unknown outcomes are excluded. *Example:* You can define an indicator on an APM service named `search-service` for the `production` environment, and the transaction name `POST /search`.