diff --git a/content/en/observability_pipelines/configuration/set_up_pipelines.md b/content/en/observability_pipelines/configuration/set_up_pipelines.md
index 01334a989b5..1608f66add9 100644
--- a/content/en/observability_pipelines/configuration/set_up_pipelines.md
+++ b/content/en/observability_pipelines/configuration/set_up_pipelines.md
@@ -90,7 +90,6 @@ To delete a destination, click on the pencil icon to the top right of the destin
 
 - 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]: /observability_pipelines/sources/
 [2]: /observability_pipelines/processors/
diff --git a/content/en/observability_pipelines/destinations/datadog_logs.md b/content/en/observability_pipelines/destinations/datadog_logs.md
index 41ea0046719..744b1be4ec6 100644
--- a/content/en/observability_pipelines/destinations/datadog_logs.md
+++ b/content/en/observability_pipelines/destinations/datadog_logs.md
@@ -16,11 +16,41 @@ Set up the Datadog Logs destination and its environment variables when you [set
 
 ### Set up the destination
 
-1. Optionally, toggle the switch to enable **Buffering Options**.<br>**Note**: Buffering options is in Preview. Contact your account manager to request access.
-	- If left disabled, the maximum size for buffering is 500 events.
-	- If enabled:
-		1. Select the buffer type you want to set (**Memory** or **Disk**).
-		1. Enter the buffer size and select the unit.
+There are no required setup steps.
+
+#### Optional settings
+
+##### Route logs to multiple Datadog organizations
+
+You can route logs to multiple Datadog organizations. After you set up routing to multiple organizations, you can [view metrics for the component or specific organizations](#view-metrics-for-the-component-or-specific-organizations) to which you are routing logs.
+
+Click **Route to Multiple Organizations** to set up routing to multiple Datadog organizations.
+
+- If you haven't added any organizations yet, enter organization details as described in the [Add a Datadog organization](#add-an-organization) section.
+- If you have already added organizations, you can:
+  - Click on an organization in the table to edit or delete it.
+  - Use the search bar to find a specific organization by name, filter query, or Datadog site, and then select the organization to edit or delete it.
+  - [View metrics](#view-metrics-for-the-component-or-specific-organizations) for an organization.
+
+**Note**: If you don't set up routing to multiple Datadog organizations, logs are routed to the default Datadog organization, which is the organization that is tied to the API key when you install the Worker.
+
+###### Add an organization
+
+1. Enter a name for the organization.
+	- **Note**: The name does not have to correspond to the actual name of the Datadog organization.
+1. Define a filter query. Only logs that match the specified filter query are sent to the organization. See [Observability Pipelines Search Syntax][3] for more information on writing filter queries.
+1. Select the Datadog organization's site.
+1. Enter the identifier for the API key for that Datadog organization.
+	- **Note**: Only enter the identifier for the API key. Do **not** enter the actual API key.
+1. Click **Save**.
+
+##### Buffering options
+
+Toggle the switch to enable **Buffering Options**.<br>**Note**: Buffering options is in Preview. Contact your account manager to request access.
+- If left disabled, the maximum size for buffering is 500 events.
+- If enabled:
+	1. Select the buffer type you want to set (**Memory** or **Disk**).
+	1. Enter the buffer size and select the unit.
 
 ### Set secrets
 
@@ -40,6 +70,32 @@ There are no secret identifiers for this destination.
 {{% /tab %}}
 {{< /tabs >}}
 
+## View metrics for the component or specific organizations
+
+You can view metrics at the component level or organization level.
+
+### Component-level metrics
+
+To view metrics for the overall Datadog Logs destination:
+
+1. Navigate to [Observability Pipelines][1].
+1. Select your pipeline.
+1. Click the cog on the **Datadog Logs** destination and select **View details**.
+
+**Note**: The **Data dropped (intentional)** metric shows logs that didn't match any of the organizations' filters.
+
+### Organization-level metrics
+
+To view metrics for a specific Datadog organization:
+
+1. Navigate to [Observability Pipelines][1].
+1. Select your pipeline.
+1. Click the **Datadog Logs** destination so the organizations show up.
+1. Click the organization you want to see metrics for.
+1. Click **View Health Metrics**.
+
+Alternatively, you can click on **Review Configured Organizations** in the Datadog Logs destination, and click the graph icon in the **Metrics** column for the organization you are interested in.
+
 ## How the destination works
 
 ### Event batching
@@ -81,3 +137,4 @@ To send logs from Observability Pipelines to Datadog using Azure Private Link, s
 
 [1]: https://app.datadoghq.com/observability-pipelines
 [2]: /observability_pipelines/destinations/#event-batching
+[3]: /observability_pipelines/search_syntax/logs/
\ No newline at end of file