Pillar 2 — Attribution
Principle: Every credit needs an owner. Cost that nobody owns is cost nobody reduces.
Attribution is where most Snowflake practices break down. Visibility tells you which queries are expensive; attribution tells you whose they are — and without it, every optimization conversation stalls on "is that us?"
Why it matters
You can't run chargeback or showback, you can't hold a team accountable for a spike, and you can't prove a saving belongs to anyone — all because the credit-to-owner mapping is missing. The usual fixes each have a failure mode:
| Pattern | Failure mode |
|---|---|
| Warehouse per team | multiplies idle cost; shared workloads fall through |
Manual QUERY_TAG discipline | decays the moment a tool, script, or new hire skips it |
ACCOUNT_USAGE joins only | after-the-fact; weak on app/team ownership |
| BI-tool's own reports | complete within one tool, blind across the platform |
The common thread: attribution that depends on humans remembering to tag queries erodes. Attribution applied in the query path does not.
What to attribute
| Dimension | Where it comes from |
|---|---|
| Snowflake user / role | session |
| Warehouse | session |
| Client application / BI tool | driver APPLICATION_NAME |
| dbt model / job | dbt-injected query comment / metadata |
| Query fingerprint | computed at the proxy |
| Optimization decision (cache/rewrite/suspend) | the plugin bus |
How chukei enforces it
Because chukei sees every query at the wire-protocol shim,
it stamps team/user/app/dbt metadata at the point of execution — no
QUERY_TAG discipline required. It reads JDBC APPLICATION_NAME, dbt metadata,
and SQL hints, then exports OpenLineage events and OTEL spans so cost maps to a
team or dbt model automatically. See the
FinOps guide for the full attribution model.
Attribution checklist
- Every query resolves to a team or owning workload.
- BI-tool and dbt traffic is attributed, not just hand-written SQL.
- Attribution does not depend on manual
QUERY_TAGdiscipline. - You can produce a per-team spend report for the last 30 days on demand.
- Savings can be attributed to the team or tool that produced them.
Related
- Previous: Visibility · Next: Elimination
- Snowflake cost attribution (FinOps guide)
- Governance pillar — chargeback/showback
See attribution on your own traffic. Pilot chukei on one team and review the per-tool, per-model breakdown — start with the replay simulator.