[DOCS-12495] Update Set Up Pipelines

content/en/observability_pipelines/configuration/install_the_worker/_index.md

@@ -395,6 +395,10 @@ sudo apt-get remove --purge observability-pipelines-worker
 {{% /tab %}}
 {{< /tabs >}}
 
+## Index your Worker logs
+
+Make sure your Worker logs are [indexed][9] in Log Management for optimal functionality. The logs provide deployment information, such as Worker status, version, and any errors, that is shown in the UI. The logs are also helpful for troubleshooting Worker or pipelines issues. All Worker logs have the tag `source:op_worker`.
+
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
@@ -407,3 +411,4 @@ sudo apt-get remove --purge observability-pipelines-worker
 [6]: /api/latest/observability-pipelines/#create-a-new-pipeline
 [7]: /observability_pipelines/guide/environment_variables/
 [8]: https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/observability_pipeline
+[9]: /logs/log_configuration/indexes/

content/en/observability_pipelines/configuration/set_up_pipelines.md

@@ -34,7 +34,7 @@ In Observability Pipelines, a pipeline is a sequential path with three types of
 Set up your pipelines and its sources, processors, and destinations in the Observability Pipelines UI.
 
 1. Navigate to [Observability Pipelines][13].
-1. Select a template.
+1. Select a template based on your use case.
     - [Archive Logs][4]
     - [Dual Ship Logs][5]
     - [Generate Metrics][6]
@@ -43,40 +43,66 @@ Set up your pipelines and its sources, processors, and destinations in the Obser
     - [Sensitive Data Redaction][9]
     - [Split Logs][10]
 1. Select and set up your [source][1].
-1. Select and set up your [destinations][2].
-1. Set up your [processors][3].
+1. Add [processors][2] to transform, redact, and enrich log data.
     - If you want to copy a processor, click the copy icon for that processor and then use `command-v` to paste it.
