TELEMETRY schema¶
In the SNOWFLAKE database, the TELEMETRY schema contains tables, views, and stored procedures to support collecting telemetry data.
TELEMETRY tables¶
The SNOWFLAKE.TELEMETRY.EVENTS table is the default event table for telemetry data collection. If you haven’t set up an event table, Snowflake uses the EVENTS table by default to collect telemetry data.
For reference information about columns in SNOWFLAKE.TELEMETRY.EVENTS, see Event table columns.
For more about telemetry in Snowflake, see Logging, tracing, and metrics.
View |
Notes |
|---|---|
EVENTS |
Displays rows for log messages, trace events, and metrics measurements collected in the default event table. |
TELEMETRY views¶
The TELEMETRY schema provides the following view on the default event table, SNOWFLAKE.TELEMETRY.EVENTS.
View |
Notes |
|---|---|
Displays a row for log messages, trace events, and metrics measurements collected in the default event table. |
Accessing views in the TELEMETRY schema¶
The EVENTS_VIEWER or EVENTS_ADMIN roles can execute SELECT operations on the EVENTS_VIEW view. For more information, see Roles for access to the default event table and EVENTS_VIEW.
General usage notes¶
The Snowflake-specific views are subject to change. Avoid selecting all columns from these views. Instead, select the columns that you want. For example, if you want the
namecolumn, useSELECT name, rather thanSELECT *.The rows returned in a query of a view depend on the privileges granted to the user’s current role. When you query a view in the EVENTS_VIEW view, only objects for which the current role has been granted access privileges are returned.
TELEMETRY stored procedures¶
The TELEMETRY schema provides the following stored procedures you can use to manage access to rows selected from the EVENTS_VIEW view.
View |
Notes |
|---|---|
Binds a row access policy to the EVENTS_VIEW by specifying an array of the table’s columns. |
|
Deletes the specified row access policy bound to the EVENTS_VIEW. |