Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add details about agent namespaces cascading to integration policies #822

Merged
merged 2 commits into from
Jan 18, 2024
Merged

Add details about agent namespaces cascading to integration policies #822

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e204026
Add details about agent namespaces cascading to integration policies
kilfoyle Jan 17, 2024
9743f92
Fixup
kilfoyle Jan 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/en/ingest-management/data-streams.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down