-1. If you want to add another group of processors for a destination:
-    1. Click the plus sign (**+**) at the bottom of the existing processor group.
-    1. Click the name of the processor group to update it.
-    1. Optionally, enter a group filter. See [Filter Syntax](#filter-query-syntax) for more information.
-    1. Click **Add** to add processors to the group.
-    1. If you want to copy all the processors in a group and paste them into the same processor group or a different group:
-       1. Click the three dots on the processor group.
-       1. Select **Copy all processors**.
-       1. Select the processor group you want to paste the processors into and then use `command-v` to paste them.
-    1. You can toggle the switch to enable and disable the processor group and also each individual processor.
-  <br>**Notes**:
-  <br>- Configuring a pipeline with processor groups is available for Worker versions 2.7 and later.
-  <br>- There is a limit of 10 processor groups for a pipeline canvas.
-1. If you want to add another set of processors and destinations, click the plus sign (**+**) to the left of the processor group to add another set of processors and destinations to the source.
-    - To delete a processor group, you need to delete all destinations linked to that processor group. When the last destination is deleted, the processor group is removed with it.
-1. 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 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.
+1. Select and set up [destinations][3] for your processed logs.
+
+### Add or remove components
+
+#### 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%;" >}}
+
+If you want to add another group of processors for a destination:
+1. Click the plus sign (**+**) at the bottom of the existing processor group.
+1. Click the name of the processor group to update it.
+1. Optionally, enter a group filter. See [Filter Syntax][17] for more information.
+1. Click **Add** to add processors to the group.
+1. If you want to copy all processors in a group and paste them into the same processor group or a different group:
+    1. Click the three dots on the processor group.
+    1. Select **Copy all processors**.
+    1. Select the desired processor group, and then paste the processors into it.
+1. You can toggle the switch to enable and disable the processor group and also each individual processor.
+
+**Notes**:
+<br>- Configuring a pipeline with processor groups is available for Worker versions 2.7 and later.
+<br>- There is a limit of 10 processor groups for a pipeline canvas.
+
+#### 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%;" >}}
+
+If you want to add another set of processors and destinations, click the plus sign (**+**) to the left of the processor group to add another set of processors and destinations to the source.
+
+To delete a processor group, you need to delete all destinations linked to that processor group. When the last destination is deleted, the processor group is removed with it.
+
+#### 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%;" >}}
+
+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**.
+
+**Notes**:
+- 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.
+
+### Install the Worker and deploy the pipeline
+
+After you have set up your source, processors, and destinations:
+
 1. Click **Next: Install**.
 1. Select the platform on which you want to install the Worker.
 1. Enter the [environment variables][15] for your sources and destinations, if applicable.
-1. Follow the instructions on installing the Worker for your platform. The command provided in the UI to install the Worker has the relevant environment variables populated. See [Install the Observability Pipelines Worker][12] for more information.
+1. Follow the instructions on installing the Worker for your platform. The command provided in the UI to install the Worker has the relevant environment variables populated.
+    - See [Install the Worker][12] for more information.
     - **Note**: If you are using a proxy, see the `proxy` option in [Bootstrap options][16].
 1. Enable out-of-the-box monitors for your pipeline.
-    1. Navigate to the [Pipelines][1] page and find your pipelines.
+    1. Navigate to the [Pipelines][13] page and find your pipeline.
     1. Click **Enable monitors** in the **Monitors** column for your pipeline.
     1. Click **Start** to set up a monitor for one of the suggested use cases.<br>
-      The new metric monitor page is configured based on the use case you selected. You can update the configuration to further customize it. See the [Metric monitor documentation][14] for more information.
+        - The metric monitor is configured based on the selected use case. You can update the configuration to further customize it. See the [Metric monitor documentation][14] for more information.
 
 After you have set up your pipeline, see [Update Existing Pipelines][11] if you want to make any changes to it.
 
@@ -96,20 +122,21 @@ After you have set up your pipeline, see [Update Existing Pipelines][11] if you
 [14]: /monitors/types/metric/
 [15]: /observability_pipelines/guide/environment_variables/
 [16]: /observability_pipelines/configuration/install_the_worker/advanced_worker_configurations/#bootstrap-options
+[17]: /observability_pipelines/processors/#filter-query-syntax
 
 {{% /tab %}}
 {{% tab "API" %}}
 
 <div class="alert alert-danger">Creating pipelines using the Observability Pipelines API is in Preview. Fill out the <a href="https://www.datadoghq.com/product-preview/observability-pipelines-api-and-terraform-support/"> form</a> to request access.</div>
 
 1. You can use Observability Pipelines API to [create a pipeline][1].
-1. After creating the pipeline, [install the Worker][2] to send logs through it.
+1. After creating the pipeline, [install the Worker][2] to send logs through the pipeline.
     - See [Environment Variables][4] for the list of environment variables you need for the different sources, processor, and destinations when you install the Worker.
 
 **Note**: Pipelines created using the API are read-only in the UI. Use the [update a pipeline][3] endpoint to make any changes to an existing pipeline.
 
 [1]: /api/latest/observability-pipelines/#create-a-new-pipeline
-[2]: /observability_pipelines/configuration/install_the_worker/
+[2]: /observability_pipelines/configuration/install_the_worker/?tab=docker#api-or-terraform-pipeline-setup
 [3]: /api/latest/observability-pipelines/#update-a-pipeline
 [4]: /observability_pipelines/guide/environment_variables/
 
@@ -119,38 +146,46 @@ After you have set up your pipeline, see [Update Existing Pipelines][11] if you
 <div class="alert alert-danger">Creating pipelines using Terraform is in Preview. Fill out the <a href="https://www.datadoghq.com/product-preview/observability-pipelines-api-and-terraform-support/"> form</a> to request access.</div>
 
 1. You can use the [datadog_observability_pipeline][1] module to create a pipeline using Terraform.
-1. After creating the pipeline, [install the Worker][2] to send logs through it.
+1. After creating the pipeline, [install the Worker][2] to send logs through the pipeline.
     - See [Environment Variables][3] for the list of environment variables you need for the different sources, processor, and destinations when you install the Worker.
 
 Pipelines created using Terraform are read-only in the UI. Use the [datadog_observability_pipeline][1] module to make any changes to an existing pipeline.
 
 [1]: https://registry.terraform.io/providers/DataDog/datadog/latest/docs
-[2]: /observability_pipelines/configuration/install_the_worker/
+[2]: /observability_pipelines/configuration/install_the_worker/?tab=docker#api-or-terraform-pipeline-setup
 [3]: /observability_pipelines/guide/environment_variables/
 
 {{% /tab %}}
 {{< /tabs >}}
 
 See [Advanced Worker Configurations][5] for bootstrapping options.
 
-### Index your Worker logs
-
-Make sure your Worker logs are [indexed][6] in Log Management for optimal functionality. The logs provide deployment information, such as Worker status, version, and any errors, that is shown in the UI. The logs are also helpful for troubleshooting Worker or pipelines issues. All Worker logs have the tag `source:op_worker`.
-
 ## Clone a pipeline
 
+To clone a pipeline in the UI:
+
 1. Navigate to [Observability Pipelines][4].
 1. Select the pipeline you want to clone.
 1. Click the cog at the top right side of the page, then select **Clone**.
 
 ## Delete a pipeline
 
+To delete a pipeline in the UI:
+
 1. Navigate to [Observability Pipelines][4].
 1. Select the pipeline you want to delete.
 1. Click the cog at the top right side of the page, then select **Delete**.
 
+You can also use the [API][6] to delete a pipeline
+
 **Note**: You cannot delete an active pipeline. You must stop all Workers for a pipeline before you can delete it.
 
+## Pipeline requirements and limits
+
+- 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.
+
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}
@@ -160,4 +195,4 @@ Make sure your Worker logs are [indexed][6] in Log Management for optimal functi
 [3]: /observability_pipelines/destinations/
 [4]: https://app.datadoghq.com/observability-pipelines
 [5]: /observability_pipelines/configuration/install_the_worker/advanced_worker_configurations/
-[6]: /logs/log_configuration/indexes/
+[6]: /api/latest/observability-pipelines/#delete-a-pipeline

content/en/observability_pipelines/monitoring_and_troubleshooting/troubleshooting.md

@@ -168,7 +168,7 @@ The quota processor is synchronized across all Workers in a Datadog organization
 [7]: https://app.datadoghq.com/logs/
 [8]: /containers/docker/log/?tab=containerinstallation#linux
 [9]: /containers/guide/container-discovery-management/?tab=helm#setting-environment-variables
-[10]: /observability_pipelines/configuration/set_up_pipelines/#index-your-worker-logs
+[10]: /observability_pipelines/configuration/install_the_worker/#index-your-worker-logs
 [11]: /observability_pipelines/install_the_worker#uninstall-the-worker
 [12]: https://app.datadoghq.com/logs
 [13]: /observability_pipelines/configuration/install_the_worker/worker_commands/