Simulation · fictional billing data · about 5 minutes

Find the spending spike

This is a made-up Google Cloud billing export for a fictional company. No cloud account is needed. Use the filters to find what changed between two comparable weeks.

1. Explore two weeks of spend

Week 1
$425
Week 2
$525
Change
+$100

Week 1: Nov 2–Nov 8 · Week 2: Nov 9–Nov 15

$0$50$100Week 1Week 2Nov 2: $60Nov 2Nov 3: $61Nov 4: $61Nov 4Nov 5: $60Nov 6: $61Nov 6Nov 7: $61Nov 8: $61Nov 8Nov 9: $61Nov 10: $61Nov 10Nov 11: $63Nov 12: $85Nov 12Nov 13: $87Nov 14: $85Nov 14Nov 15: $83
Chart summary: Daily spend for all projects, all services, Nov 2 to Nov 15. Week 1 total $425; week 2 total $525, up $100. Highest day: Nov 13 at $87.
Show daily values as a table
DateSpend
Nov 2$60
Nov 3$61
Nov 4$61
Nov 5$60
Nov 6$61
Nov 7$61
Nov 8$61
Nov 9$61
Nov 10$61
Nov 11$63
Nov 12$85
Nov 13$87
Nov 14$85
Nov 15$83

2. Record what you found

3. Choose a follow-up action

Follow-up action

4. See how a budget alert would flag it

Set a weekly budget for all projects. Alerts fire at 50%, 90%, and 100% of the budget as week 2 spend accumulates.

  • 50% · $225

    Alert email on Nov 12

  • 90% · $405

    Alert email on Nov 14

  • 100% · $450

    Alert email on Nov 15

Week 1 spend was $425; week 2 reached $525. analytics-prod alone went from $145 to $245.

A budget alert does not cap spending. It sends a notification when a threshold is crossed; resources keep running and charges keep accruing. Stopping spend requires a separate action, like changing quotas or the workload itself.

What you just practiced

Comparing equal weeks, isolating the project and service behind a change, and knowing what billing data can and can't tell you. The full course has you build this dashboard from a sample billing export.

Notify me when it opens