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_SERVING_USAGE_HISTORY`	Read Cortex Search continuous-serving charges.

Grant the relevant Snowflake database role, or imported privileges on the SNOWFLAKE database, to the dedicated read-only role. Do not grant warehouse mutation, role administration, or data-write privileges. Account Usage views can lag; the connector labels its source window and latest upstream timestamp. Snowflake documents the serving view and its latency in CORTEX_SEARCH_SERVING_USAGE_HISTORY.

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 VENTURI_SNOWFLAKE_CORTEX_LOOKBACK_HOURS if you need a poll window other than 24 hours.
In Venturi, open Integrations and select 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 continues operating and skips upstream read errors without interrupting other syncs.
The read-only inventory test succeeds under the dedicated role and fails if that role can mutate warehouses, data, or grants.

Rotation and offboarding¶

Rotate the Snowflake credential through your normal privileged-access process. Removing the connector stops new Cortex usage syncs.