E-MapReduce (EMR) tracks the cost and resource usage of your auto-scaled task nodes in the Auto Scaling Cost Analysis dashboard. Use the dashboard to evaluate how much auto scaling saves you and decide whether switching elastic nodes to preemptible instances would reduce costs further.
The dashboard covers only task node groups that contain pay-as-you-go or preemptible instances. Cost data reflects historical usage — not a projected estimate — and is updated once per day.
Prerequisites
Before you begin, make sure that:
-
The AliyunEMRManagedCostRole role is assigned to EMR. Assign it with an Alibaba Cloud account or a RAM user when you use the cost analysis feature for the first time.
-
The cluster has at least one task node group that contains pay-as-you-go or preemptible instances. For details, see Add auto scaling rules.
Usage notes
-
Cost data is updated at 06:00 the next day, so the dashboard always shows data with a one-day delay.
-
Costs shown for individual node groups are estimated values. The actual charges in your final bills prevail.
-
Node groups that use saving plans are not supported.
View the Auto Scaling Cost Analysis dashboard
-
Log on to the EMR console. In the left-side navigation pane, click EMR on ECS.
-
In the top navigation bar, select the region where your cluster resides, and select a resource group.
-
On the EMR on ECS page, find the cluster and click its name in the Cluster ID/Name column.
-
Click the Auto Scaling tab, then click the Auto Scaling Cost Analysis subtab.
The dashboard displays the following parameters and metrics.
| Parameter or metric | Description |
|---|---|
| PretaxGrossAmount / PretaxAmount | The type of cost data to display. PretaxAmount (default) shows fees after discounts. PretaxGrossAmount shows fees calculated at list prices, before any discounts. For details, see Billing details. |
| NodeGroup | The task node group whose costs to display. Defaults to All, which aggregates all supported groups. Switch to a specific node group when you want to investigate a cost spike in one group or compare spending across groups. Only task node groups with pay-as-you-go or preemptible instances that have cost data are available. |
| Select Time | The time range of the displayed data. Defaults to the last 7 days. |
| Cost for yesterday | The cost of elastic resources in the cluster for the previous day, calculated the next morning. Because data is calculated the next day, the current week's data is unavailable on Monday, and the current month's data is unavailable on the first day of the month. |
| Cost for this week (calendar week) | The aggregated cost for the current calendar week. |
| Cost for this month (calendar month) | The aggregated cost for the current calendar month. |
| The day-over-day growth rate | The percentage change in cluster cost between the previous day and the day before it. Available only after cost data for two consecutive days has been collected. |
| Cost | The cost trend over the selected time range. |
| Cpu-All | The total number of CPU cores across all elastic nodes over time. Under normal conditions, this metric correlates with the cost trend. If changes in the total number of cores are inconsistent with the cost trend, the per-core unit cost is abnormal for that period. Check whether resources that are more expensive are used. |
| Cost of each nodeGroup | The cost breakdown by task node group. |
| Estimated cost savings if all nodes are spot instance | An estimate of how much you would save if all elastic nodes switched to preemptible instances. Use this figure to analyze whether changing the billing method of elastic nodes would reduce costs and optimize resource usage. |
FAQ
No data is displayed on the Auto Scaling Cost Analysis subtab. Why?
The AliyunEMRManagedCostRole role has not been assigned to EMR. After you assign the role, data appears at 06:00 the next day. The day-over-day growth rate requires two consecutive days of data and will not appear until the second day.
Why are the weekly or monthly totals lower than the costs in my actual bills?
The cost analysis feature only collects data from the point when the role was assigned. Costs incurred before the authorization are not included.