slashpeak
Solutions

Cost attribution

Every query finding names who ran it (person or service account), which tool sent it (dbt, Looker, Sheets, Airflow…) and which environment it hit, so each fix reaches the team that owns it.

Get my free BigQuery scanView all products

On BigQuery

Available

Job-id prefixes, job labels and SQL comment headers classify dbt, Looker, Dataform, Airflow, Connected Sheets, scheduled queries, and the console. Dataset name tokens infer prod / staging / qa / dev.

BigQuery product

On Snowflake

Waitlist

Coming soon: QUERY_HISTORY user_name, client application, and warehouse labels mapped onto the same attribution dimensions so a Snowflake finding names a team too.

Snowflake product

On Databricks

Waitlist

Coming soon: query.history executed_by, client, and warehouse id mapped onto the same user / tool / environment dimensions.

Databricks product
How it works

A finding without a name never gets fixed

  1. 01

    Classify at fetch time

    No extra vendor APIs. The job record already has the signal.

  2. 02

    Roll up by person and tool

    Top users, workload mix, and environment share on every finding.

  3. 03

    Hand the list to the owner

    The dashboard is a conversation starter, not a mystery score.

Blog

More from the blog

Databricks system table catalog path into ranked cost findings

Diagnosing Databricks costs with system tables

system.query.history and system.compute.warehouses rank full scans, idle warehouses, and shuffle-heavy jobs. SlashPeak never needs SELECT on your tables.

13 min read
Shuffle exchange where every map node sends rows to every reduce node

Databricks Photon shuffle costs and join key layout

Photon speeds up a shuffle join; it does not shrink it. Adaptive execution helps at the edges, but an unclustered join key still burns DBUs every run.

10 min read
Z-order curve versus liquid clustering over Delta files

Z-ordering vs. liquid clustering in Databricks

ZORDER and liquid clustering write min/max stats so Photon can skip files. The wrong columns, or a stale table, means it still reads everything.

10 min read
Databricks SQL warehouse DBU chart with idle auto-stop tail

Databricks SQL warehouses: auto-stop and idle DBUs

A serverless warehouse with a 10-minute auto-stop bills 10 minutes after the last query. Oversizing is a separate leak, and system tables show both.

13 min read

Take control of your warehouse bill

Understand, reduce and govern your cloud data spend with SlashPeak — starting today.

Start for freeGet a demo
  • 30-day free trial
  • No credit card
  • Read-only access
  • Set up in minutes