From e2040266c79fb8bded7659465fd5cfa6fc1fb342 Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Wed, 17 Jan 2024 11:43:48 -0500 Subject: [PATCH 1/2] Add details about agent namespaces cascading to integration policies --- docs/en/ingest-management/data-streams.asciidoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/en/ingest-management/data-streams.asciidoc b/docs/en/ingest-management/data-streams.asciidoc index aa9630310..94c905584 100644 --- a/docs/en/ingest-management/data-streams.asciidoc +++ b/docs/en/ingest-management/data-streams.asciidoc @@ -42,6 +42,13 @@ A `namespace` can be up to 100 bytes in length (multibyte characters will count Using a namespace makes it easier to search data from a given source by using a matching pattern. You can also use matching patterns to give users access to data when creating user roles. // Corresponds to the `data_stream.dataset` field. ++ +By default the namespace defined for an agent policy is propagated to all integrations in that policy. if you'd like to define a more granular namespace for a policy: + +. In {kib}, go to **Management -> Integrations**. +. Open the **Integration policies** tab. +. From the **Actions** menu next to the integration that you'd like to update, select *Edit integration*. +. Open the advanced options and update the **Namespace** field. Data streams from the integration will now use the specified namespace rather than the default namespace inherited from the {agent} policy. The naming scheme separates each components with a `-` character: From 9743f92280e154cb3f23c2d02d106091ce059c4b Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Wed, 17 Jan 2024 13:40:12 -0500 Subject: [PATCH 2/2] Fixup --- docs/en/ingest-management/data-streams.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/data-streams.asciidoc b/docs/en/ingest-management/data-streams.asciidoc index 94c905584..5c9746d71 100644 --- a/docs/en/ingest-management/data-streams.asciidoc +++ b/docs/en/ingest-management/data-streams.asciidoc @@ -43,7 +43,7 @@ Using a namespace makes it easier to search data from a given source by using a You can also use matching patterns to give users access to data when creating user roles. // Corresponds to the `data_stream.dataset` field. + -By default the namespace defined for an agent policy is propagated to all integrations in that policy. if you'd like to define a more granular namespace for a policy: +By default the namespace defined for an {agent} policy is propagated to all integrations in that policy. if you'd like to define a more granular namespace for a policy: . In {kib}, go to **Management -> Integrations**. . Open the **Integration policies** tab.