add Streams 9.2 updates

solutions/observability/streams/management/advanced.md

@@ -1,11 +1,44 @@
 ---
 applies_to:
-  serverless: preview
-  stack: preview 9.1
+  serverless: ga
+  stack: preview 9.1, ga 9.2
 navigation_title: Configure advanced settings
 ---
 # Configure advanced settings for streams [streams-advanced-settings]
 
-The **Advanced** tab on the **Manage stream** page shows the underlying configuration details of your stream. While Streams simplifies many configurations, it doesn't support modifying all pipelines and templates. From the **Advanced** tab, you can manually interact with the index or component templates or modify other ingest pipelines that used by the stream.
+The **Advanced** tab shows the underlying {{es}} configuration details and advanced configuration options for your stream.
 
-This UI is intended for advanced users.
+You can use the **Advanced** tab to add [descriptions](#streams-advanced-description) or [features](#streams-advanced-features) that provide useful information to Stream's AI components. You can also  [manually configure](#streams-advanced-index-config) the index or component templates or modify other ingest pipelines used by the stream.
+
+## Stream description [streams-advanced-description]
+
+Describe the data in the stream. AI features like system identification and significant events use this description when generating suggestions.
+
+## Stream feature configuration [streams-advanced-features]
+
+Streams analyzes your data and identifies features. Features are a way to classify some of the data you have in your stream.
+
+Each feature has a natural language description and an optional filter which points to a subset of your data.
+
+For example, in a stream of Kubernetes logs, the feature identification process would be able to identify that you have data from "nginx" which can be found by filtering for `WHERE service.name==nginx`. It would also include a description defining nginx.
+
+Features provide useful information for AI processes, such as significant events, and are used as the foundation for them.
+
+## 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.
+:::
+
+For classic streams, you can manually configure:
+
+- [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).
+
+For both wired ({applies_to}`stack: preview 9.2`) 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.

solutions/observability/streams/management/data-quality.md

@@ -0,0 +1,31 @@
+---
+applies_to:
+  serverless: preview
+  stack: preview 9.1, ga 9.2
+---
+
+# Manage data quality [streams-data-retention]
+
+After selecting a stream, use the **Data quality** tab to find failed and degraded documents in your stream. Use the following components to monitor the health of your data and identify and fix issues:
+
+- **Degraded documents:** Documents with the `ignored` property usually because of malformed fields or exceeding the limit of total fields when `ignore_above:false`. This component shows the total number of degraded documents, the percentage, and status (**Good**, **Degraded**, **Poor**).
+- **Failed documents:**: Documents that were rejected during ingestion because of mapping conflicts or pipeline failures.
+- **Quality score:** Streams calculates the overall quality score (**Good**, **Degraded**, **Poor**) based on the percentage of degraded and failed documents.
+- **Trends over time:** A time-series chart so you can track how degraded and failed documents are accumulating over time. Use the date picker to zoom into a specific range and understand when problems are spiking.
+- **Issues:** {applies_to}`stack: preview 9.2`Find issues with specific fields, how often they've occurred, and when they've occurred.
+
+## Failure store
+
+A [failure store](../../../../manage-data/data-store/data-streams/failure-store.md) is a secondary set of indices inside a data stream, dedicated to storing failed documents. Instead of losing documents that are rejected during ingestion, a failure store retains it in a `::failures` index, so you can review failed documents to understand what went wrong and how to fix it.
+
+### Required permissions
+To view and modify failure store in {{stack}}, you need the following data stream level privileges:
+- `read_failure_store`
+- `manage_failure_store`
+
+For more information, refer to [Granting privileges for data streams and aliases](../../../../deploy-manage/users-roles/cluster-or-deployment-auth/granting-privileges-for-data-streams-aliases.md).
+
+### Turn on failure stores
+In Streams, you need to turn on failure stores to get failed documents. To do this, select **Enable failure store** in the **Failed documents** component. From here you can set your failure store retention period.
+
+For more information on data quality, refer to the [data set quality](../../data-set-quality-monitoring.md) documentation.