In Preview
The Cost Anomalies dedicated page is in Preview. To request access, complete the form.
Request AccessOverview
Cloud Cost Monitors help you proactively identify cost changes, and understand if you’re projected to go over budget, so you can investigate the cause.
In order to configure Cloud Cost monitors, you need to have Cloud Cost Management set up.
Cloud Cost monitors are evaluated with a 48 hour delayed evaluation window, because Cloud Cost data is not guaranteed to be available until 48 hours after usage. For example, a monitor with a lookback of 7 days being evaluated on January 15 examines cost data from January 6 through January 13.
Monitor creation
To create a Cloud Cost monitor in Datadog, you can set up via Terraform, from the main navigation, Monitors –> New Monitor –> Cloud Cost, or from the Cloud Cost Explorer.
Optionally, click the + Create Monitor button in the cost Explorer side panel.
Select a cost monitor type
You can select from the following monitor types.
| Cost Type | Description | Usage Examples |
|---|
| Cost Changes | Compare costs on a daily, weekly or monthly basis | Alert when the difference between today’s cost and the week before is over 5%. |
| Cost Type | Description | Usage Examples |
|---|
| Cost Threshold | Set alerts on total costs exceeding a threshold in a day | Set alerts when today’s total cost exceeds $10,000. |
| Cost Type | Description | Usage Examples |
|---|
| Cost Forecast | Set alerts based on forecasted costs exceeding a threshold by the end of the current month. | Alert daily if the forecasted cost for this month is projected to exceed $500. |
| Cost Type | Description | Usage Examples |
|---|
| Cost Anomalies | Detect anomalies by comparing current costs to historical data, using a defined lookback period. Incomplete days are excluded from analysis to ensure accuracy. Anomaly monitors require at least 1 month of cloud cost data to evaluate since historical data is required to train the algorithm. | Alert if 3 days from the past 30 days show significant cost anomalies compared to historical data. |
Specify which costs to track
Any cost type or metric reporting to Datadog is available for monitors. You can use custom metrics or observability metrics alongside a cost metric to monitor unit economics.
| Step | Required | Default | Example |
|---|
| Select the cost metric | Yes | aws.cost.amortized | azure.cost.actual |
Define the filter by | No | Everything | aws_product:s3 |
| Group by | No | Everything | aws_availability_zone |
| Add observability metric | No | system.cpu.user | aws.s3.all_requests |
Use the editor to define the cost types or exports.
For more information, see the Cloud Cost Management documentation.
Set alert conditions
If you are using the Cost Changes monitor type, you can trigger an alert when the cost increases or decreases more than the defined threshold. The threshold can be set to either a Percentage Change or set to Dollar Amount.
If you are using the Percentage Change, you can filter out changes that are below a certain dollar threshold. For example, the monitor alerts when there is a cost change above 5% for any change that is above $500.
If you are using the Cost Threshold monitor type, you can trigger an alert when the cloud cost is above, below, above or equal, or below or equal to a threshold.
If you are using the Cost Forecast monitor type, you can trigger an alert when the cloud cost is above, below, above or equal, below or equal to, equal to, or not equal to a threshold.
If you are using the Cost Anomalies monitor type, you can trigger an alert if the observed cost deviates from historical data by being above, below, or above or below a threshold for any provider and service.
The agile anomaly algorithm is used with two bounds and monthly seasonality.
For detailed instructions on the Configure notifications and automations section, see the Notifications page.
Further Reading
Additional helpful documentation, links, and articles:
