Configure advanced settings for streams

The Advanced tab shows the underlying Elasticsearch configuration details and advanced configuration options for your stream.

You can use the Advanced tab to add descriptions or features that provide useful information to Stream's AI components. You can also manually configure the index or component templates or modify other ingest pipelines used by the stream.

Stream description

Describe the data in the stream. AI features like system identification use this description when generating suggestions.

Stream feature configuration

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.

Index configuration

Important

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 components:

For both wired ( The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Preview since 9.2 This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Preview This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. ) 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.