Skip to content
Open
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions content/en/cloud_cost_management/reporting/explorer.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,30 @@

**Note:** When querying costs across multiple providers, resource-level tags are not available. To access resource-specific tags, filter to a single provider in your query.

## Cost Change Summary Side Panel

Check warning on line 49 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings

'Cost Change Summary Side Panel' should use sentence-style capitalization.

The Cost Change Summary panel highlights what and who may be driving cost changes for the current period vs the prior period.

{{< img src="cloud_cost/reporting/cost-change-sidepanel.png" alt="The Cost Change Summary panel highlights what and who may be driving cost changes for the current period vs the prior period." style="width:100%;" >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what do you think of using this image instead?
cost-change-side-panel


At the top, you’ll see Total cost for the current period and the dollar and percent cost change versus the prior period.

Check failure on line 55 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.quotes

Use straight quotes instead of smart quotes.

### Change details and Investigate Further

- **Instantly Identify Cost Anomalies:** Unexpected deviations in cost, calculated against historical data, are automatically highlighted in red, allowing you to quickly focus your investigation on critical trends.

Check warning on line 59 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.words

Use '' instead of 'quickly'.

- **Analyze Change Drivers:** Easily determine the cause of a cost change—whether it was driven by a change in **usage** (the count of resources) or a change in **unit price** (the cost per resource). For example, in the screenshot below, we can see the change in spend is driven by a shift in unit price rather than usage—the resource count stays flat while cost per resource rises and falls, causing the overall cost change.

Check warning on line 61 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.pronouns

Avoid first-person pronouns such as 'we'.
Copy link
Contributor

@rtrieu rtrieu Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Analyze Change Drivers:** Easily determine the cause of a cost changewhether it was driven by a change in **usage** (the count of resources) or a change in **unit price** (the cost per resource). For example, in the screenshot below, we can see the change in spend is driven by a shift in unit price rather than usagethe resource count stays flat while cost per resource rises and falls, causing the overall cost change.
- **Analyze Change Drivers**---Easily determine the cause of a cost change - whether it was driven by a change in **usage** (the count of resources) or a change in **unit price** (the cost per resource). For example, in the screenshot below, the change in spend is driven by a shift in unit price rather than usage---the resource count stays flat while cost per resource rises and falls, causing the overall cost change.


{{< img src="cloud_cost/reporting/cloud-cost-spend-summary.png" alt="The change in spend is driven by a shift in unit price rather than usage—the resource count stays flat while cost per resource rises and falls, causing the overall cost change" style="width:100%;" >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's remove this screenshot since the overview one i suggested captures it all

Copy link
Contributor

@buraizu buraizu Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @rtrieu, just wanted to flag that the preceding paragraph references the screenshot below. Do you still think the image should be removed?


### Take Action

Check warning on line 65 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings

'Take Action' should use sentence-style capitalization.

- **Associated Team(s)**: The responsible team(s) for the cost change are automatically identified, inferred from resource tags (e.g., `team:shopist`). To gain full context for the change, follow up with the listed teams (e.g., Shopist, Platform, Cloud-Networks). For a streamlined investigation, you can **send a Notebook** containing the full context directly to the team with a single click. Use the Notebook to capture context, annotate findings, and share the investigation thread.

Check warning on line 67 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.abbreviations_latin

Use 'for example' instead of abbreviations like 'e.g.,'.

Check warning on line 67 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.abbreviations_latin

Use 'for example' instead of abbreviations like 'e.g.,'.

- **Associated Tags**: This list shows all relevant tags contributing to the current cost line item. A crucial feature is the ability to \[Refine your search\] by clicking on a tag value (like `account:demo` or a specific `aws_account`). This acts as a quick filter to narrow down the entire Cloud Cost Explorer to only the resources with that specific tag.

Check warning on line 69 in content/en/cloud_cost_management/reporting/explorer.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.words

Use '' instead of 'quick'.

- Create a Monitor to be alerted the next time a similar change occurs. Learn more about [Cloud Cost Monitors](https://docs.datadoghq.com/monitors/types/cloud_cost/).

## Refine your results

Click **Refine Results** to access advanced filtering options that help you focus on specific cost patterns.
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading