Snowflake Cortex usage¶
Snowflake Cortex supplies usage-history, query-history, and Cortex Search serving rows so Venturi can attribute Cortex charges to users, roles, and warehouses.
Release state
This guide documents the read-only snowflake_cortex connector implemented
in the platform connector surface.
Required access¶
Grant read access to:
| View | Purpose |
|---|---|
SNOWFLAKE.ACCOUNT_USAGE.CORTEX_FUNCTIONS_USAGE_HISTORY |
Read Cortex function usage. |
SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY |
Correlate usage to users, roles, and warehouses. |
SNOWFLAKE.ACCOUNT_USAGE.CORTEX_SEARCH_USAGE_HISTORY |
Read Cortex Search continuous-serving charges. |
Do not grant warehouse mutation, role administration, or data-write privileges.
Setup¶
- Create a Snowflake role for Venturi with the read grants above.
- Bind the integration credential to that role.
- Store the credential reference in Venturi.
- Set
ARGMIN_SNOWFLAKE_CORTEX_LOOKBACK_HOURSif you need a poll window other than 24 hours. - In Venturi, open Administration -> Connectors -> Snowflake Cortex and run Test connection.
Verification¶
- Cortex function and Cortex Search rows appear in the latest sync.
- Query-history correlation resolves user, role, or warehouse fields where available.
- Cortex Search serving charges are labeled as continuous-serving idle cost.
- The connector remains fail-open on upstream read errors.
Rotation and offboarding¶
Rotate the Snowflake credential through your normal privileged-access process. Removing the connector stops new Cortex usage syncs.