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

[8.13] Add missing step to edit integration policy namespace (backport #993) #994

Merged
merged 1 commit into from
Apr 1, 2024
Merged

[8.13] Add missing step to edit integration policy namespace (backport #993) #994

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion docs/en/ingest-management/data-streams.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,9 @@ You can also use matching patterns to give users access to data when creating us
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**.
. On the **Installed integrations** tab, select the integration that you'd like to update.
. Open the **Integration policies** tab.
. From the **Actions** menu next to the integration that you'd like to update, select *Edit integration*.
. From the **Actions** menu next to the integration, 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