From 4a783b9b86cbe0f8a59a83ab3c1123b9d87f5550 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Thu, 12 Dec 2024 12:11:44 -0800 Subject: [PATCH] Update apm-spaces.asciidoc (#4588) (#4682) (cherry picked from commit 008f24a892264658525f3966bedbcf72e512ec82) Co-authored-by: Julien Orain --- .../apm/security/data-security/apm-spaces.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc b/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc index d7fab241ba..f213ef547c 100644 --- a/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc +++ b/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc @@ -5,7 +5,7 @@ Starting in version 8.2.0, the Applications UI is {kibana-ref}/xpack-spaces.html This allows you to separate your data--and access to that data--by team, use case, service environment, or any other filter that you choose. -To take advantage of this feature, your APM data needs to be written to different data steams. +To take advantage of this feature, your APM data needs to be written to different data streams. One way to accomplish this is with different namespaces. For example, you can send production data to an APM integration with a namespace of `production`, while sending staging data to a different APM integration with a namespace of `staging`.