Snowflake
Euno's Snowflake integration supports auto-discovery of:
Usage information of applications using Snowflake, like Tableau
Setting up Snowflake integration
Required Snowflake Permissions
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 password and a role euno_role
.
Euno discovers Snowflake resources by issuing SQL queries on Snowflake's system database and information schema. The Snowflake role require the Snowflake USAGE grant on a Snowflake warehouse. In the code snippet below, we use the warehouse euno_dwh
.
These grants do not provide the euno_role
with access to your data, only to the metadata. To read more about these grants, see:
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 Control which views metadata Euno has access to.
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 Using a non-default query history view.
Setup Steps
To integrate a Snowflake account please follow the below steps:
Integration Configuration
Asterik (*) means a mandatory field.
Using a non-default query history view
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
Control which views metadata Euno has access to
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 databaseexample_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.
Discovered Resources
The Euno-Snowflake integration discovers the following resources:
Snowflake views
Last updated