Skip to main content
The Radar environment connects Paradime to your data warehouse to surface cost insights about your warehouse spend. Configure it in Workspace Settings > Environments > Radar. A workspace can have more than one cost connection, for example one for each Snowflake account. See Connect several accounts or projects. Set up a Radar cost connection for your data warehouse:

BigQuery

Configure a BigQuery cost connection.

Snowflake

Configure a Snowflake cost connection.

Databricks

Coming soon.

Redshift

Coming soon.

Connect several accounts or projects

Add a cost connection for each Snowflake account, or each set of BigQuery projects, that you want Radar to read. In Workspace Settings > Environments > Radar, click Add connection, then set up the connection for your warehouse. Give each connection a Connection name, so you can tell them apart in Settings and in Radar. If you leave it empty, Paradime uses the Snowflake account, or the BigQuery project IDs, as the name. The Radar settings page lists each cost connection with its name, and its account and database (Snowflake), or its projects and GCS bucket (BigQuery). Click View to open a connection.

The default connection

The first cost connection in a workspace becomes its default, and the list shows it with a Default badge. To make another connection the default, open it with View, select the More (…) menu, then Set as default. If your workspace had a cost connection before you could add more than one, that connection is the default. Nothing else changes for it.

Rules for cost connections

  • One holder for each account or project. A Snowflake account or a BigQuery project can be connected to Radar once in your company. If another connection already holds it, the connection doesn’t save, and the error names that connection and its workspace.
  • One warehouse for each workspace. All the cost connections of a workspace must be on the same warehouse, Snowflake or BigQuery.
  • Snowflake accounts are kept apart. With two or more Snowflake connections, Radar’s cost pages let you look at one account or at all of them. See Several Snowflake accounts.
  • BigQuery spend is shown together. Radar shows the spend of all your BigQuery cost connections together. There is no account selector for BigQuery.

Delete a cost connection

Open the connection with View, select the More (…) menu, choose Delete connection, and confirm. If you delete the default connection, Paradime makes another cost connection the default. When you delete a Snowflake cost connection, or edit it to point at another account, the Warehouse AI Agent Optimizer and the Warehouse AI Autoscaler stop on the old account’s warehouses. They keep running if another cost connection in your company still holds that account. See Snowflake Cost Optimization. If Paradime can’t stop the cost agent when you delete a connection, it keeps the connection and shows an error. Try again. Radar also turns off every alert that can no longer run on the cost connections that are left, for example an alert on the account you removed. See Configure Alerts.