Snowflake
Last updated
Last updated
Euno's Snowflake integration supports auto-discovery of:
Snowflake Views and Tables
In order to integrate with Euno, create a custom role in Snowflake with the permissions listed below. In the code snippet below, we create a user euno_user
, with a role euno_role
.
Euno discovers Snowflake resources by issuing SQL queries on Snowflake's and . The Snowflake role require the Snowflake USAGE grant on a Snowflake warehouse. In the code snippet below, we use the warehouse euno_dwh
. The RSA_PUBLIC_KEY is generated by the source integration (see step 2).
These grants do not provide the euno_role
with access to your data, only to the metadata. To read more about these grants, see:
Go to the Sources page.
Click Add New Source and select Snowflake from the list.
Asterik (*) means a mandatory field.
Name*
Enter a name for your Snowflake source (e.g., "Snowflake - Data Warehouse"
Host*
This is the Snowflake host associated with your Snowflake account. Below are some examples of Snowflake hosts: - mycompany.eu-central-1.snowflakecomputing.com - org-account.us-west-2.snowflakecomputing.com
User*
The Snowflake user to use for the integration
Generate Credentials*
Click on the button to generate an RSA public key.
Role
The Snowflake role to use. If you configured the Snowflake user to have a default role, you can keep this blank.
Warehouse
The Snowflake warehouse to use for queries. If you configured the Snowflake user to have a default warehouse, you can keep this blank.
Cost per credit (USD)
The credit price paid to Snowflake. this will be used to calculate table activity costs.
Observe warehouse information
Tick this option to enable warehouse size information
Toggle Schedule to activate updates.
Configure:
Weekly: Select the days and times for updates.
Hourly: Set the interval in hours (e.g., every 12 hours).
Immediate Cleanup: Remove resources not detected in the most recent successful source integration run.
No Cleanup: Keep all resources indefinitely, even if they are no longer detected.
Click on the 'Advanced' section to display these additional configurations.
Skip SSL certificate verification
Skip SSL certificate verification. This is used in cases where Euno accesses Snowflake through a proxy. We recommend leaving this unchecked.
Auto discover views & tables metadata
Enable this for auto-discovery of Snowflake views and tables metadata.
Use Snowflake system database to collect views
Auto discover Tableau usage
Enable this to for auto-discovery of Tableau's usage data on Snowflake.
Query history table
Database pattern
Use a regular expression to allow or exclude specific databases. ".*" will include or exclude all databases in the warehouse.
Click the Save button to complete the setup.
By default, Euno uses the system view snowflake.account_usage.query_history
to discover the query history.
You might prefer, for security reasons, to limit the rows or columns that Euno integration has access to.
In that case, you can manually create a Snowflake view to expose a subset of the query hisotry. In order for Euno to use this non-default Snowflake view, the following columns, available in snowflake.account_usage.query_history
, must be exposed by the view:
query_tag
total_elapsed_time
bytes_scanned
start_time
end_time
query_type
Make sure you grant Euno permissions to SELECT on this view. Below is an example of creating such a view, and excluding records that were initiated by the user PRIVATE_USER
By default, the Euno integration uses the system view snowflake.account_usage.views
to discover all Snowflake views defined in the snowflake account.
In some environments, users may prefer to grant the Euno integration access to read the metadata of views defined in specific databases, rather than to all the databases in the Snowflake account.
To set up Euno this way, follow these steps:
Grant the Snowflake role used by Euno access to the metadata of views defined in the needed database. For example, to grant the Snowflake role euno_role
access to the metadata of views defined in the database example_database
, execute:
These privileges do not provide the euno_role
with access to the data in these views, only to the metadata. To read more about these privileges, see:
Uncheck the box "Use Snowflake system database to query for Snowflake views" in the integration configuration.
In some environments, users may prefer to grant the Euno integration access to read the metadata of views defined in specific databases, rather than to all the databases in the Snowflake account. For more information, see .
In some environments, users may prefer to limit the rows or columns in the Snowflake query history that Euno integration has access to. For more information, see .
To keep your data relevant and free of outdated resources, Euno provides automatic resource cleanup options. These settings determine when a resource should be removed if it is no longer detected by a source integration. For a detailed explanation on Euno's cleanup strategies, see: .
By default, Euno uses the system view snowflake.account_usage.views
to discover all Snowflake views and tables defined in the snowflake account.
If you prefer not to grant the integration permissions to query the views and tables definitions on all databases, See
By default, Euno uses the table snowflake.account_usage.query_history
to access your Snowflake's query history. If you prefer to use a different table, enter it here. See "" below.