[DOCS-11489] CCM new data source

[rtrieu]

What does this PR do? What is the motivation?

• Reorders a few steps based on updated UI
• Updated screenshots
• Adds info about data source limitations

Merge instructions

Merge readiness:

• Ready for merge

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

[github-actions]

📝 Documentation Team Review Required

This 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.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/rtrieu/docs-11489-ccm-new-data-source/cloud_cost_management/custom_allocation_rules

[helenmtang]

Suggested change

	- Create suballocations by [partitioning](#step-4---optional-apply-a-partition) the allocation rule: **environment** (`env`).
	- Create suballocations by [partitioning](#step-4---optional-apply-a-partition) the allocation rule. To do this, first apply another group by to the metric. In Network, do this by filling out the `View servers as` section: **Gateway ID** (`gateway_id`). This groups the metric by gateway_id. Then, select `server_gateway_id` in the **Partition source costs by** section.

[helenmtang]

Does this make sense? Should we add another sentence "Note: if you do not define a partition, the allocation rule will consider all group by tags as your destination tags, and split source costs across all destinations."

[rtrieu]

This part is a little confusing - is the filter under Define the source or Choose split method?

[helenmtang]

Specific to the Dynamic by metric, the filter, partition, and destination sections are all selected in the query editor (i'll send a screenshot to yu on slack!)

[helenmtang]

Specific to the Dynamic by metric, the filter, partition, and destination sections are all selected in the query editor (i'll send a screenshot to yu on slack!)

[helenmtang]

Suggested change

	- **Proportional by spend**: You can add filters to narrow the scope of your allocation. For example, filter by `aws_product:ec2` to create an allocation that only applies to EC2 costs, then proportionally distribute those costs based on each team's EC2 spend.
	For example, let's take a **proportional by spend** allocation rule. Say you're allocating shared costs to the team tag. Filter by `aws_product:ec2` to create an allocation that proportionally distributes shared costs costs based on each team's EC2 spend.

[helenmtang]

what do you think about making this a "general" example? Since filters apply to multiple allocation rule types.

[helenmtang]

Suggested change

	1. Select the destinations you want to allocate costs to, such as `team`, `department`, or `service`, that receive the allocated costs.
	1. Select the destinations you want to allocate costs to, such as `team`, `department`, or `service`.

[helenmtang]

Suggested change

	You can also specify how cost proportions should be partitioned to ensure segment-specific allocations. For example, if you partition your costs by environment using tags like `staging` and `production`, the proportions are calculated separately for each environment. This ensures allocations are based on the specific proportions within each partition.
	You can also specify how the cost allocation rule should be partitioned to create multiple suballocations. For example, if you partition your costs by the `environment` tag, the allocation rule is calculated separately for each environment.

[helenmtang]

Suggested change

	For example, the Network query `sum:network.bytes_written[server_gateway_id:nat-*] by client_service and server_gateway_id` (shown below) tracks the total traffic volume through NAT gateways by service. The relative values are then used to determine what proportion of total NAT gateway costs should be allocated to each service.
	For example, the Network query `sum:network.bytes_written[server_gateway_id:nat-*] by client_service and server_gateway_id` (shown below) tracks the total traffic volume through NAT gateways by service. The relative traffic volume per `client_service` and `server_gateway_id` is then used to determine what proportion of total NAT gateway costs should be allocated to each destination.

[helenmtang]

Suggested change

	Before creating this type of rule, be aware:
	Before creating this type of rule, please note:

[helenmtang]

Suggested change

- **Data sources support** - The dynamic by metric allocation method only supports specific data sources, listed in the dropdown below.

[helenmtang]

Suggested change

	- **Destination**: The primary group by becomes your destination tag. For example, group by `client_service` to split costs by service.
	- **Destination**: By default, the tag(s) you group by become the destination tag(s) for your allocation. For example, group by `client_service` to split costs by service.

[helenmtang]

Suggested change

	- **Partition**: Additional group bys become your partition. For example, add another group by for `gateway_id` to create suballocations by Gateway ID.
	- **Partition**: To define a partition, first group by the tag you wish to partition on. For example, add another group by for `gateway_id` to create suballocations by Gateway ID.

[helenmtang]

Suggested change

	- In section 3, **"Choose the destination(s) to split costs across"**, specify which group by tag is your destination and which will be your partition.
	- In section 3, **"Choose the destination(s) to split costs across"**, specify which group by tag is your partition tag. All group by tags are destination tags by default.

[helenmtang]

let me know if these changes make sense!

[helenmtang]

Suggested change

- **Dynamic by metric**: You can filter your metric query to focus on specific data. For example, add `environment:production` to your metric query so the allocation is based only on production environment usage data.

[helenmtang]

what do you think about making this a "general" example? Since filters apply to multiple allocation rule types.