What you will be able to do
- Create an event table and set it as the consumer account's active event table
- Enable event sharing for an app instance with the right privilege and settings
- Explain why consumer event sharing stays in one region and how a provider centralizes events from many regions
- Diagnose a failed or half-working Native App installation from its symptoms
1.Setting the consumer account's active event table
The logs, traces and metrics an app emits land in the consumer account only if that account has an active event table. An account can hold many event tables, but only one is active at a time. Without one, nothing the app emits is stored locally, even when its procedures call the logging and tracing APIs directly. Setup takes two statements: create the table in a database and schema, then make it the account's active table.
CREATE EVENT TABLE event_db.event_schema.my_event_table;ALTER ACCOUNT SET EVENT_TABLE=event_db.event_schema.my_event_table;Because the setting is account-wide, changing it affects more than the app. Choosing a different table under Event table location in Snowsight redirects every event generated in the account, including events from unrelated workloads. If the account already has an active table, add the app's events to that one instead of switching. The consumer also pays ingestion and storage costs for the event table. Snowflake doesn't charge for enabling event sharing itself.
Checkpoint 1 of 4· Fill the gap
A consumer has just created an event table so that the app's logs and traces are stored locally. Which keyword completes the statement that makes this table the active event table?
ALTER ? SET EVENT_TABLE=event_db.event_schema.my_event_table;The active event table is an account-level setting. You set it with ALTER ACCOUNT, not on the app, database or schema. Only one table can be active at a time, and changing it redirects every event generated in the account, not just the app's events.
Source: docs.snowflake.comSources1
2.Enabling event sharing during and after installation
The provider's event definitions decide whether the event table has to exist before installation. Event definitions and event sharing approval explains how definitions filter what reaches the provider. At install time, required definitions are turned on automatically, so the consumer must set up an event table before selecting Get. Once installed, sharing for those definitions can't be turned off. Optional definitions also need an active event table, but the consumer can accept or decline each one, and neither choice blocks installing or using the app.
After installation, sharing is managed per app instance by a role with the MANAGE EVENT SHARING global privilege. ACCOUNTADMIN holds it and can grant it to other roles. In Snowsight, open Catalog » Apps, select the app, open Settings, go to the Events and logs tab, turn on the optional definitions you want, and save. The older SHARE_EVENTS_WITH_PROVIDER property still works, but it reads TRUE only when every definition is enabled. It can be set to FALSE only when all of the app's definitions are optional.
Checkpoint 2 of 4· Check yourself
An installed app has one required event definition and two optional ones, and all three are enabled. Later the consumer decides to stop sharing as much as possible with the provider. What can they actually do?
Required definitions, and the event sharing they need, are turned on at install and can't be turned off afterwards. Only optional definitions can be toggled. SHARE_EVENTS_WITH_PROVIDER can be set to FALSE only when every definition is optional. Setting the event table to NONE only stops events from being stored locally, and enabled sharing keeps sending them to the provider.
“event sharing and the required event definitions are enabled during installation and cannot be disabled later”Source: docs.snowflake.com
3.Collecting events from consumers in other regions
Consumer event sharing never crosses regions. Shared events go to a designated provider account in the consumer's own region. A provider whose app runs in many regions therefore receives telemetry in many places. Collecting it into one account is done by the provider at the organization level, not by the consumer.
Centralized event sharing solves this with an event routing table. It holds rules that map source regions to a destination account, given as org.account_name (the account name, not the locator). A rule naming specific regions takes precedence over the default rule, which uses REGIONS=('ALL'). A typical setup sends European regions to one analysis account and everything else to another. An organization can have only one active routing table, with up to 200 rules. Activating it is a single statement.
ALTER ORGANIZATION SET EVENT ROUTING TABLE org_table FOR ALL APPLICATION LISTINGS;Two operational details trip providers up. Replacing the rules of an active table with ALTER EVENT ROUTING TABLE fails unless you add FORCE. DROP EVENT ROUTING TABLE fails while the table is active, so deactivate it first with ALTER ORGANIZATION UNSET EVENT ROUTING TABLE FOR ALL APPLICATION LISTINGS;. To see which table is active, run SHOW EVENT ROUTING TABLE ON ORGANIZATION FOR ALL APPLICATION LISTINGS;. It returns no rows when none is active. Routing telemetry across regions also puts it under regimes such as GDPR, so check compliance before you pick a destination.
Checkpoint 3 of 4· Check yourself
Your app has consumers in AWS US East, Azure West Europe and GCP Asia regions, and they all have event sharing enabled. You want all of their telemetry in one analysis account in your organization. What achieves this?
Consumer event sharing only delivers events to a provider account in the consumer's own region. To bring events from several regions into one account, the provider sets up centralized event sharing at the organization level with an event routing table. The consumer doesn't configure this.
“The Snowflake Native App Framework supports centralized event sharing, which allows an app to share telemetry messages from different regions to a central location.”Source: docs.snowflake.com
4.Diagnosing failed and half-working installations
Most installation failures fall into a few groups, and the symptom usually tells you which. Start with whatever happened first: the install wouldn't start, the install failed partway, or the app installed and then broke.
| Symptom | Likely cause | Fix |
|---|---|---|
| The listing is invisible or Get fails for a non-admin role | Role lacks IMPORT SHARE and its paired privilege | Grant them from ACCOUNTADMIN, or install as ACCOUNTADMIN |
| Buy is unavailable on a paid app | Role lacks PURCHASE DATA EXCHANGE LISTING | Grant the privilege and meet the payment criteria |
| Install blocked by an event requirement | App has required event definitions and no active event table exists | CREATE EVENT TABLE, then ALTER ACCOUNT SET EVENT_TABLE |
| Container app won't install | Snowpark Container Services not enabled | Enable it for the account |
| App installed but fails on first data access | Reference unbound, or the object isn't accessible to the app | Bind the reference to an accessible object |
| App installed but a feature fails on warehouses or session info | A manual-only privilege such as MANAGE WAREHOUSES or READ SESSION was never granted | Run the GRANT statements the provider documents |
| App suddenly non-functional for everyone | Owner role was dropped | Drop the app and reinstall it |
Setup script errors and missing grants show up differently. Under manifest_version: 2 the setup script can create warehouses and compute pools directly, because those privileges are granted at install. A script that relies on a manual-only privilege, though, fails until the consumer grants it. Compute pools are another trap: an app can't share a pool with another app or with the consumer's own workloads, so a script that expects an existing pool won't find a usable one.
Cross-region problems come from the provider side. A consumer in a remote region can only install once Auto-fulfillment for remote regions has replicated the application package there. Even then, a change to a release directive reaches that region only after the package is replicated again. A consumer who sees an old version, or no app at all, in a remote region is usually waiting on replication, and nothing in the consumer account will fix it.
Checkpoint 4 of 4· Check yourself
After a clean install of a manifest_version: 2 app, its setup script created its own warehouse without any problem. A week later, the app's feature that resizes and suspends warehouses fails with a privilege error. What is the most likely cause, and how do you fix it?
Under manifest_version: 2, CREATE WAREHOUSE is granted automatically, so creating the warehouse works. MANAGE WAREHOUSES is one of the manual-only privileges, so a feature that needs it fails until the consumer grants it. A dropped owner role would break the whole app for everyone, not one feature. Automatic grants can't be revoked.
“Some privileges are not automatically granted to the app. Consumers must manually grant these privileges when installing or upgrading an app.”Source: docs.snowflake.com
Practise it for real
Prepare a consumer account to install an app that has required event definitions, then confirm events are captured
1.Run CREATE EVENT TABLE event_db.event_schema.my_event_table; in an existing database and schema.
Why: An app with required event definitions can't be installed until an event table is ready.
You should see: The event table is created in event_db.event_schema.
2.Run ALTER ACCOUNT SET EVENT_TABLE=event_db.event_schema.my_event_table; as a role allowed to change account parameters.
Why: Only the active event table receives the app's logs and traces, and there is one per account.
You should see: The account parameter now points at the new table.
3.Install the app from its listing, reviewing the Security details (including App events) before selecting Get.
Why: Required definitions turn on at install and can't be disabled afterwards, so check them first.
You should see: The app installs, with sharing for its required definitions already on.
4.Using a role with MANAGE EVENT SHARING, open the app's Settings, go to Events and logs, turn on the optional definitions you want, and save.
Why: Optional definitions are the consumer's choice and are enabled per app instance.
You should see: The chosen optional definitions show as enabled, and the app's events start appearing in my_event_table.
Stuck? Get a nudge
If the install is still blocked on events, run SHOW PARAMETERS LIKE 'EVENT_TABLE' IN ACCOUNT to check which table is actually active.
Sources
(6)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.
“only one of them can be set as the active event table in a Snowflake account at a time”
↩︎ Setting the consumer account's active event table“Changing the event table causes all events generated in the account to be stored in the new location.”
↩︎ Setting the consumer account's active event table“Snowflake does not charge you to enable event sharing.”
↩︎ Setting the consumer account's active event table“Optional event definitions require an active event table, but they are not required to install or use the app.”
↩︎ Enabling event sharing during and after installation“Use a role with the MANAGE EVENT SHARING global privilege.”
↩︎ Enabling event sharing during and after installation“SHARE_EVENTS_WITH_PROVIDER is TRUE only when all event definitions are enabled, otherwise it is FALSE.”
↩︎ Enabling event sharing during and after installation“After enabling event sharing with a provider, you cannot revoke access to shared trace events and log messages.”
↩︎ Enabling event sharing during and after installation“This feature does not share data across different regions.”
↩︎ Collecting events from consumers in other regions“Snowflake sends the shared events to a designated provider account within the same region as your account.”
↩︎ Exam trap 1“event sharing and the required event definitions are enabled during installation and cannot be disabled later.”
↩︎ Exam trap 2“If the consumer sets the event table to NONE, the events are not stored in the consumer account. They are still shared with the provider.”
↩︎ Prediction“event sharing and the required event definitions are enabled during installation and cannot be disabled later”
↩︎ Checkpoint - 2.
“If the provider includes required event definitions in the app, the consumer must set up an event table before installing the app.”
↩︎ Enabling event sharing during and after installation - 3.
“allows an app to share telemetry messages from different regions to a central location”
↩︎ Collecting events from consumers in other regions“Rules with specific regions take precedence over rules for ALL.”
↩︎ Collecting events from consumers in other regions“Each organization can have only one event routing table activated for it.”
↩︎ Collecting events from consumers in other regions“If the event routing table is currently activated for an organization, and you do not use the FORCE option, the command fails.”
↩︎ Collecting events from consumers in other regions“The Snowflake Native App Framework supports centralized event sharing, which allows an app to share telemetry messages from different regions to a central location.”
↩︎ Checkpoint - 4.
“Compute pools cannot be shared across apps or between an app and your non-app workloads.”
↩︎ Diagnosing failed and half-working installations“you must drop the broken app and reinstall it”
↩︎ Diagnosing failed and half-working installations - 5.
“a change to a release directive takes effect in a remote region only after the application package is replicated to that region.”
↩︎ Diagnosing failed and half-working installations - 6.
“The provider does not have to add additional logic to check whether the consumer has granted the required privileges.”
↩︎ Diagnosing failed and half-working installations“Some privileges are not automatically granted to the app. Consumers must manually grant these privileges when installing or upgrading an app.”
↩︎ Checkpoint