For the latest version of this help, see: https://help.apptio.com/en-us/cloudability/product/glossary-of-cost-dimensions-and-metrics.html
Cloudability's reporting tools allow you to slice and dice your cost and usage data so you can figure out exactly where your money is going. Divided into two sections, the dimensions and metrics that are available in your reports are identified below.
Account ID: The 12-digit AWS number used to identify a linked account. Used for cost analytics of consolidated billing accounts.
Account Name: The name associated with an AWS linked account. Used for cost analytics of consolidated billing accounts.
Availability Zone: A combination of the region and zone in which an instance exists or a usage charge occurs (e.g. us-east-1a).
Compute Usage Type: Based on the “UsageType” column from the AWS Detailed Billing Report (DBR), this field provides a curated and highly readable and filterable set of usage types for compute instances. Click here to learn more.
Date: The calendar date (e.g., YYYY-MM-DD).
Day: The numeric calendar day (e.g., 2014-1-15 => 15).
Day of Week: The weekday (e.g. Monday).
Engine: Use this identifier to easily report on the specific Storage Engine being used for storage tasks. Previously, this information was buried in several areas in the raw billing file. Now, it's available as an easy-to-use dimension. (e.g. Oracle, PostgreSQL, MySQL, etc.)
Instance Category: The instance category (e.g. General Purpose, Compute Optimized, Memory Optimized, etc.).
Instance Family: The instance category combined with the generation number (e.g. m3 vs. m1). For GCP, this is considered the machine type (e.g. standard, highmem, highcpu, etc.)
Instance Size: The size of an instance (e.g. m1.medium, t2.large, f1.micro, g1.small, etc.).
Instance Type: The full identifier of the instance running (e.g. m3.medium). Click here to learn more.
Invoice Date: The date/time your AWS invoice was issued. In AWS Cost Analytics, this value describes the last time the cost information was updated by AWS.
Invoice ID: The ID of your AWS invoice. For the current period where the cost is not invoiced yet, you will see "Estimated".
Item Description: Description of the type of usage for this line item. This description matches the “ItemDescription” column from the AWS Detailed Billing Report (DBR), including the average price of any usage that is based on a volume pricing tier. Click here to learn more.
Lease Type: A dimension created by Cloudability to show the different terms AWS offers for leasing resources: Spot, Reserved, and On-Demand.
Linked Account ID: For Consolidated Billing accounts, the 12-digit AWS identifier for the linked account.
Linked Account Name: The name associated with the linked account. This name can be changed in AWS account settings.
Month: The numeric calendar month (e.g. 2014-1-15 => 1).
Operating System: This dimension easily reports on the specific operating system being used for compute tasks. Previously, this information was buried in several areas in the raw billing file. Now, it's available as an easy-to-use dimension.
Operation: This dimension shows the specific action taken upon an asset. For example, if the networking is transferring data in or out of a compute instance. Paired with Resource, this helps customers understand both the source and actions that contribute to cost. (e.g. CPU, N1Standard, Dataproc, etc.)
Payer Account ID: The 12-digit AWS identifier of the payer account.
Payer Account Name: The name of an AWS account. This name can be changed in your AWS account settings.
Product Name: Long name of the AWS product (e.g. Amazon Elastic Compute Cloud). Click here to learn more.
Region: Region in which an instance exists or a usage charge occurred (e.g. US East, Europe-west1, etc.).
Resource ID: This is an identifier used by the vendor to distinguish the actual assets that are used. For example, this would be the instance ID of the VM, the name of the storage bucket, or an ID of the data volume.
Service Name: A new dimension created by Cloudability that standardizes product naming conventions for AWS, Azure, and GCP:
- AWS EBS becomes its own top-level product, as opposed to being considered EC2 in the DBR file.
- Unified data that was mixed across multiple products:
- AWS tracks Cloudwatch partially as a product and as EC2; this separates Cloudwatch into its own service
- AWS tracks Glacier partially as a product and in S3; this consolidates all Glacier and S3
- AWS has an import/export service, as well as a Snowball service; Service Name consolidates these
- In some cases, AWS and Azure's data show multiple products for the same services:
- AWS has multiple names for Support, this consolidates them all into a single "AWS Support" line item
- AWS has many administrative charges listed as top-level "products" like: Amazon Partner Network, re:Invent Tickets, etc. These are consolidated into a single "AWS Administrative" item
- Azure has Compute, Microsoft.Compute, and Virtual Machines; these are all the same and consolidated under Azure Compute.
- In some cases, AWS and GCP mirror each other fairly close in regards to the names of their services:
- GCP uses terms like Google Compute Engine and Google App Engine (AWS EC2), Google Cloud SQL, Google Cloud Firestore, and Google Cloud Bigtable (AWS RDS and DynamoDB).
- AWS billing files have inconsistent naming schemes for products, sometimes Amazon vs AWS; acronyms vs spelled out names. Service Name follows a single pattern of a prefix of "AWS" followed by the name that is seen in the AWS Console menu: EC2, S3, RDS, Kinesis, Lambda, etc. Similarly, Azure is the prefix for all Microsoft Azure services.
Seller: The official seller of services; this will normally be Amazon Web Services, Inc. Services purchased from AWS Marketplace list a different seller of record.
Transaction Type: A new Cloudability dimension, that shows whether particular costs were related to usage, a recurring monthly charge, one-time charge, credit, or taxes. For additional information, click here.
Usage Type: Specifies the operational details of the usage line item. The following example describes Amazon EC2 High-Memory Double ExtraLarge Instance box usage in the US West (Oregon) region. Example: USW1-BoxUsage:m2.2xlarge. Click here to learn more.
For GCP: This does not apply.
Usage Family: A new standardized dimension created by Cloudability to consolidate similar values of Usage Type into a single high-level family (e.g. Data Transfer, Storage, API Request).
Vendor: The vendor that provided the product.
Week: The numeric calendar week.
Year: The calendar year (e.g., 2014).
Zone: Availability Zone in which an instance exists or a usage charge occurred (e.g. 1a).
Cost (List): The cost without the effects of Reservation or Discounts.
Cost (Total): Total cost calculated by the unblended rate.
Cost (Total Blended): The total charges for the reporting period (calculated as a sum of blended cost).
Cost (Total Blended Before Taxes): The month-to-date charges, before any applicable taxes.
Cost (Amortized): This cost is calculated using the unblended rate, with any one-time, upfront reservation (RI) purchases spread out evenly across the duration of their term.
Cost (Adjusted): The cost after adjustment. *This is not available unless Custom Pricing is enabled.
Cost (Adjusted Amortized): This cost is calculated using the unblended rate, with any one-time, upfront reservation (RI) purchases spread out evenly across the duration of their term and includes any pricing adjustments. *This is not available unless Custom Pricing is enabled.
Cost Adjustment: The amount by which the cost was adjusted. *This is not available unless Custom Pricing is enabled.
Credits: Amount of credit that applies to the line item.
Date Transferred: Amount of data transferred in a particular time period.
GB Hours: A gigabyte-hour refers to the number of gigabytes stored on an AWS storage service in a particular hourly period. Click here for more information.
GB Months: References byte-hours, which refer to the number of bytes stored on an AWS storage service in a particular hourly period. Click here for more information.
I/O Requests: Describes the number of data requests from an AWS database service.
IOPS Months: The storage input/output operations per second associated with AWS storage services.
On Demand Hours: The amount of on-demand computing hours used during the reporting period. Click here for more information.
Rate (Blended): For Consolidated Billing accounts, the effective rate for the line item, calculated as an average of the cost of identical Amazon EC2 instances operating in that hour in the same Availability Zone.
Rate (Unblended): The cost per hour for a line item. This is summarized across the hours of a day. For additional information, click here.
Requests: The amount of computing resources used, in the units specified by each service. For example, your service may determine pricing by the amount of storage, number of requests, or hours of operation. For more information about how usage is calculated, click here.
Reserved Coverage Rate: The percentage of total usage hours during the period which had Reserved Instances applied. Click here for more information.
Reserved Hours: The amount of reserved computing hours used during the reporting period. Click here for more information.
Resource Count: This new metric indicates the count of unique resources in a given time frame. This allows customers to understand the number of assets they control and how it ebbs and flows over time.
Taxes: Estimated tax collected by AWS.
Usage Hours: The amount of computing resources used, in the units specified by each service. For example, your service may determine pricing by the amount of storage, number of requests, or hours of operation. For more information about how usage is calculated, click here.
Usage Quantity: Generic usage quantity. Units will vary on dimensions and filters.
Usage Rate: The amount of computing resources used, in the units specified by each service. For example, your service may determine pricing by the amount of storage, number of requests, or hours of operation. For more information about how usage is calculated, click here.