[DOCS-10759] CCM Commitment Programs #30007
Conversation
📝 Documentation Team Review RequiredThis pull request requires approval from the @DataDog/documentation team before it can be merged. Please ensure your changes follow our documentation guidelines and wait for a team member to review and approve your changes. |
Preview links (active after the
|
| - You can customize the table view by showing or hiding columns like Start Date, Multi-AZ, and NFU # (where applicable) to focus on the information most relevant to your needs. | ||
| - The table also highlights commitments that are expiring soon. | ||
|
|
||
| | Column | Description | |
There was a problem hiding this comment.
Note that the columns change depending on which product/program you're looking at. There are a number of columns common to both RDS and EC2, and some specific to each.
Common columns:
- ARN
- Payment Model
- Term
- Region
- Instance Type
- Start Date
- End Date
- Instance #
- NFU #
- Utilization
Columns specific to RDS RIs:
- DB Engine
- Multi-AZ
Columns specific to EC2 RIs:
- OS
- Offering Class
- AZ
| ### Targeting high on-demand spend | ||
|
|
||
| **Scenario** | ||
| Your cloud bill shows a spike in on-demand usage in a specific region. |
There was a problem hiding this comment.
Reserved Instances are best at covering usage that is consistent over time, rather than spiky (you may be wasting committed instances in the throughs) so you may want to reword that scenario slightly?
|
|
||
| The Commitments Explorer provides a detailed, interactive table of all your cloud commitment contracts, such as database reserved instances. It allows you to browse, search, filter, and sort your commitments by key attributes so you can track your inventory, monitor expiration dates, and identify opportunities to optimize usage and savings. | ||
|
|
||
| {{< img src="cloud_cost/planning/commitments-commitment-explorer-2.png" alt="Table showing AWS EC2 Reserved Instances commitments with the top section highlighting the columns button and five expired commitments, all of which had 100% utilization." style="width:100%;" >}} |
There was a problem hiding this comment.
Couple of comments on this screenshot:
- it highlights areas without really saying what these are? (as you did in the first screenshot of this page) As a reader I have to read on and do the linking myself between the image and the text
- it doesn't show any expiring-soon commitments (another disconnect with the text below: the text only mentions highlighting of the commitments expiring soon and not of the commitments already expired)
|
|
||
| - **Effective Savings Rate (ESR):** The percentage of cost savings achieved by your discount programs compared to on-demand prices, factoring in both utilized and underutilized commitments. | ||
|
|
||
| _Example: Coverage is 90% but ESR is 65%—you may have underutilized commitments dragging down your savings._ |
There was a problem hiding this comment.
-
The ESR is capped by the maximum discount rate achievable with the program you're looking at - so it won't get any higher than 64% for RDS (3yr, all upfront RI) or 62% for EC2 (3yr, all upfront, standard RI)
-
Since ESR is only about costs covered by Reserved Instances, I'm not sure it makes sense to mention coverage in the example?
|
|
||
| ## Overview | ||
|
|
||
| Cloud providers offer commitment-based discount programs (like {{< tooltip text="Reserved Instance (RI)" tooltip="A type of cloud commitment where you reserve capacity for a specific instance type and term, usually at a discounted rate." >}} and {{< tooltip text="Savings Plans" tooltip="Flexible cloud discount programs that provide lower prices in exchange for a commitment to a consistent amount of usage (measured in $/hour) over a term." >}}) to help you save on predictable usage. Datadog's Commitment Programs feature helps you monitor, optimize, and maximize the value of these discounts across your cloud environments. |
There was a problem hiding this comment.
A type of cloud commitment where you reserve capacity for a specific instance type and term, usually at a discounted rate.
In AWS, RIs do not usually come with capacity reservation (confusing, I know 😅)
What does this PR do? What is the motivation?
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