For the complete documentation index, see llms.txt. This page is also available as Markdown.

Snowflake Metadata

This page describes what Snowflake metadata Espresso reads and why. In general, we look at workload metadata to be able to understand and optimize your traffic patterns.

Espresso will never access your Snowflake data.

We read metadata from Snowflake's ACCOUNT_USAGE and, when available, ORGANIZATION_USAGE schemas. The regular product and the savings estimate use different sets of metadata. Some views depend on your Snowflake edition or enabled features; when a view is unavailable, we skip it.

Most customers, including public companies, are comfortable sharing this data under NDA.

Savings estimate

For a savings estimate, we pull only the metadata below.

Snowflake view
Why we use it

To understand what workloads you're running and when, along with statistics such as runtime, queue time, and bytes scanned.

To understand compute cost at the query level.

To see warehouse events, such as warehouses turning on and off and clusters spinning up and down.

To measure hourly credit usage by warehouse.

To measure daily credit usage across the account.

To calculate financial projections and understand committed spend.

We also run SHOW WAREHOUSES to read warehouse settings such as size and type. We use Snowflake's CURRENT_REGION, CURRENT_ACCOUNT, CURRENT_ORGANIZATION_NAME, and CURRENT_ACCOUNT_NAME functions to uniquely identify the account.

QUERY_HISTORY contains user-generated query text. If your query text is sensitive, we're happy to sign an NDA or a BAA before sharing data. We can remove query text from a savings estimate export upon request. All other fields in these views are machine-generated.

We can also omit RATE_SHEET_DAILY and CONTRACT_ITEMS from a savings estimate upon request.

Regular product

The regular product pulls the savings estimate metadata above, plus the views below. This broader set lets us report on all Snowflake spend, understand account configuration, and identify cost outliers and edge cases. Many of these views are feature-specific and optional; unavailable views are skipped.

Category
Additional Snowflake views

Workload and warehouse activity

ACCESS_HISTORY, SESSIONS, WAREHOUSE_CLUSTER_UTILIZATION, and WAREHOUSE_LOAD_HISTORY (for accounts where warehouse-load collection is enabled)

We take daily snapshots of catalog and security views so we can understand how the account changes over time. We also read warehouse settings through Snowflake's warehouse API.

Last updated