App / Data engineering and quality
Build a Google Cloud cost and activity App
How can I build a reusable Google Cloud cost and activity review? Inspect permitted billing data, reporting limits and a reusable review method in Proforma.
Engineering and operations lead · Finance reviewer
Bring this question into Chat
Your starting prompt.
Build one Google Cloud Cost and Activity App from governed Data and inspectable SQL Models. Include App-local routes for overview, cost drivers, resource evidence, activity and alert setup. Show freshness, reporting basis, unmatched costs and missing history. Keep synthetic sample data separate from live totals. Reuse the Cloud Cost and Activity template when available, preserve its App identity and leave Connections, recipients and schedules for explicit destination-owned setup. Do not create a second App for each route.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Profile keys, row counts, types, missing values and join cardinality. Retain source lineage and concrete exception records so a correction can be checked.
For this task, check
Template installation is explicit after sign-in. It transfers sample definitions, not private customer records, credentials or active schedules. Live ingestion requires a configured Google Cloud Connection.
Before you begin
- Permitted inputs covering the listed reporting windows
- Review the Google Cloud setup and supported export coverage
- Review live Connection and Action availability before enabling recurring work
Build one App from data you have permission to query. Review its definitions and calculations with your team.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Three sample inputs illustrate a proposed App mapping, with missing metrics explicitly visible.
These invented records explain the method. They are not a recorded Proforma run.
| Input | Scope | Evidence state |
|---|---|---|
| Billing | One project; USD | Synthetic complete window |
| Inventory and activity | Exact resource references | Synthetic dated observations |
| Usage metrics | Optional | Not connected |
| App route | Model or state | Review boundary |
|---|---|---|
| Overview and drivers | Cost and comparison Models | Sample totals only |
| Resources and activity | Exact-reference evidence | No inferred historical state |
| Alerts/setup | Inactive reviewed rules | No recipients or schedule |
Method
Keep one atomic App with internal routes and inspectable SQL Models. Bind synthetic sample Sources separately from destination-owned live Sources. Missing optional metrics reduce evidence coverage and cannot be replaced with invented zero usage.
What the result tells you
This is an illustrative design, not an installed App or execution receipt. Inspect the template and explicitly install it after signing in. Live Connections, data mappings, recipients and schedules require separate setup and review.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Start from the reusable template
Inspect the disclosed sample, then sign in and choose Install. Live Google Cloud setup, recipients and schedules require separate review.
Inspect Cloud Cost and ActivityReview Google Cloud setupOr start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.