Optional snowflakeAccount-level usage metrics read from the Snowflake ACCOUNT_USAGE schema, covering storage usage, credit consumption, and query activity.
Optional snowflakeCost data aggregated from the Snowflake ORGANIZATION_USAGE schema. Cloud Cost Management must be enabled for your organization while this dataflow is enabled. Any request that enables this dataflow without Cloud Cost Management is rejected with a 422 response. The Snowflake role also needs the ORGANIZATION_BILLING_VIEWER database role to read the underlying cost views; without that role this dataflow collects no data.
Optional snowflakeData Observability, which collects lineage and data quality information from your Snowflake databases so you can explore how data flows and detect and resolve quality issues.
Optional snowflakeRecords from your Snowflake event tables, used to monitor application behavior and identify issues. enabled turns the dataflow on and off as a whole, and the per-record-type toggles in settings select which kinds of record it collects while it is on. The Snowflake role needs usage granted on the database, the schema, and the event table itself; without those grants this dataflow collects no data.
Optional snowflakeOrganization-level usage metrics read from the Snowflake ORGANIZATION_USAGE schema, covering the credit consumption of every account in the organization and the history of data transferred out of Snowflake. Reading that schema requires the ORGADMIN role; without it this dataflow collects no data.
Optional snowflakePer-query logs that let you identify long-running, poorly performing, and expensive queries.
Optional snowflakeSecurity logs from the Snowflake ACCOUNT_USAGE schema, for analyzing the security of your Snowflake account and running threat detection with Cloud SIEM.
Optional snowflakeExecution logs for your scheduled Snowflake tasks, covering start time, end time, status, and any error message.
Generated using TypeDoc
Data Datadog collects from Snowflake, keyed by dataflow id. Each dataflow turns on a distinct kind of collection: set
enabledto start or stop it, and usesettingsto configure what it collects. Defaults listed on each dataflow apply when the account is created; on update, omitted fields keep their current values. Every dataflow reads from Snowflake as the user insettings.username, so that user's role must be granted access to the underlying views; a dataflow enabled without those grants is stored but collects no data.