Connector docs — GCP
Exactly what CostMon asks for to read GCP
CostMon runs a read-only BigQuery SQL query against the FOCUS-formatted billing export table you point it at. It never calls any other GCP API.
What CostMon calls
The literal API surface, nothing more
- BigQuery — Jobs.query
- A SELECT against your <project>.<dataset>.<table> billing export, aggregated by day, service, region, SKU, and account, for the sync window.
What you supply
Credential and config fields
service_account_jsonService account JSON keysecretrequired
project_idProject IDrequired
datasetDatasetrequired
tableTablerequired
Minimum permission
Copy this, not a broader role
Scope of access
What GCP access can't reach
- Compute Engine instances, GKE clusters, or anything else running in your project
- Any BigQuery dataset other than the one you point the connector at
- Any GCP API besides BigQuery's query endpoint
Worth knowing
- The export must be FOCUS-conformant. CostMon maps FOCUS columns directly; a non-FOCUS export won't parse.
Troubleshooting
Setup errors and what they mean
- service_account_json must be valid JSON
- The credential you pasted isn't a parseable JSON key file. Re-download it from the GCP console.
FAQ
Common questions about the GCP connector
Does CostMon see my GCP resources, like VMs or GKE clusters?
No. The only call CostMon makes is a read query against the billing export table you configure. It never calls Compute Engine, GKE, or any resource-management API.
What if my billing export isn't FOCUS-formatted?
The gcp connector expects a FOCUS v1.x export. Enable FOCUS export in your GCP billing account settings first, or use the generic FOCUS export connector if you're pulling from somewhere else.
A rate you looked up will change again.
Provider pricing pages change without notice. CostMon tracks the bill that pays for it.