Container Cost Allocation
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Cloud Cost Management is not supported for this site.
Overview
Datadog Cloud Cost Management (CCM) automatically allocates EC2 compute cost in Kubernetes and ECS clusters to individual pods and tasks running in those clusters. Use cost metrics enriched with tags from pods, nodes, containers, and tasks to visualize container workload cost in the context of your entire cloud bill.
Prerequisites
- Set up and configure AWS Cloud Cost integration.
- (Optional) Enable AWS Split Cost Allocation for usage-based ECS allocation.
- At least one of the following must be running:
Cost allocation
Cost allocation divides EC2 compute costs in the Cost and Usage Report (CUR) into individual costs for each pod or task running on the instance. These divided costs are then enriched with tags from the nodes, pods, and tasks, which allows you to break down costs by any associated dimensions.
Kubernetes
For Kubernetes allocation, a Kubernetes node is joined with its associated EC2 instance costs. The node’s cluster name and all node tags are added to the entire EC2 compute cost for the node. This allows you to associate cluster-level dimensions with the cost of the instance, without considering the pods scheduled to the node.
Next, Datadog looks at all of the pods running on that node for the day. The cost of the node is allocated to the pod based on the resources it has used and the length of time it ran. This calculated cost is enriched with all of the pod’s tags.
Note: Only tags from pods and nodes are added to cost metrics. To include labels, enable labels as tags for nodes and pods.
ECS on EC2
For ECS allocation, Datadog determines which tasks ran on each EC2 instance used for ECS. If you enable AWS Split Cost Allocation, the metrics allocate ECS costs by usage instead of reservation, providing more granular detail.
Based on resources the task has used, Datadog assigns the appropriate portion of the instance’s compute cost to that task. The calculated cost is enriched with all of the task’s tags and all of the container tags (except container names) running in the task.
ECS on Fargate
ECS tasks that run on Fargate are already fully allocated in the CUR. CCM enriches that data by adding out-of-the-box tags and container tags to the AWS Fargate cost.
Everything else
Any cost other than EC2, computed for instances hosting Kubernetes pods or ECS tasks, is given the same value and tags as the source metric, aws.cost.amortized.
Understanding spend
Using the allocated_spend_type tag, you can visualize the spend category associated with your cost at the Kubernetes node, ECS host, or cluster level. Costs are allocated into three spend types:
- Usage: Cost of memory and cpu being used or reserved by workloads.
- Workload idle: Cost of memory and cpu that is being reserved and allocated but not used by workloads.
- Cluster idle: Cost of memory and cpu not reserved by workloads in a cluster.
Cost metrics
When the prerequisites are met, new AWS cost metrics automatically appear.
| AWS Cost Metric | Description |
|---|
aws.cost.amortized.shared.resources.allocated | EC2 costs allocated by the CPU & memory used by a pod or ECS task, using a 60:40 split for CPU & memory respectively.
Based on aws.cost.amortized |
aws.cost.net.amortized.shared.resources.allocated | Net EC2 costs allocated by CPU & memory used by a pod or ECS task, using a 60:40 split for CPU & memory respectively.
Based on aws.cost.net.amortized, if available |
aws.cost.amortized.mem.allocated | EC2 costs allocated by memory used by a pod or ECS task.
Based on aws.cost.amortized |
aws.cost.net.amortized.mem.allocated | Net EC2 costs allocated by memory used by a pod or ECS task
Based on aws.cost.net.amortized, if available |
aws.cost.amortized.cpu.allocated | EC2 costs allocated by CPU used by a pod or ECS task
Based on aws.cost.amortized |
aws.cost.net.amortized.cpu.allocated | Net EC2 costs allocated by CPU used by a pod or ECS task
Based on aws.cost.net.amortized, if available |
These new cost metrics include all of your AWS cloud costs. This allows you to continue visualizing all of your cloud costs at one time, with added visibility into pods and tasks running on EC2 instances.
For example, say you have the tag team on S3 buckets, RDS stores, and Kubernetes pods. You can use these new metrics to group costs by team, which includes costs for S3, RDS and compute expenses from tagged pods.
Datadog consolidates and applies additional tags from various sources to cost metrics. Conflicts are resolved by favoring higher-specificity tags such as pod tags over lower-specificity tags such as host tags. For example, a Kubernetes pod tagged service:datadog-agent running on a node tagged service:aws-node results in a final tag service:datadog-agent.
Containers
| Out-of-the-box tag | Description |
|---|
orchestrator:kubernetes | The orchestration platform associated with the item is Kubernetes. |
orchestrator:ecs | The orchestration platform associated with the item is ECS. |
allocated_spend_type:usage | Cost of resources used by a workload. Only available for .shared.resources.allocated metrics. |
allocated_spend_type:workload_idle | Cost of resources reserved and allocated by a workload, but not used. Only available for .shared.resources.allocated metrics. |
allocated_spend_type:cluster_idle | Cost of resources that are not reserved or used by any workload. Only available for .shared.resources.allocated metrics. |
allocated_spend_type:managed_service_fee | Cost of cloud provider managed service fees. Only available for .shared.resources.allocated metrics. |
allocated_resource:cpu | Cost of CPU resources. Only available for .shared.resources.allocated metrics. |
allocated_resource:memory | Cost of Memory resources. Only available for .shared.resources.allocated metrics. |
allocated_resource:managed_service_fee | Cost of cloud provider managed service fees. Only available for .shared.resources.allocated metrics. |
Kubernetes
In addition to Kubernetes pod and Kubernetes node tags, the following out-of-the-box tags are applied to cost metrics:
| Out-of-the-box tag | Description |
|---|
kube_cluster_name | The name of the Kubernetes cluster. |
is_kubernetes | All EC2 compute costs associated with running Kubernetes nodes. Only available for .cpu.allocated or .mem.allocated metrics. |
is_cluster_idle | The cost of unreserved CPU or memory on Kubernetes nodes. Only available for .cpu.allocated or .mem.allocated metrics. |
ECS
In addition to ECS task tags, the following out-of-the-box tags are applied to cost metrics. Note: most tags from ECS containers (excluding container_name) are applied.
| Out-of-the-box tag | Description |
|---|
ecs_cluster_name | The name of the ECS cluster. |
is_aws_ecs | All costs associated with running ECS. |
is_aws_ecs_on_ec2 | All EC2 compute costs associated with running ECS on EC2. |
is_aws_ecs_on_fargate | All costs associated with running ECS on Fargate. |
is_cluster_idle | The cost of unreserved CPU or memory on EC2 instances running ECS tasks. Only available for .cpu.allocated or .mem.allocated metrics. |
Further reading
Documentation, liens et articles supplémentaires utiles:
