BigQuery
MCPBigQuery holds the analytical data that tells you how far a problem actually reached. Antimetal runs read-only SQL to quantify impact rather than estimate it.
#What Antimetal does with BigQuery
- Run read-only SQL against your datasets
- Inspect datasets, tables, and schemas
- Check job history for failed or unusually slow queries
- Quantify how many records or users an incident touched
#Connecting BigQuery
-
Open Integrations in the Antimetal dashboard
Go to Integrations in the Antimetal dashboard and find BigQuery.
-
Authorize Antimetal in BigQuery
Click Connect and follow the prompt. Depending on the tool this is either an OAuth handoff or a read-only credential you generate in BigQuery and paste into Antimetal.
-
Confirm the connection
Once BigQuery shows as connected, Antimetal begins pulling from it during investigations. No further configuration is required.
#Permissions and access
Antimetal connects over MCP with read-only access and performs no write operations. The exact scopes depend on the credential you issue in the vendor tool — grant read access only.
All tenant data is processed in isolated environments. See security and compliance for details.
Contact us via Slack or at support@antimetal.com.
Related integrations
Data warehouse queries, schema exploration, and Cortex AI.
Run read-only SQL against ClickHouse databases and tables.
Connect Google Cloud logging, monitoring, and tracing.