GuidesAPI Reference

Viewing Usage Data

Suggest Edits

Introduction to Usage Data

CloudZero's Analytics provides insights into cost data. Yet, behind every cost data, there is an associated usage data. For instance, if you are charged $5 for an EC2 instance for a day, and you used it for 4.2 hours, then 4.2 hours is the usage data, and hours are the pricing unit. The incorporation of this usage and pricing unit data provides additional value for analysis.

📘

Please note that the usage data discussed here is specifically from the CUR (Cost and Usage Report) and does not cover other potential metrics like memory, CPU limits, etc.

Why is Usage Data Important?

Costs can sometimes decrease, not because of reduced usage, but due to external factors like purchasing savings plans. While cost data can be affected by these pricing mechanisms, usage data remains unaffected, offering a clearer, more genuine insight into resource consumption.

Accessing Usage Data in CloudZero

Currently, usage data can only be accessed in the Analytics feature.

When adding a visualization, you'll now notice an option that says "Cost Types and Usage." This is where you can access usage metrics. Among them is "Usage Amount," a metric that showcases the amount of resource consumed without indicating the cost.

📘

Please Note

Unlike cost, usage data requires more discernment to ensure the constructed visuals provide accurate insights. If you are to summarize or aggregate usage data, it is essential to have both "Resource Type" and "Pricing Unit" selected. If these are not selected, you risk aggregating across different units, leading to potentially misleading data.

How to Build with Usage Data

  1. Navigate to analytics.
  2. When adding a visualization, select the option that says "Cost Types and Usage."
  3. Select "Usage Amount."
  4. Always add a filter for date for optimal results.
  5. To ensure accuracy, always include the "Pricing Unit" when dealing with "Usage Amount."
  6. Always keep in mind that aggregating different units (e.g., hours, MB, instances) may not be meaningful. Thus, when summarizing or aggregating, always filter by both "Resource Type" and "Pricing Unit."

📘

Please Note

Currently, only Usage Data from AWS, Azure, GCP, and AnyCost (CBF) is available.

Updated 6 months ago