From 544b065d3289d7b016932b35d50c03a0998938c6 Mon Sep 17 00:00:00 2001 From: Mike Birnstiehl Date: Mon, 27 Oct 2025 14:16:42 -0500 Subject: [PATCH 1/6] [Streams] Add section on managed assets --- solutions/observability/streams/streams.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/solutions/observability/streams/streams.md b/solutions/observability/streams/streams.md index cc0a1a161f..99dbcbdd73 100644 --- a/solutions/observability/streams/streams.md +++ b/solutions/observability/streams/streams.md @@ -37,6 +37,11 @@ Wired streams: For more information, refer to [sending data to wired streams](./wired-streams.md). +## Managed assets +When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level assets like templates and pipelines are created for the stream. These assets are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible. + +You can still edit non-managed ingest pipelines, templates, and other assets, but avoid editing assets marked as *managed* or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles assets managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed assets. + ## Required permissions Streams requires the following permissions: From e53d71442ac53121c64bdfe67a7aa433b09d24a5 Mon Sep 17 00:00:00 2001 From: Mike Birnstiehl Date: Mon, 27 Oct 2025 14:31:02 -0500 Subject: [PATCH 2/6] update advanced tab --- solutions/observability/streams/management/advanced.md | 8 ++++---- solutions/observability/streams/streams.md | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/solutions/observability/streams/management/advanced.md b/solutions/observability/streams/management/advanced.md index 3c89063f3d..8d63abba93 100644 --- a/solutions/observability/streams/management/advanced.md +++ b/solutions/observability/streams/management/advanced.md @@ -26,16 +26,16 @@ Features provide useful information for AI processes, such as significant events ## Index configuration [streams-advanced-index-config] -:::{note} -Processing and schema changes should typically be done through the Streams interface, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows. +:::{Important} +Avoid editing assets marked as *managed* or any per-data-stream mappings and settings. Processing and schema changes should typically be done through the Streams interface or API, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows. ::: -For classic streams, you can manually configure: +For classic streams, you can access the following assets: - [Index templates](../../../../manage-data/data-store/templates.md#index-templates) - [Component templates](../../../../manage-data/data-store/templates.md#component-templates) - [Pipelines](../../../../manage-data/ingest/transform-enrich.md) -- [Data streams](../../../../manage-data/data-store/data-streams.md). +- [Data streams](../../../../manage-data/data-store/data-streams.md) For both wired ({applies_to}`stack: preview 9.2`) and classic streams, you can manually configure: diff --git a/solutions/observability/streams/streams.md b/solutions/observability/streams/streams.md index 99dbcbdd73..d53bb82fbd 100644 --- a/solutions/observability/streams/streams.md +++ b/solutions/observability/streams/streams.md @@ -40,7 +40,7 @@ For more information, refer to [sending data to wired streams](./wired-streams.m ## Managed assets When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level assets like templates and pipelines are created for the stream. These assets are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible. -You can still edit non-managed ingest pipelines, templates, and other assets, but avoid editing assets marked as *managed* or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles assets managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed assets. +You can still edit non-managed ingest pipelines, templates, and other assets, but avoid editing assets marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles assets managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed assets. ## Required permissions From db8df24bc9cf4f083c5e6c6577886b2e6be1a3f2 Mon Sep 17 00:00:00 2001 From: Mike Birnstiehl Date: Mon, 27 Oct 2025 14:44:24 -0500 Subject: [PATCH 3/6] update language --- solutions/observability/streams/management/advanced.md | 4 ++-- solutions/observability/streams/streams.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/solutions/observability/streams/management/advanced.md b/solutions/observability/streams/management/advanced.md index 8d63abba93..f95fe09802 100644 --- a/solutions/observability/streams/management/advanced.md +++ b/solutions/observability/streams/management/advanced.md @@ -27,10 +27,10 @@ Features provide useful information for AI processes, such as significant events ## Index configuration [streams-advanced-index-config] :::{Important} -Avoid editing assets marked as *managed* or any per-data-stream mappings and settings. Processing and schema changes should typically be done through the Streams interface or API, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows. +Avoid editing components marked as **managed** or any per-data-stream mappings and settings. Processing and schema changes should typically be done through the Streams interface or API, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows. ::: -For classic streams, you can access the following assets: +For classic streams, you can access the following components: - [Index templates](../../../../manage-data/data-store/templates.md#index-templates) - [Component templates](../../../../manage-data/data-store/templates.md#component-templates) diff --git a/solutions/observability/streams/streams.md b/solutions/observability/streams/streams.md index d53bb82fbd..dc27a0a931 100644 --- a/solutions/observability/streams/streams.md +++ b/solutions/observability/streams/streams.md @@ -37,10 +37,10 @@ Wired streams: For more information, refer to [sending data to wired streams](./wired-streams.md). -## Managed assets -When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level assets like templates and pipelines are created for the stream. These assets are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible. +## Managed components +When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level components like templates and pipelines are created for the stream. These components are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible. -You can still edit non-managed ingest pipelines, templates, and other assets, but avoid editing assets marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles assets managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed assets. +You can still edit non-managed ingest pipelines, templates, and other components, but avoid those marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles components managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed components. ## Required permissions From 0363a3667740c1135b45c2ab2178441b7f9dbc34 Mon Sep 17 00:00:00 2001 From: Mike Birnstiehl Date: Mon, 27 Oct 2025 14:45:25 -0500 Subject: [PATCH 4/6] typo --- solutions/observability/streams/streams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/observability/streams/streams.md b/solutions/observability/streams/streams.md index dc27a0a931..f99f92ad37 100644 --- a/solutions/observability/streams/streams.md +++ b/solutions/observability/streams/streams.md @@ -40,7 +40,7 @@ For more information, refer to [sending data to wired streams](./wired-streams.m ## Managed components When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level components like templates and pipelines are created for the stream. These components are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible. -You can still edit non-managed ingest pipelines, templates, and other components, but avoid those marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles components managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed components. +You can still edit non-managed ingest pipelines, templates, and other components, but avoid those marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles components managed by integrations. Refer to the [Advanced tab](./management/advanced.md) to review managed components. ## Required permissions From 6cceeaa876d49fcb876bc29e5eef6ffdf1e4895e Mon Sep 17 00:00:00 2001 From: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com> Date: Mon, 27 Oct 2025 15:57:48 -0500 Subject: [PATCH 5/6] Update solutions/observability/streams/streams.md Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> --- solutions/observability/streams/streams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/observability/streams/streams.md b/solutions/observability/streams/streams.md index f99f92ad37..d00bdfba6b 100644 --- a/solutions/observability/streams/streams.md +++ b/solutions/observability/streams/streams.md @@ -40,7 +40,7 @@ For more information, refer to [sending data to wired streams](./wired-streams.m ## Managed components When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level components like templates and pipelines are created for the stream. These components are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible. -You can still edit non-managed ingest pipelines, templates, and other components, but avoid those marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles components managed by integrations. Refer to the [Advanced tab](./management/advanced.md) to review managed components. +You can still edit non-managed ingest pipelines, templates, and other components, but avoid those marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles components managed by integrations. Refer to the [**Advanced** tab](./management/advanced.md) to review managed components. ## Required permissions From 0dee7be57c8dd3943f8b85fb099a3281508ba59e Mon Sep 17 00:00:00 2001 From: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com> Date: Mon, 27 Oct 2025 16:00:29 -0500 Subject: [PATCH 6/6] Update configuration details for streams --- solutions/observability/streams/management/advanced.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/solutions/observability/streams/management/advanced.md b/solutions/observability/streams/management/advanced.md index f95fe09802..b9688a1c13 100644 --- a/solutions/observability/streams/management/advanced.md +++ b/solutions/observability/streams/management/advanced.md @@ -37,8 +37,8 @@ For classic streams, you can access the following components: - [Pipelines](../../../../manage-data/ingest/transform-enrich.md) - [Data streams](../../../../manage-data/data-store/data-streams.md) -For both wired ({applies_to}`stack: preview 9.2`) and classic streams, you can manually configure: +For both wired ({applies_to}`stack: preview 9.2` {applies_to}`serverless: preview`) and classic streams, you can manually configure: - **Shards:** Control how the index is split across nodes. More shards can improve parallelism but may increase overhead. - **Replicas:** Define how many copies of the data exist. More replicas improve resilience and read performance but increase storage usage. -- **Refresh interval:** Control how frequently new data becomes visible for search. A longer interval reduces resource usage; a short one makes data searchable sooner. \ No newline at end of file +- **Refresh interval:** Control how frequently new data becomes visible for search. A longer interval reduces resource usage; a short one makes data searchable sooner.