From 0bd14d70ac1ccb8a84757ffdc59d4d3572ec0769 Mon Sep 17 00:00:00 2001 From: "bianca.catarau" Date: Thu, 25 Jun 2026 15:08:31 +0200 Subject: [PATCH 1/6] Add Customize anomaly detection section to CCM anomalies page Documents the new custom anomaly detection (Configure Cost Anomalies) feature, currently in Preview, on the Cloud Cost Management anomalies page. --- .../cost_changes/anomalies.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/content/en/cloud_cost_management/cost_changes/anomalies.md b/content/en/cloud_cost_management/cost_changes/anomalies.md index a76f6319b0b..04149a36013 100644 --- a/content/en/cloud_cost_management/cost_changes/anomalies.md +++ b/content/en/cloud_cost_management/cost_changes/anomalies.md @@ -34,6 +34,24 @@ To distinguish between true anomalies and expected fluctuations, Datadog's algor - Focuses on engineering usage (excludes taxes, credits, refunds, and Reserved Instance fees) - Filters out low-impact anomalies to reduce noise +## Customize anomaly detection + +
Custom anomaly detection is in Preview.
+ +By default, Datadog automatically detects cost anomalies for each cloud provider. If you have the `cloud_cost_management_write` permission, you can customize how anomalies are detected per provider to better match your organization's cost structure. Custom anomaly detection is available for AWS, Azure, Google Cloud, Datadog, and Oracle Cloud. + +To customize anomaly detection: + +1. On the [Anomalies tab][1], click {{< ui >}}Configure{{< /ui >}}. +1. In the {{< ui >}}Configure Cost Anomalies{{< /ui >}} panel, select a provider. A checkmark indicates that the provider uses custom settings, and an empty circle indicates that it uses Datadog's default settings. +1. Adjust the following settings for the selected provider: + - **Detection dimension**: The dimension that Datadog detects cost anomalies on (for example, service or charge description). This setting is required. + - **Minimum daily cost**: The minimum daily cost a change must reach before it is flagged as an anomaly (100 by default, with a minimum of 5, in your organization's currency). Increase this value to reduce noise from low-cost changes. + - **Breakdown tags**: Up to five additional tags used to break down detected anomalies, helping [Watchdog Explains][2] identify what's driving each anomaly. A set of default tags is always included and cannot be removed. +1. Click {{< ui >}}Save{{< /ui >}}. Changes apply to anomalies detected going forward. + +To return a provider to Datadog's default settings, select the provider, click {{< ui >}}Revert{{< /ui >}}, and then save. + ## View cost anomalies On the [Anomalies tab of the Cloud Cost page in Datadog][1], you can view and filter anomalies: From f81387d34a6649b3c0ef7553cae3bb22df9b868b Mon Sep 17 00:00:00 2001 From: "bianca.catarau" Date: Thu, 25 Jun 2026 15:42:48 +0200 Subject: [PATCH 2/6] Re-trigger preview build From 5717e725da02df7b43128202db40bc2856aec8a5 Mon Sep 17 00:00:00 2001 From: "bianca.catarau" Date: Thu, 25 Jun 2026 16:21:47 +0200 Subject: [PATCH 3/6] Simplify minimum daily cost wording to just the minimum threshold --- content/en/cloud_cost_management/cost_changes/anomalies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/cloud_cost_management/cost_changes/anomalies.md b/content/en/cloud_cost_management/cost_changes/anomalies.md index 04149a36013..446b499516e 100644 --- a/content/en/cloud_cost_management/cost_changes/anomalies.md +++ b/content/en/cloud_cost_management/cost_changes/anomalies.md @@ -46,7 +46,7 @@ To customize anomaly detection: 1. In the {{< ui >}}Configure Cost Anomalies{{< /ui >}} panel, select a provider. A checkmark indicates that the provider uses custom settings, and an empty circle indicates that it uses Datadog's default settings. 1. Adjust the following settings for the selected provider: - **Detection dimension**: The dimension that Datadog detects cost anomalies on (for example, service or charge description). This setting is required. - - **Minimum daily cost**: The minimum daily cost a change must reach before it is flagged as an anomaly (100 by default, with a minimum of 5, in your organization's currency). Increase this value to reduce noise from low-cost changes. + - **Minimum daily cost**: The minimum daily cost a change must reach before it is flagged as an anomaly (at least 5, in your organization's currency). Increase this value to reduce noise from low-cost changes. - **Breakdown tags**: Up to five additional tags used to break down detected anomalies, helping [Watchdog Explains][2] identify what's driving each anomaly. A set of default tags is always included and cannot be removed. 1. Click {{< ui >}}Save{{< /ui >}}. Changes apply to anomalies detected going forward. From b70abe6a26145a589bfb49f64c8dbef27801e03d Mon Sep 17 00:00:00 2001 From: Bianca Catarau Date: Fri, 26 Jun 2026 15:22:49 +0200 Subject: [PATCH 4/6] Apply reviewer suggestions to anomalies docs Address review feedback: reword detection sentence, wrap Anomalies tab in ui shortcode, and use Save shortcode in the revert instructions. Co-authored-by: Cursor --- content/en/cloud_cost_management/cost_changes/anomalies.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/cloud_cost_management/cost_changes/anomalies.md b/content/en/cloud_cost_management/cost_changes/anomalies.md index 446b499516e..9c0ce1117af 100644 --- a/content/en/cloud_cost_management/cost_changes/anomalies.md +++ b/content/en/cloud_cost_management/cost_changes/anomalies.md @@ -38,11 +38,11 @@ To distinguish between true anomalies and expected fluctuations, Datadog's algor
Custom anomaly detection is in Preview.
-By default, Datadog automatically detects cost anomalies for each cloud provider. If you have the `cloud_cost_management_write` permission, you can customize how anomalies are detected per provider to better match your organization's cost structure. Custom anomaly detection is available for AWS, Azure, Google Cloud, Datadog, and Oracle Cloud. +By default, Datadog automatically detects cost anomalies for each cloud provider. If you have the `cloud_cost_management_write` permission, you can customize how Datadog detects anomalies per provider to better match your organization's cost structure. Custom anomaly detection is available for AWS, Azure, Google Cloud, Datadog, and Oracle Cloud. To customize anomaly detection: -1. On the [Anomalies tab][1], click {{< ui >}}Configure{{< /ui >}}. +1. On the [{{< ui >}}Anomalies{{< /ui >}} tab][1], click {{< ui >}}Configure{{< /ui >}}. 1. In the {{< ui >}}Configure Cost Anomalies{{< /ui >}} panel, select a provider. A checkmark indicates that the provider uses custom settings, and an empty circle indicates that it uses Datadog's default settings. 1. Adjust the following settings for the selected provider: - **Detection dimension**: The dimension that Datadog detects cost anomalies on (for example, service or charge description). This setting is required. @@ -50,7 +50,7 @@ To customize anomaly detection: - **Breakdown tags**: Up to five additional tags used to break down detected anomalies, helping [Watchdog Explains][2] identify what's driving each anomaly. A set of default tags is always included and cannot be removed. 1. Click {{< ui >}}Save{{< /ui >}}. Changes apply to anomalies detected going forward. -To return a provider to Datadog's default settings, select the provider, click {{< ui >}}Revert{{< /ui >}}, and then save. +To return a provider to Datadog's default settings, select the provider, click {{< ui >}}Revert{{< /ui >}}, and then click {{< ui >}}Save{{< /ui >}}. ## View cost anomalies From f40e22c15f210f731372a372a8f9d6f5ede8a24e Mon Sep 17 00:00:00 2001 From: Bianca Catarau Date: Tue, 30 Jun 2026 10:56:39 +0200 Subject: [PATCH 5/6] Link breakdown tags to the Cloud Cost skill in Bits Chat Per review feedback, point the breakdown tags reference to the Cloud Cost skill in Bits Chat (the FinOps agent) instead of Watchdog Explains, since the configured tags feed the agent's anomaly investigation context. Co-authored-by: Cursor --- content/en/cloud_cost_management/cost_changes/anomalies.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/cloud_cost_management/cost_changes/anomalies.md b/content/en/cloud_cost_management/cost_changes/anomalies.md index 9c0ce1117af..8d72284dcce 100644 --- a/content/en/cloud_cost_management/cost_changes/anomalies.md +++ b/content/en/cloud_cost_management/cost_changes/anomalies.md @@ -47,7 +47,7 @@ To customize anomaly detection: 1. Adjust the following settings for the selected provider: - **Detection dimension**: The dimension that Datadog detects cost anomalies on (for example, service or charge description). This setting is required. - **Minimum daily cost**: The minimum daily cost a change must reach before it is flagged as an anomaly (at least 5, in your organization's currency). Increase this value to reduce noise from low-cost changes. - - **Breakdown tags**: Up to five additional tags used to break down detected anomalies, helping [Watchdog Explains][2] identify what's driving each anomaly. A set of default tags is always included and cannot be removed. + - **Breakdown tags**: Up to five additional tags used to break down detected anomalies, helping the [Cloud Cost skill in Bits Chat][5] identify what's driving each anomaly. A set of default tags is always included and cannot be removed. 1. Click {{< ui >}}Save{{< /ui >}}. Changes apply to anomalies detected going forward. To return a provider to Datadog's default settings, select the provider, click {{< ui >}}Revert{{< /ui >}}, and then click {{< ui >}}Save{{< /ui >}}. @@ -133,3 +133,4 @@ For more help, contact [Datadog Support][4]. [2]: /dashboards/graph_insights/watchdog_explains [3]: /cloud_cost_management/setup/ [4]: /help/ +[5]: /cloud_cost_management/cloud_cost_skill/ From 1c901bd389fb525f6c3a0ada6f25b6a1eca64430 Mon Sep 17 00:00:00 2001 From: Bianca Catarau Date: Fri, 3 Jul 2026 10:37:47 +0200 Subject: [PATCH 6/6] Remove "to help improve the algorithm" from anomaly resolution step Co-authored-by: Cursor --- content/en/cloud_cost_management/cost_changes/anomalies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/cloud_cost_management/cost_changes/anomalies.md b/content/en/cloud_cost_management/cost_changes/anomalies.md index 8d72284dcce..8f9ea2313cc 100644 --- a/content/en/cloud_cost_management/cost_changes/anomalies.md +++ b/content/en/cloud_cost_management/cost_changes/anomalies.md @@ -105,7 +105,7 @@ As you investigate anomalies, you may find some that are not significant, were a To resolve an anomaly: 1. Click {{< ui >}}Resolve Anomaly{{< /ui >}} to open the resolution popup. -1. Select one of the following resolutions to help improve the algorithm: +1. Select one of the following resolutions: - {{< ui >}}The anomaly amount was too small{{< /ui >}} - {{< ui >}}This is an unexpected increase{{< /ui >}} - {{< ui >}}This is an expected increase{{< /ui >}}