diff --git a/content/en/observability_pipelines/destinations/amazon_opensearch.md b/content/en/observability_pipelines/destinations/amazon_opensearch.md
index 8b65c5941a6..24d06091a24 100644
--- a/content/en/observability_pipelines/destinations/amazon_opensearch.md
+++ b/content/en/observability_pipelines/destinations/amazon_opensearch.md
@@ -37,6 +37,7 @@ After you select the Amazon OpenSearch destination in the pipeline UI:
 			- In the {{< ui >}}Type{{< /ui >}} field, enter the category of data being ingested, for example `logs`.
 			- In the {{< ui >}}Dataset{{< /ui >}} field, specify the format or data source that describes the structure, for example `apache`.
 			- In the {{< ui >}}Namespace{{< /ui >}} field, enter the grouping for organizing your data streams, for example `production`.
+			- You can use [template syntax][3] for the {{< ui >}}Type{{< /ui >}}, {{< ui >}}Dataset{{< /ui >}}, and {{< ui >}}Namespace{{< /ui >}} fields to dynamically construct the data stream name based on specific fields in your logs.
 			- In the UI, there is a preview of the data stream name you configured. With the above example inputs, the data stream name that the Worker writes to is `logs-apache-production`.
 1. Optionally, enter the name of the Amazon OpenSearch index. See [template syntax][3] if you want to route logs to different indexes based on specific fields in your logs.
 1. Select an authentication strategy, {{< ui >}}Basic{{< /ui >}} or {{< ui >}}AWS{{< /ui >}}. If you selected:
diff --git a/content/en/observability_pipelines/destinations/elasticsearch.md b/content/en/observability_pipelines/destinations/elasticsearch.md
index 0c714b7e264..5842fc54828 100644
--- a/content/en/observability_pipelines/destinations/elasticsearch.md
+++ b/content/en/observability_pipelines/destinations/elasticsearch.md
@@ -42,6 +42,7 @@ After you select the Elasticsearch destination in the pipeline UI:
 			1. In the {{< ui >}}Type{{< /ui >}} field, enter the category of data being ingested, for example `logs` or `metrics`.
 			1. In the {{< ui >}}Dataset{{< /ui >}} field, specify the format or data source that describes the structure, for example `apache`.
 			1. In the {{< ui >}}Namespace{{< /ui >}} field, enter the grouping for organizing your data streams, for example `production`.
+			- You can use [template syntax][3] for the {{< ui >}}Type{{< /ui >}}, {{< ui >}}Dataset{{< /ui >}}, and {{< ui >}}Namespace{{< /ui >}} fields to dynamically construct the data stream name based on specific fields in your logs or metrics.
 			1. Enable the {{< ui >}}Auto routing{{< /ui >}} toggle to automatically route events to a data stream based on the event content.
 			1. Enable the {{< ui >}}Sync fields{{< /ui >}} toggle to synchronize data stream fields with the Elasticsearch index mapping.
 			- In the UI, there is a preview of the data stream name you configured. If the fields are left blank, the default data stream name used is `logs-generic-default` for logs and `metrics-generic-default` for metrics. With the above example inputs, the data stream name that the Worker writes to is:
diff --git a/content/en/observability_pipelines/destinations/opensearch.md b/content/en/observability_pipelines/destinations/opensearch.md
index 9ce5fe96a8b..81fbd914d53 100644
--- a/content/en/observability_pipelines/destinations/opensearch.md
+++ b/content/en/observability_pipelines/destinations/opensearch.md
@@ -39,6 +39,7 @@ After you select the OpenSearch destination in the pipeline UI:
 			- In the {{< ui >}}Type{{< /ui >}} field, enter the category of data being ingested, for example `logs`.
 			- In the {{< ui >}}Dataset{{< /ui >}} field, specify the format or data source that describes the structure, for example `apache`.
 			- In the {{< ui >}}Namespace{{< /ui >}} field, enter the grouping for organizing your data streams, for example `production`.
+			- You can use [template syntax][3] for the {{< ui >}}Type{{< /ui >}}, {{< ui >}}Dataset{{< /ui >}}, and {{< ui >}}Namespace{{< /ui >}} fields to dynamically construct the data stream name based on specific fields in your logs.
 			- In the UI, there is a preview of the data stream name you configured. With the above example inputs, the data stream name that the Worker writes to is `logs-apache-production`.
 
 ### Optional settings