Page Comparison

About Collectors

Collectors are extractors that are developed and managed by you (A customer of K).

...

There are several reasons why you may use a collector vs the direct connect extractor:

1. You are using the KADA SaaS offering and it cannot connect to your sources due to firewall restrictions

2. You want to push metadata to KADA rather than allow it pull data for Security reasons

3. You want to inspect the metadata before pushing it to K

Using a collector requires you to manage

1. Deploying and orchestrating the extract code

2. Managing a high water mark so the extract only pull the latest metadata

3. Storing and pushing the extracts to your K instance.

...

Pre-requisites

• Python 3.6 - 3.9

• Access to the KADA Collector repository that contains the Redshift whl

  • The repository is currently hosted in KADA’s Azure Blob Storage. You will be given a SAS token to access the repository. Reach out to KADA Support (support@kada.ai) if you do not have access.

  • Download the Redshift whl (e.g. kada_collectors_extractors_redshift-#.#.#-py3-none-any.whl)

  Access to K landing directory

• Access to Redshift (see section below)

...

Create a Redshift user. This user MUST be either (one or the other below, we generally recommend 2.)

1. Be a Superuser. Refer to https://docs.aws.amazon.com/redshift/latest/dg/r_superusers.html to view all required data.

   Code Block
   ALTER USER <kada user> CREATEUSER; -- GRANTS SUPERUSER

2. Be a Database user with:

   1. Unrestricted SYSLOG ACCESS refer to https://docs.aws.amazon.com/redshift/latest/dg/c_visibility-of-data.html. This will allow full access to the STL tables for the user.

      Code Block
      language sql
      ALTER USER <kada user> SYSLOG ACCESS UNRESTRICTED; -- GRANTS READ ACCESS

   2. Select Access to existing and future tables in all Schemas for each Database you want K to ingest.

      1. List all existing Schema in the Database by running

         Code Block
         language sql
         SELECT DISTINCT schema_name FROM svv_all_tables; -- LIST ALL SCHEMAS

      2. For each schema above do the following to allow the user select access to all tables inside the Schema and any new tables created in the schema thereafter.

         You also must do this for ANY new schemas created in the Database to ensure K has view of it.

         Code Block
         language sql
         GRANT USAGE ON SCHEMA <schema name> TO <kada user>; GRANT SELECT ON ALL TABLES IN SCHEMA <schema name> TO <kada user>; ALTER DEFAULT PRIVILEGES IN SCHEMA <schema name> GRANT SELECT ON TABLES TO <kada user>;

PG Catalog

The PG tables are granted per database but generally all users should have access to them on DB creation. In the event the user doesn’t have access, explicit grants will need to be done per new DB in Redshift.

...

Some python packages also have dependencies on the OS level packages, so you may be required to install additional OS packages if the below fails to install.

You can download the Latest Core Library and Redshift whl via Platform Settings → Sources → Download Collectors

...

Run the following command to install the collector

...