[CCT-1571] Add Customize anomaly detection section to CCM anomalies page#37754
Merged
Conversation
Documents the new custom anomaly detection (Configure Cost Anomalies) feature, currently in Preview, on the Cloud Cost Management anomalies page.
Contributor
Preview links (active after the
|
bianca-catarau
marked this pull request as ready for review
June 25, 2026 14:26
janine-c
approved these changes
Jun 25, 2026
janine-c
left a comment
Contributor
There was a problem hiding this comment.
Looks awesome, thanks for submitting! Just a couple minor suggestions that you're welcome to take or leave 🙂
|
|
||
| <div class="alert alert-danger">Custom anomaly detection is in Preview.</div> | ||
|
|
||
| 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. |
Contributor
There was a problem hiding this comment.
Suggested change
| 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 >}}. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. On the [Anomalies tab][1], click {{< ui >}}Configure{{< /ui >}}. | |
| 1. On the [{{< ui >}}Anomalies{{< /ui >}} tab][1], click {{< ui >}}Configure{{< /ui >}}. |
Contributor
There was a problem hiding this comment.
I don't see a Configure button. Do you need to have a specific permission to make it visible? If so, we should probably mention it 🙂 If it's just hidden behind a feature flag, ignore me.
Contributor
Author
Contributor
Contributor
Author
There was a problem hiding this comment.
Yes, I just checked and you don't have that permission so that's why.
| - **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. |
Contributor
There was a problem hiding this comment.
Suggested change
| 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 >}}. |
Address review feedback: reword detection sentence, wrap Anomalies tab in ui shortcode, and use Save shortcode in the revert instructions. Co-authored-by: Cursor <cursoragent@cursor.com>
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 <cursoragent@cursor.com>
xaviersicotte
self-requested a review
June 30, 2026 09:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


What does this PR do? What is the motivation?
CCT-1571
Documents the new custom anomaly detection capability (the Configure Cost Anomalies experience) on the Cloud Cost Management Anomalies page. The feature lets users with the
cloud_cost_management_writepermission customize, per cloud provider, the detection dimension, minimum daily cost threshold, and breakdown tags used to detect cost anomalies.This adds a new
## Customize anomaly detectionsection tocontent/en/cloud_cost_management/cost_changes/anomalies.md. The feature is currently in Preview, flagged using the existingalert alert-dangerPreview convention used elsewhere in the CCM docs.Additional notes
Preview link (active after the build_preview check completes): https://docs-staging.datadoghq.com/bianca.catarau/ccm-custom-anomalies-docs/cloud_cost_management/cost_changes/anomalies/