[DOCS-15572] Updates for multiple destinations

hugo/content/en/observability_pipelines/configuration/set_up_pipelines.md

@@ -57,21 +57,19 @@ See [Export a Pipeline Configuration to JSON or Terraform][14] if you want to pr
       - For a pipeline canvas, there is a limit of 25 processor groups and a total of 150 processors.
       - If you want to copy a processor, click the copy icon for that processor and then use `command-v` to paste it.
 
-#### Add or remove components
-
-##### Add another processor group
+#### Add another processor group
 
 {{< img src="observability_pipelines/setup/another_processor_group.png" alt="The Pipelines page showing two processor groups sending logs to the same destination" style="width:100%;" >}}
 
 {{% observability_pipelines/set_up_pipelines/add_another_processor_group %}}
 
-##### Add another set of processors and destinations
+#### Add another set of processors and destinations
 
 {{< img src="observability_pipelines/setup/another_set_processor_destination.png" alt="The Pipelines page showing two processor groups sending logs to two different destinations" style="width:100%;" >}}
 
 {{% observability_pipelines/set_up_pipelines/add_another_set_of_processors_and_destinations %}}
 
-##### Add another destination to a processor group
+#### Add another destination to a processor group
 
 {{< img src="observability_pipelines/setup/another_destination.png" alt="The Pipelines page showing one processor group sending logs to two different destinations" style="width:100%;" >}}
 
@@ -99,10 +97,22 @@ See [Export a Pipeline Configuration to JSON or Terraform][14] if you want to pr
 
 #### Add another processor group
 
-{{< img src="observability_pipelines/setup/another_processor_group_metrics.png" alt="The Pipelines page showing two processor groups sending logs to the same destination" style="width:100%;" >}}
+{{< img src="observability_pipelines/setup/another_processor_group_metrics.png" alt="The Pipelines page showing two processor groups sending metrics to the same destination" style="width:100%;" >}}
 
 {{% observability_pipelines/set_up_pipelines/add_another_processor_group %}}
 
+#### Add another set of processors and destinations
+
+{{< img src="observability_pipelines/setup/another_set_processor_destination_metrics.png" alt="The Pipelines page showing two processor groups sending metrics to two different destinations" style="width:100%;" >}}
+
+{{% observability_pipelines/set_up_pipelines/add_another_set_of_processors_and_destinations %}}
+
+#### Add another destination to a processor group
+
+{{< img src="observability_pipelines/setup/another_destination_metrics.png" alt="The Pipelines page showing one processor group sending metrics to two different destinations" style="width:100%;" >}}
+
+{{% observability_pipelines/set_up_pipelines/add_another_destination %}}
+
 [1]: https://app.datadoghq.com/observability-pipelines
 [2]: /observability_pipelines/configuration/explore_templates/?tab=metrics#metric-tag-governance
 [3]: /observability_pipelines/sources/?tab=metrics#sources

hugo/content/en/observability_pipelines/destinations/_index.md

@@ -17,7 +17,9 @@ further_reading:
 
 Use the Observability Pipelines Worker to send your processed logs and metrics to different destinations. Most Observability Pipelines destinations send events in batches to the downstream integration. See [Event batching](#event-batching) for more information. Some Observability Pipelines destinations also have fields that support template syntax, so you can set these fields based on specific fields. See [Template syntax](#template-syntax) for more information.
 
-Select a destination in the left navigation menu to see more information about it.
+**Notes**:
+- You can add a total of 20 destinations for a pipeline.
+- If you add multiple destinations of the same type to a pipeline, you must use [Secrets Management][4]. For example, if you add two HTTP Client destinations for two different HTTP clients, you must use secret identifiers for the HTTP client URIs. You cannot use the default `DESTINATION_HTTP_CLIENT_URI` to store the two different HTTP client URIs.
 
 ## Destinations
 
@@ -178,3 +180,4 @@ If the destination receives 3 events within 2 seconds, it flushes a batch with 2
 [1]: /observability_pipelines/configuration/set_up_pipelines/
 [2]: https://app.datadoghq.com/observability-pipelines
 [3]: https://docs.rs/chrono/0.4.19/chrono/format/strftime/index.html#specifiers
+[4]: /observability_pipelines/configuration/secrets_management/

hugo/layouts/shortcodes/observability_pipelines/set_up_pipelines/add_another_destination.en.md

@@ -1,11 +1,13 @@
 If you want to add an additional destination to a processor group, click the plus sign (**+**) to the right of the processor group.
 
-To delete a destination, click on the pencil icon to the top right of the destination, and select **Delete node**.
+To delete a destination, click on the trash icon to the top right of the destination.
 - If you delete a destination from a processor group that has multiple destinations, only the deleted destination is removed.
 - If you delete a destination from a processor group that only has one destination, both the destination and the processor group are removed.
 
 **Notes**:
 
 - A pipeline must have at least one destination. If a processor group only has one destination, that destination cannot be deleted.
-- You can add a total of three destinations for a pipeline.
-- A specific destination can only be added once. For example, you cannot add multiple Splunk HEC destinations.
+- You can add a total of 20 destinations for a pipeline.
+- If you add multiple destinations of the same type to a pipeline, you must use [Secrets Management][101]. For example, if you add two HTTP Client destinations for two different HTTP clients, you must use secret identifiers for the HTTP client URIs. You cannot use the default `DESTINATION_HTTP_CLIENT_URI` to store the two different HTTP client URIs.
+
+[101]: /observability_pipelines/configuration/secrets_management/