Preparing to Connect Unravel to Snowflake: Required Configuration Properties
Overview
This page lists the properties you need to provide during Unravel and Snowflake setup. Each property controls how Unravel collects, analyzes, or reports your data. Supplying accurate values ensures a secure and efficient integration.
Property | Scope | Allowed Values | Default | Required | Impact |
|---|---|---|---|---|---|
Data retention properties | |||||
com.unraveldata.history.maxSize.weeks Set the number of weeks to retain query data. Unravel retains query history for this duration and automatically deletes the oldest data. | Global | 1-365 | 24 | Yes | Longer retention increases storage use and will reduce dashboard performance. |
Currency and cost mapping properties | |||||
com.unraveldata.sf.credits.to.isocurrency Specifies the target ISO currency to which Snowflake credit usage should be converted. Snowflake usage is measured in credits, but Unravel can map credits to cost by applying an exchange rate or a configured credit price for the given currency. Setting this property ensures that all cost and chargeback reports are consistently expressed in the specified ISO currency (for example, if the input value is 3, then 1 credit costs $3). | Account | 2.5–5 | 3 | Yes | Direct impact on how Snowflake credit usage is reported and costed. |
com.unraveldata.sf.storage.to.isocurrency Specifies the ISO currency to which Snowflake storage costs are converted. Snowflake tracks storage usage in bytes, which Unravel translates into cost using Snowflake’s pricing model. By setting this property, all storage-related charges and reports are normalized and displayed in the specified ISO currency. | Account | 23–40 | 30 | Yes | Direct impact on storage cost reporting. |
Data load and history properties | |||||
com.unraveldata.sf.look.back.days Specifies the number of days of data history to be considered for loading or processing Snowflake metadata in Unravel. | Account | 0–180 | 180 | Yes | Higher values increase storage needs and initial setup time. Lower values result in faster loads and reports that use a smaller data set. |
Data transfer cost properties | |||||
com.unraveldata.sf.datatransfer.scdc.cost.to.isocurrency Sets the currency and cost mapping for Snowflake data transfers between two accounts on the same cloud/service provider (such as AWS, Azure, or GCP), but in different regions (for example, from us-east-1 to us-central). | Account | 10-1000 | 20 | Yes | Directly affects the data transfer cost displayed in Unravel. |
com.unraveldata.sf.datatransfer.dc.cost.to.isocurrency Sets the ISO currency for calculating Snowflake data transfer costs between two accounts hosted on different cloud service providers (for example, AWS to Azure, Azure to GCP), in any regions (such as us-east-1 to us-central). | Account | 10-1000 | 90 | No | Directly affects the data transfer cost displayed in Unravel. |
com.unraveldata.sf.datatransfer.scsr.cost.to.isocurrency Sets the ISO currency for calculating Snowflake data transfer costs between two accounts on the same cloud provider (AWS, Azure, or GCP), when both are in the same region (for example, us-east-1 to us-east-1). | Account | 0-100 | 0 | No | Directly affects the data transfer cost displayed in Unravel. |
com.unraveldata.sf.datatransfer.scsc.cost.to.isocurrency Sets the ISO currency for calculating Snowflake data transfer costs between two accounts on the same cloud provider (such as AWS, Azure, or GCP), located in different regions but within the same continent (for example, transferring data from Australia to Asia). | Account | 10-100 | 20 | Yes | Directly affects the data transfer cost displayed in Unravel. |
Polling Interval Properties | |||||
com.unraveldata.sf.query.history.poll.secs Specifies how frequently Unravel reads queries from the query_history view. Snowflake has up to a four-hour latency in writing telemetry data. | GLOBAL | 60 min–24 hours | 1 hour | Yes | Lower values provide faster findings and alerts, but increase warehouse cost. Higher values delay alerts and lower costs. |
com.unraveldata.sf.account_usage.poll.secs Specifies how often Unravel reads warehouse metrics from Snowflake. | GLOBAL | 60 min–24 hours | 1 hour | Yes | More frequent polling enables more granular, real-time cost tracking, but increases polling cost. |
com.unraveldata.sf.compute.events.poll.secs Specifies how often Unravel reads warehouse compute event data from Snowflake. | GLOBAL | 60 min–24 hours | 1 hour | Yes | More frequent polling enables more granular, real-time cost tracking, but increases polling cost. |
com.unraveldata.sf.compute.events.poll.secs Specifies how frequently Unravel reads table information from warehouse views. | GLOBAL | 12-24 hours | 24 hours | Yes | Lower value allows faster table insights, but increases polling cost. Higher value reduces polling cost but increases latency. |
Resource, Security, and Encryption | |||||
com.unraveldata.sf.warehouse Specifies which Snowflake warehouse to use for running queries and tasks. | Global | Yes | XS warehouse is required to run the script. A shared warehouse can also be used. | ||
Encryption key sharing mechanism for storage Specify the encryption key sharing mechanism if your Snowflake data is encrypted. | Global | Yes | Required for secure access to encrypted Snowflake data. | ||
Query Threshold Properties | |||||
com.unraveldata.sf.expensive.query.by.cost Analyzes only queries that exceed this credit threshold. Queries below the threshold are ignored. | Account | 1–10 | 1 | No | Lower values increase polling frequency and warehouse cost. Higher values decrease polling frequency and reduce warehouse cost. |
com.unraveldata.sf.parser.expensive.query.by.cost Generate SQL insights only for queries above this threshold. Queries below the threshold are ignored. | Account | 0.1–10 | 0.1 | No | Lower values increase polling frequency and warehouse cost. Higher values decrease polling frequency and reduce warehouse cost. |