This chapter covers how cloud cost is read once it has been allocated: which reports answer which question, which signals show a movement early, and how the same numbers are reported to engineering, management and finance. A cost report is the answer to a question, not a table with every column. The chapter therefore starts from the questions a team asks every day, every week and every month, and shows which dimension, which period and which cost basis answer each.

What this chapter covers

Reports. What a cost report contains and how a saved view turns an analysis into a repeatable question; which dimensions the billing data offers and what filtering, grouping and segmenting each do to the total; when a dashboard beats a report and when it does not; how two periods are compared without the calendar writing the result; how several providers are reported in one currency without mistaking an exchange-rate movement for usage; and how fresh a report's data is, since every provider keeps changing its figures after the first delivery.

Signals. Which movements a detector derives from a scope's own history, how the providers find and report anomalies, and why an anomaly is a question for its owner; which trends and drivers sit behind a month's change and how a report splits them into rate, usage and mix.

Audiences. Which cadence belongs to which decision, daily for operations, weekly for the team, monthly for the close; how a report subscription brings a report to its readers without a login; what management wants to see and what finance needs to carry the cloud invoice into the month-end close. How the monthly review turns these reports into decisions is the subject of the guide Monthly cloud cost review: agenda and templates.

One rule runs through the whole chapter: a report states its cost basis, its data cut-off and its currency, or it cannot be reproduced. Billed cost shows how the invoice moves; effective cost shows what a team consumed once commitments and discounts are spread. Both are right, but never on the same line.

Key terms

  • Cost report: the saved answer to one question, with its dimension, period, cost basis and filters.
  • Dashboard: several reports on one surface, for analysis rather than as a record.
  • Report subscription: a report that reaches its readers on a fixed cadence instead of waiting to be looked up.
  • Cost insight: a hint the data gives on its own, before anyone asks.
  • Anomaly: a movement a scope's history makes unlikely, and so a question for that scope's owner.
  • Segment: a named slice of cost that means the same thing in every report.
  • Effective cost: the cost basis in which commitments and discounts are spread over usage, and the one that shows a team's trend.

Neighbouring chapters

The chapter before this one, Allocation and ownership, supplies the dimensions a report groups by: a report can only tell apart what allocation has made distinguishable, and the owner in a report is the same owner allocation names. The chapter after it, Budgets, forecasts and finance, reads the same reports in the other direction: a budget checks the total against an amount, a forecast extends the trend, and both need the cost basis and the data cut-off this chapter fixes. The providers' consoles, where most reports are built, belong to the chapter Tooling; the billing data they read from belongs to Billing data and standards. The overview of every chapter is the handbook.