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.
Last updated
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. Most customers, including public companies, are comfortable sharing all of the below data under NDA.
We read Snowflake's query history table to understand what workloads you're running and when, as well as statistics about those workloads (e.g. runtime, time in queue, bytes scanned). This table 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 also remove query text from the data we collect when we generate a savings estimate upon request. All other data in this table is machine-generated.
This table gives a per-query breakdown of compute costs.
This table logs warehouse events, such as warehouses turning on and off and clusters spinning up and down.
These tables contains Snowflake contract information. We use them to calculate financial projections and to let you know if you're on track with your committed spend. We can remove them from the data we collect for a savings estimate upon request.
These tables store hourly credit usage broken down by warehouse and daily credit usage, respectively. We use then to tune our models for new accounts and to check for outliers and certain edge cases.
This lists your warehouses and their settings (e.g. size, type).
This is your Snowflake's account ID. We use it to uniquely identify your account.
Last updated