Cost reports enable you to easily identify expensive instances and compare them against utilization, type, elements, and tags. These multi-dimensional reports also break down information like total versus individual instance costs and even how much each instance state (Reserved, On-Demand) costs. Custom tagging is another easy way to group your instances.
Cost Reports are generated once per week. It may take up to 7 days before your first report is available.
Estimated Cost (AWS Integration Only)
If you just have an AWS integration in Metricly, the Estimated Cost report is available. Instance costs are estimated based on current list prices and simple assumptions to fill in missing information. For a more accurate view including reservations, data transfer costs, iops guarantees and other account specific charges, you can add an AWS Cost integration that allows Metricly to use your actual billing files from AWS.
Estimated Cost reports use 7 days of metric results and the current list prices to estimate element instance costs for all instances monitored by Metricly. Estimated Reports do not include data transfer costs and assumes all instances are on-demand.
Full Cost (AWS+AWS Cost Integration)
If you have both an AWS and AWS Cost integration, the Full Cost report is available and based on your billing files. The Full Cost report reads 7 days of billing data associated with the instances monitored by Metricly.
Costs are aggregated, simplified, and reduced to the following categories element:
|Hourly Instance Fees||On-Demand Instance||Hourly fee for an on-demand instance|
|Spot Instance||Hourly fee for a spot instance|
|Reserved Instance||Hourly fees for partial upfront or no-upfront reserved instances|
|Amortized Upfront Reservation Fee||Amortized upfront fees for partial upfront or all-upfront instances **|
|Dedicated Instance||Hourly fee for a dedicated instance|
|Instance EBS Optimized Charge||Hourly incremental fee for EBS optimized instances (applies to certain instance types)|
|Instance Dedicated Charge||Hourly incremental fee for dedicated host|
|Data Transfer Costs*||Data In – InterZone||Costs for data transfer to/from another AWS service in another availability zone or peered VPC in the same region|
|Data In – InterRegion||Costs for data transfer to/from another AWS service in another region|
|Data In – PublicIP||Costs for data transfer to/from another AWS service via a public or elastic IP address|
|Data In – Internet||Costs for data transfer to/from the instance from/to the internet|
|Data In – CloudFront||Costs for data transfer to/from the instance via CloudFront|
|Other||Other data transfer costs (e.g., Direct Connect)|
*All of the data transfer costs are separated into Data In and Data Out categories
**Actual upfront reservation fees are used where data for the original reservation is available in the S3 bucket containing billing data. If the original reservation cannot be found then the amortized upfront reservation fees are estimated using the current reservation list prices, the instance attributes and by assuming it is a one year reservation.
This section outlines all of the available report views.
Total Cost Pareto
This graph shows the total costs incurred for all the instances monitored by Metricly (or the subset if a filter has been applied). The line is plotted against the right-hand axis and shows a cumulative percent contribution of each of the bars. Use this view to see the total cost of your environment and total contributions by category.
All cost categories are shown in this chart even if you have incurred no costs of a particular type. For the Estimated Cost report, you may see just one bar.
Cost by Element
This graph breaks down how much each element is costing by category. The line is plotted against the right-hand axis and shows the utilization of each element. With this view, you can compare the relative cost of elements versus their level of utilization. This chart only shows the cost categories that you have actually incurred.
Cost by Instance Type
This graph breaks down how much each instance size is costing by instance type. The line is plotted against the right-hand axis and shows the maximum of the utilizations of all elements per instance type. This chart only shows the cost categories that you have actually incurred.
Cost vs. Utilization Scatter
This graph displays a scatter plot of the cost versus utilization for your instances. Hover over a point on the graph to view the instance name, utilization, instance type, tag, and cost. You can zoom into an area of the chart by clicking and dragging the mouse.
This view lets you compare the relative cost and utilization of your instances amongst their peers: elements to the bottom-right have relatively high utilization and lower cost compared with elements in the top-left corner which have lower utilization and higher costs. Elements are given different markers based on their tag. To use this view you need to have tags on your instance elements; these can be source tags (set in AWS) or tags you have created in Metricly.
Cost by Tag
This graph lets you group the costs by any custom tag. To use this view you need to have tags on your instance elements. These can be source tags (set in AWS) or tags you have created in Metricly. For example, if combinations of your instances represent different applications you could create a tag called “application” in each instances and set the value accordingly. In this view, you could select the “application” tag to aggregate the costs according to the grouping you have specified. Other examples could include grouping by department or by environment. This chart only shows the cost categories that you have actually incurred.
EC2 vs. RDS vs. S3
Cost Reports across instances have largely the same experience, but this section covers the main differences between cost reporting for each.
- Active Hours
- CPU Utilization %
- Memory Utilization
- Disk I/O %
- Disk Space Used %
- Network I/O %
- EC2 elements without a Metricly agent / Windows agent display only two utilization measures: Active Hours and CPU Utilization %.
- EC2 elements with a Metricly agent installed have the following additional utilization metrics available: Memory Utilization %, Disk I/O %, and Disk Space Used %.
- EC2 elements with a Windows agent installed have the Network I/O % metric available.
If you have a mix of elements with and without a Metricly agent, you will see gaps in the utilization figures where values are not available.
- Active Hours
- CPU Utilization
- Disk Space Used %
- IOPS Utilization %
- Put Requests
- Get Requests
- Number of Objects
- Bucket Size (bytes)