Skip to content

Commit

Permalink
[CCA-233][CCA-281] Prepare docs for AWS network cost allocation GA (#…
Browse files Browse the repository at this point in the history
…25301)

Co-authored-by: buraizu <[email protected]>
  • Loading branch information
mpavlov and buraizu authored Oct 22, 2024
1 parent 68b97da commit 4f69e57
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 2 deletions.
4 changes: 3 additions & 1 deletion content/en/cloud_cost_management/aws.md
Original file line number Diff line number Diff line change
Expand Up @@ -255,11 +255,13 @@ The following out-of-the-box tags are available for filtering and grouping data:
| `aws_savings_plan_arn` | The ARN of the Savings Plan the item benefited from.|
| `aws_usage_type` | The usage details of the item (for example, BoxUsage:i3.8xlarge).|
| `aws_operation` | The operation associated with the item (for example, RunInstances).|
| `aws_region` | The region associated with the item (such as `us-east-1`).|
| `aws_region` | The region associated with the item (for example, us-east-1).|
| `aws_availability_zone` | The availability zone associated with the item.|
| `aws_resource_id` | The resource ID associated with the item.|
| `aws_instance_type` | The instance type of the item.|
| `aws_instance_family` | The instance family associated with your item (for example, Storage optimized).|
| `aws_datatransfer_type` | The type of data transfer associated with the item (for example, cross-zone or cross-region).|
| `aws_datatransfer_direction` | The direction of data transfer associated with the item (for example, in or out).|
| `is_aws_ec2_compute` | Whether the usage is related to EC2 compute.|
| `is_aws_ec2_compute_on_demand`| Whether the usage is on-demand.|
| `is_aws_ec2_compute_reservation`| Whether the usage is associated with a Reserved Instance.|
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ The following table presents the list of collected features and the minimal Agen
| Container Cost Allocation | 7.27.0 | 1.11.0 |
| GPU Container Cost Allocation | 7.54.0 | 7.54.0 |
| AWS Persistent Volume Allocation | 7.46.0 | 1.11.0 |
| Data Transfer Cost Allocation | 7.55.0 | 7.55.0 |
| Data Transfer Cost Allocation | 7.58.0 | 7.58.0 |

1. Configure the AWS Cloud Cost Management integration on the [Cloud Costs Setup page][101].
1. For Kubernetes support, install the [**Datadog Agent**][102] in a Kubernetes environment and ensure that you enable the [**Orchestrator Explorer**][103] in your Agent configuration.
Expand Down Expand Up @@ -141,12 +141,15 @@ ECS tasks that run on Fargate are already fully allocated [in the CUR][103]. CCM

For Kubernetes data transfer allocation, a Kubernetes node is joined with its associated data transfer costs from the [CUR][103]. The node's cluster name and all node tags are added to the entire data transfer cost for the node. This allows you to associate cluster-level dimensions with the cost of the data transfer, without considering the pods scheduled to the node.

[Network Performance Monitoring][105] must be enabled on all AWS hosts to allow accurate data transfer cost allocation. If some hosts do not have Network Performance Monitoring enabled, the data transfer costs for these hosts is not allocated and may appear as an `n/a` bucket depending on filter and group-by conditions.

Datadog supports data transfer cost allocation only through the [standard 6 workload resources][104]. If you use custom workload resources their data transfer costs may only be allocated down to the cluster level and not the node/namespace level.

[101]: /containers/kubernetes/tag/?tab=containerizedagent#node-labels-as-tags
[102]: /containers/kubernetes/tag/?tab=containerizedagent#pod-labels-as-tags
[103]: https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html
[104]: https://kubernetes.io/docs/concepts/workloads/
[105]: /network_monitoring/performance/setup

{{% /tab %}}
{{% tab "Azure" %}}
Expand Down

0 comments on commit 4f69e57

Please sign in to comment.