From 44374e502765ba9c6c8d6ee508421c61483f5135 Mon Sep 17 00:00:00 2001 From: May Lee Date: Mon, 22 Dec 2025 16:49:56 -0500 Subject: [PATCH 1/5] add info --- .../destinations/datadog_logs.md | 34 ++++++++++++++++--- 1 file changed, 29 insertions(+), 5 deletions(-) diff --git a/content/en/observability_pipelines/destinations/datadog_logs.md b/content/en/observability_pipelines/destinations/datadog_logs.md index 41ea0046719..533206d007b 100644 --- a/content/en/observability_pipelines/destinations/datadog_logs.md +++ b/content/en/observability_pipelines/destinations/datadog_logs.md @@ -16,11 +16,35 @@ 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**.
**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. +#### Optional settings + +##### Route logs to multiple Datadog organizations + +If you want to route to multiple Datadog organizations, click **Route to Multiple 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. + - Click **Save** to add the organization. + +###### 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. +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**.
**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 From bdbc42a22af8af65aaf5335a818d846ef1213e75 Mon Sep 17 00:00:00 2001 From: May Lee Date: Tue, 23 Dec 2025 13:58:16 -0500 Subject: [PATCH 2/5] remove destination type restriction --- .../en/observability_pipelines/configuration/set_up_pipelines.md | 1 - 1 file changed, 1 deletion(-) 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/ From dae6d0e4a9dc921becd9c5fab9745c7d58a520d0 Mon Sep 17 00:00:00 2001 From: May Lee Date: Tue, 23 Dec 2025 14:54:25 -0500 Subject: [PATCH 3/5] add metrics info --- .../destinations/datadog_logs.md | 30 ++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git a/content/en/observability_pipelines/destinations/datadog_logs.md b/content/en/observability_pipelines/destinations/datadog_logs.md index 533206d007b..3342c3ccade 100644 --- a/content/en/observability_pipelines/destinations/datadog_logs.md +++ b/content/en/observability_pipelines/destinations/datadog_logs.md @@ -16,11 +16,15 @@ Set up the Datadog Logs destination and its environment variables when you [set ### Set up the destination +There are no required setup steps. + #### Optional settings ##### Route logs to multiple Datadog organizations -If you want to route to multiple Datadog organizations, click **Route to Multiple Organizations**. +You can route logs to multiple Datadog organizations. After you set up routing to multiple organization, you can view metrics for the destination component or specific organizations. See [View metrics for the component or specific organizations](#view-metrics-for-the-component-or-specific-organizations) for more information. + +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: @@ -28,6 +32,8 @@ If you want to route to multiple Datadog organizations, click **Route to Multipl - 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. - Click **Save** to add the 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. @@ -64,6 +70,28 @@ There are no secret identifiers for this destination. {{% /tab %}} {{< /tabs >}} +## View metrics for the component or specific organizations + +You can view metrics at both the organization level and the overall component level. + +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. + +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. + ## How the destination works ### Event batching From 50aaeb7fb8c98c5490823ee8afdaa633f714c3e2 Mon Sep 17 00:00:00 2001 From: May Lee Date: Tue, 23 Dec 2025 15:24:52 -0500 Subject: [PATCH 4/5] small edits --- .../destinations/datadog_logs.md | 26 +++++++++++-------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/content/en/observability_pipelines/destinations/datadog_logs.md b/content/en/observability_pipelines/destinations/datadog_logs.md index 3342c3ccade..7d9bd182b5b 100644 --- a/content/en/observability_pipelines/destinations/datadog_logs.md +++ b/content/en/observability_pipelines/destinations/datadog_logs.md @@ -22,7 +22,7 @@ There are no required setup steps. ##### Route logs to multiple Datadog organizations -You can route logs to multiple Datadog organizations. After you set up routing to multiple organization, you can view metrics for the destination component or specific organizations. See [View metrics for the component or specific organizations](#view-metrics-for-the-component-or-specific-organizations) for more information. +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. @@ -30,7 +30,7 @@ Click **Route to Multiple Organizations** to set up routing to multiple Datadog - 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. - - Click **Save** to add the organization. + - [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. @@ -72,25 +72,29 @@ There are no secret identifiers for this destination. ## View metrics for the component or specific organizations -You can view metrics at both the organization level and the overall component level. +You can view metrics at the component level or organization level. -To view metrics for a specific Datadog organization: +### 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 **Datadog Logs** destination so the organizations show up. -1. Click the organization you want to see metrics for. -1. Click **View Health Metrics**. +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. -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. +### Organization-level metrics -To view metrics for the overall Datadog Logs destination: +To view metrics for a specific Datadog organization: 1. Navigate to [Observability Pipelines][1]. 1. Select your pipeline. -1. Click the cog on the **Datadog Logs** destination and select **View details**. +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**. -**Note**: The **Data dropped (intentional)** metric shows logs that didn't match any of the organizations' filters. +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 From 91d948010de125e90b6aecf7ec19dffa01dcce83 Mon Sep 17 00:00:00 2001 From: May Lee Date: Tue, 23 Dec 2025 15:33:27 -0500 Subject: [PATCH 5/5] add search syntax link --- .../en/observability_pipelines/destinations/datadog_logs.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/observability_pipelines/destinations/datadog_logs.md b/content/en/observability_pipelines/destinations/datadog_logs.md index 7d9bd182b5b..744b1be4ec6 100644 --- a/content/en/observability_pipelines/destinations/datadog_logs.md +++ b/content/en/observability_pipelines/destinations/datadog_logs.md @@ -38,7 +38,7 @@ Click **Route to Multiple Organizations** to set up routing to multiple Datadog 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. +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. @@ -137,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