DOCS-8111 #32793
Open
DOCS-8111 #32793
Conversation
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
Contributor
Preview links (active after the
|
rtrieu
requested changes
Nov 12, 2025
Contributor
rtrieu
left a comment
rtrieu
left a comment
There was a problem hiding this comment.
hi @tony-ruschioni great work highlighting the powerful functionalities in this side panel! i made many suggestions to comply with our style guide, introduce the side panel more, and make the content a bit more action-oriented. let me know if you have any questions about my feedback or disagree with any of it. happy to chat through it!
|
|
||
| - **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. | ||
|
|
||
| - **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. |
Contributor
There was a problem hiding this comment.
Suggested 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, 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. | |
| - **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. |
|
|
||
| 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%;" >}} |
Contributor
There was a problem hiding this comment.
what do you think of using this image instead?
|
|
||
| - **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. | ||
|
|
||
| {{< 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%;" >}} |
Contributor
There was a problem hiding this comment.
let's remove this screenshot since the overview one i suggested captures it all
Contributor
There was a problem hiding this comment.
Hi @rtrieu, just wanted to flag that the preceding paragraph references the screenshot below. Do you still think the image should be removed?
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.
Add Cloud Costs Explorer Documentation
Updated existing doc page to include more information on the side panel.
What does this PR do? What is the motivation?
DOCS-8111
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes