skip to content
Application library

Cloud operations investigation

Cloud Cost and Activity

A reusable cost investigation with inspectable Models, protected-resource policy and attributed decisions.

Explain Google Cloud cost changes and trace the evidence behind a resource review.

One atomic App with five routes
1
Disclosed synthetic Cloud Sources
4
Versioned sample SQL Models
6
Setup, refresh, rules and review Actions
6
Synthetic fixture and versioned SQL definitions
7
Revisioned settings, reviews and alert state
3
Add to workspaceNo connections, schedules, or messages run automatically.

Cloud cost investigation

Explain the increase. Review the next step.

Start with disclosed synthetic billing and activity records. Inspect service changes, follow supported resource references and keep protected core resources visible. Missing evidence stays unresolved; the App never changes cloud resources.

Prior month
USD 229 · Fictional August net costs
Current month
USD 344 · Fictional September net costs
Increase
USD 115 · Synthetic comparison; no savings claim
  1. Inspect the sample's cost bridge, reporting basis and freshness.
  2. Review resource purpose, available activity and continuing charges.
  3. Prepare an inactive rule; review the destination and release before scheduling.

This is a synthetic walkthrough, not a recorded customer outcome. Live ingestion requires a configured Google Cloud Connection and an existing billing export.

Review Google Cloud setup and availability

The configured-client beta needs a dedicated Google OAuth client. Authorize the saved Connection in the browser, then resume the same bounded run. Shared public Google Cloud OAuth remains planned.

Included workflow

What your team can do

  • Separate sample and live costs
  • Service, SKU and resource drilldown
  • Matched reporting windows and explicit freshness
  • Owner-reviewed rules with schedules off by default

All preview and installed sample rows are synthetic. Live setup requires your own export and project permissions, binds separate Models and preserves the sample. Rules start inactive, recipients unset and schedules off. Reviews do not change cloud resources.

Built for

  • Engineering leads
  • Software teams
  • Cloud operators

Bring your data

  • Disclosed synthetic billing and activity
  • Destination-owned Google Cloud billing export
  • Selected project inventory, activity and curated metrics

Installed artifacts

  • One atomic App with five routes1
  • Disclosed synthetic Cloud Sources4
  • Versioned sample SQL Models6
  • Setup, refresh, rules and review Actions6
  • Synthetic fixture and versioned SQL definitions7
  • Revisioned settings, reviews and alert state3