Overview
OpenSRE connects to Snowflake to help investigate analytics pipeline issues — querying warehouse metadata and query history to surface failed queries, long-running statements, and warehouse usage patterns. Authentication uses a programmatic access token (Bearer). A password field may appear in config schemas but is ignored at runtime —SNOWFLAKE_TOKEN is required.
Prerequisites
- A Snowflake account (trial or production)
- A configured warehouse
- A programmatic access token for API authentication
- A database and schema to query
- Network access from your OpenSRE environment to Snowflake
Setup
There is no dedicatedopensre integrations setup snowflake wizard today. Configure via environment variables or the persistent store, then verify.
Option 1: Environment variables
OpenSRE requires
SNOWFLAKE_ACCOUNT_IDENTIFIER (or SNOWFLAKE_ACCOUNT) and SNOWFLAKE_TOKEN to activate the integration. Generate a programmatic access token in Snowflake under your user’s security settings.Option 2: Persistent store
Credentials
Finding your account identifier
- Open the Snowflake web interface
- Open your account or profile settings
- Locate your account identifier
- Use the full value for
SNOWFLAKE_ACCOUNT_IDENTIFIER
Use the full account identifier shown by Snowflake. Do not remove region or organization information unless your Snowflake deployment documentation explicitly instructs you to do so.
Best practice: dedicated role
Investigation tools
Verify
Troubleshooting
Security
- Use a dedicated Snowflake user for OpenSRE
- Grant only the permissions required for investigations
- Rotate credentials regularly
- Monitor access through Snowflake audit logs