Managing the Snowflake Connector for Google Analytics Raw Data

本主题介绍在安装和配置连接器后可能需要执行的典型任务。

更改连接器的引入间隔

The connector periodically checks and downloads data from BigQuery. The check is done every 8 hours by default, but it can be changed. If you want to set the new interval for checking and downloading data, please use the CONFIGURE_INGESTION_INTERVAL procedure defined in the PUBLIC schema:

CALL CONFIGURE_INGESTION_INTERVAL(<interval_configuration_name>)

可能的间隔配置以及在后台使用的 cron 定义：

EVERY_15_MINUTES   -   */15 * * * * UTC
EVERY_30_MINUTES   -   */30 * * * * UTC
EVERY_1_HOUR       -   0 * * * * UTC
EVERY_4_HOURS      -   0 3/4 * * * UTC
EVERY_8_HOURS      -   0 3/8 * * * UTC
EVERY_1_DAY        -   0 3 * * * UTC

Note

无法设置自定义 cron 表达式。

示例用法：

CALL CONFIGURE_INGESTION_INTERVAL('EVERY_1_HOUR')

The list of supported intervals can be also printed using the LIST_SUPPORTED_INGESTION_INTERVALS procedure defined in the PUBLIC schema:

CALL LIST_SUPPORTED_INGESTION_INTERVALS()

设置警报

要设置警报，请执行以下步骤：

  1. Sign in to Snowsight as a user with the ACCOUNTADMIN role.
  2. In the navigation menu, select Catalog » Apps.
  3. Search for the Snowflake Connector for Google Analytics Raw Data, then select the tile for the connector.
  4. In the page for the Snowflake Connector for Google Analytics Raw Data, go to the Settings section and then select Email alerts from the menu on the left.

这将显示电子邮件警报配置页面。

  1. In the Email Address field, provide a Snowflake verified email address.

Note

您必须指定与 Snowflake 账户关联的电子邮件地址。

  1. In the Email Frequency field, select how often you would like to receive alerts:
  • Immediately - you will receive notifications according to the values set in table synchronization.
  • Once per day - you will receive notifications once a day at 12PM UTC.

Note

仅当发生无效操作（如错误）时，才会发送警报。

  1. Select Save changes to start receiving email alerts.

禁用警报

To stop receiving alerts, select Stop receiving alerts in the email alerts configuration page.

升级连接器

连接器升级由应用程序的提供商自动管理。

缩放连接器

You should start your work with the Connector using a X-Small as it will most likely give you a sufficient performance. However, if you are experiencing any Connector slowdowns, you may want to try gradually increasing the warehouse size and evaluating whether you see any performance boosts at each step. Whether the Connector gains anything from scaling the warehouse depends on a few factors, such as the number of properties or the amount of data each of them has.

For insights on how to resize the warehouse see Resizing a warehouse in Working with warehouses.

Note

If you are constantly experiencing ingestion errors related to insufficient memory and are already using a LARGE or X-LARGE warehouse, then you can try to resolve this issue by decreasing the MAX_CONCURRENCY_LEVEL parameter on a warehouse from 8 (default) to 4.

更改连接器的仓库

It is possible to change the warehouse that the Snowflake Connector for Google Analytics Raw Data uses for its internal tasks without reinstalling the connector. First, make sure that the Connector is paused. It can be done eiter via UI or using the PAUSE_CONNECTOR procedure. Then, you need to grant the Connector access to the new warehouse:

GRANT USAGE ON WAREHOUSE <new_warehouse_name> TO APPLICATION snowflake_connector_for_google_analytics_raw_data;

After the access is granted, execute the UPDATE_WAREHOUSE procedure defined in the PUBLIC schema:

CALL UPDATE_WAREHOUSE('<new_warehouse_name');

重新对连接器进行身份验证

In order to change the secret, external access integration or the security integration used by the connector without re-installation, you need to execute the UPDATE_CONNECTION procedure defined in the PUBLIC schema. Ensure, that all of the new objects are defined as described in Configuring the Snowflake Connector for Google Analytics Raw Data using SQL and that the connector has all of the required grants.

CALL UPDATE_CONNECTION('<new external access integration>', '<new secret>', '<new security integration>');

自动禁用不可访问的 Google Analytics 属性

连接器具有一种机制，可以自动禁用不可访问的 Google Analytics 属性，以防止因尝试引入非无限期存在的数据而产生不必要的成本，并会提醒您无法再引入数据。该属性被视为不可访问，如果数据引入在过去 7 天内失败，则可能会自动禁用该属性。

在灾难恢复和故障转移期间继续进行

If you want to ensure that the connector will be able to continue data ingestion during a deployment outage, you need to set up the sink database failover to a replica account. For details, see Failing over databases across multiple accounts.

Moreover, after an outage you need to manually install the Snowflake Connector for Google Analytics Raw Data on your replica account, because the connector itself can not be replicated. After the installation it will synchronize itself with the replicated sink database.

Note

为防止数据损坏，您不能有两个连接器实例，一个在主账户上，另一个在副本账户上，同时将数据引入接收器数据库。

当发生部署中断并且接收器数据库故障转移到副本账户时，请执行以下步骤：

  1. 登录用于复制接收器数据库的辅助账户。
  2. Install the Snowflake Connector for Google Analytics Raw Data on your secondary account. The connector will synchronize itself with the replicated sink database. The instance on your primary account goes into a read-only state after an outage, so data will not be corrupted at this point.
  3. 如果要在部署再次可用后返回到主账户，您需要先删除两个连接器。必须确保一致的连接器状态。
  4. 使用复制机制将数据从辅助账户复制回主账户。
  5. 接收器表中的数据与辅助账户上的接收器表同步之后，在主账户上重新安装连接器。

更新数据引入选项

You can use the UPDATE_INGESTION_OPTIONS procedure defined in the PUBLIC schema to modify default ingestion options for certain properties. This procedure allows you to change the following:

  • EXCLUDE_NULLS - Remove fields containing null values from the ingested data. Setting this value to TRUE can improve the data ingestion throughput. The default value is FALSE.
  • DISABLE_AUTO_RELOADS - Disables auto reloading data. For more details about auto reload see Data ingestion model for the Snowflake Connector for Google Analytics Raw Data. Setting this value to TRUE can reduce credit consumption, but late data won’t be ingested into Snowflake. This property cannot be set to true for the FRESH_DAILY export type. The default value is FALSE.
  • ENABLED_EXPORT_TYPES - A list of export types, which connector will try to ingest data for. Possible values are: DAILY, FRESH_DAILY, INTRADAY, USERS and PSEUDONYMOUS_USERS.
CALL UPDATE_INGESTION_OPTIONS(
    PROPERTY_IDS => ['<property_1>', '<property_2>'],
    EXCLUDE_NULLS => <boolean>,
    ENABLED_EXPORT_TYPES => ['DAILY', 'FRESH_DAILY' 'INTRADAY', 'USERS', 'PSEUDONYMOUS_USERS']
 );

Note

To leave an ingestion option unchanged, omit the argument from the UPDATE_INGESTION_OPTIONS procedure call.

按需刷新扁平化视图

You can use the REFRESH_VIEWS procedure defined in the PUBLIC schema to trigger an on-demand refresh of the flattened views. The flattened views are refreshed automatically daily by default. For more details about views see Accessing data ingested by Snowflake Connector for Google Analytics Raw Data.

CALL REFRESH_VIEWS();