Google BigQuery
Know which queries drive your BigQuery bill.
Cloud Intelligence™ reads your Google Cloud billing export and BigQuery audit logs, so you see cost by project, user, table, reservation and query, plus compute and storage recommendations. Right next to the rest of your cloud spend.
Billing export · 30 days of job history · Anomaly checks every 30 minutes
Google BigQuery · October
what we import
BigQuery data, in the dimensions you already use.
BigQuery cost comes from your billing export. BigQuery Intelligence adds audit log dimensions for user, reservation, statement type, query priority and region, plus slot and bytes metrics.
data-produnreservedSELECTQUERY_INTERACTIVEUSprojects/data-prod/datasets/events/tables/page_viewswhat you can do with it
From the BigQuery bill to a decision
Cost by user and table
Drill from billing project to user, dataset, table and query.
Physical storage savings
Recommendations show datasets that cost less on physical storage billing.
On-demand vs editions
Scan TB and slot usage across pricing models, side by side.
Next to your other platforms
BigQuery cost next to your other data platforms and clouds.
Budgets and anomalies
Budgets on BigQuery spend, plus real-time anomaly checks every 30 minutes.
Allocations
Put BigQuery spend on teams by Google Cloud project and label.
set up once
Bring in BigQuery in three steps
Connect your billing account.
Enable detailed usage cost export, then grant our service account read access.
Set up BigQuery Intelligence.
Connect your Google Cloud organization and grant the BigQuery Intelligence permissions.
Dashboard within a day.
We backfill 30 days of jobs. Billing data lands in 24 to 72 hours.
Our analysis queries run in your billing project and use its slots.
Start freeFrequently asked
questions
How does BigQuery data get into Cloud Intelligence?
BigQuery cost comes from your Google Cloud billing export, alongside the rest of your Google Cloud and other providers' spend. BigQuery Intelligence adds job-level detail from a BigQuery audit log sink it sets up in your billing project.
What does connecting the billing account require?
Enable the detailed usage cost export to a BigQuery dataset, then grant our service account Billing Account Viewer on the billing account and BigQuery READER on that dataset. Standalone billing accounts need a Cloud Intelligence Enhanced or Enterprise plan.
What does BigQuery Intelligence run in our project?
It creates a dataset and an audit log sink for your BigQuery jobs in your billing project, then runs scheduled queries there for table discovery, hourly cost updates, reservation mapping and daily dashboard calculations. Cost depends on your audit log volume and pricing model, and jobs use slots from any reservation assigned to that project.
How much history do we get, and how fresh is it?
BigQuery Intelligence backfills the last 30 days of jobs and can take up to 24 hours to fully populate. Costs update hourly, most dashboard widgets update daily at 01:00 UTC, and Cloud Analytics refreshes billing data every hour.
How does real-time anomaly detection work for BigQuery?
You enable it per project. Every 30 minutes we fetch query jobs and apply on-demand pricing to estimate cost as the baseline; to monitor slot reservations, enable it on every reservation administration project.
What doesn't BigQuery Intelligence cover?
The dashboard reports only on BigQuery jobs and reservations from Google's data access logs, which can have gaps such as streaming inserts. It can't calculate storage costs for clones and snapshots, though those still appear in your billing export, and per-job cost during slot autoscaling is approximate.
Bring in BigQuery. Know what every query costs.
Read-only billing access. Recommendations in a day.