Logging and tracing: Default event table included (Postponed)


This behavior change was originally in the 2024_04 bundle and intended to become enabled by default in the 2024_05 bundle. However, it has been postponed and a new release date has not been determined. This change is not available for testing.

Before the change:

Snowflake does not include an event table by default. To begin using logging and tracing, you must install and activate an event table, set it as the event table for the account to use, then enable logging and tracing. Before you install the event table, log or trace events are not captured, even with logging or tracing enabled.

After the change:

By default, Snowflake includes an event table called SNOWFLAKE.TELEMETRY.EVENTS. If no event table is yet installed and active, the new default event table will be activated for the account.

If logging and tracing were previously enabled and no events captured because there was no active event table, the new default event table will begin capturing logging and tracing events. This will incur costs as described in Costs of Logging.

If you don’t yet have an event table and want to collect logging and tracing events, do nothing. New events will be captured in the SNOWFLAKE.TELEMETRY.EVENTS table in the SNOWFLAKE database, in the TELEMETRY schema.

If you do not want to collect events for the associated objects, you can do any one of the following:

  • Turn off or change the logging and tracing levels appropriately at the respective object levels. For more information, see Setting log level and Setting trace level.

  • Uninstall the applications/connector emitting log and trace events or drop the unnecessary objects.

  • If you do not want any logging and tracing events to be collected at all in the account, execute the following command:


If you create your own event table and set it as active, events will then be collected in that event table, and not in the default event table in the Snowflake database.

Ref: 1598