...
There are several reasons why you may use a collector vs the direct connect extractor:
You are using the KADA SaaS offering and it cannot connect to your sources due to firewall restrictions
You want to push metadata to KADA rather than allow it pull data for Security reasons
You want to inspect the metadata before pushing it to K
Using a collector requires you to manage
Deploying and orchestrating the extract code
Managing a high water mark so the extract only pull the latest metadata
Storing and pushing the extracts to your K instance.
...
Pre-requisites
Python 3.6 - 3.10
MSDB database / SQLServer DB access
We currently only support SSIS package deployments to the MSDB database and not project deployments which deploy to SSISDB database, please advise KADA if you use project deployments against SSISDB
The collector will need access to the underlying SQLServer Database with permissions to read the following tables is the SSIS main databases:
MSDB.DBO.SYSSSISPACKAGES
<SSIS Logging Database>.DBO.SYSSSISLOG where <SSIS Logging Database> is the database configured for SSIS logging
Access to K landing directory
Access to the KADA Collector repository that contains the SSIS 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 SSIS whl (e.g. kada_collectors_extractors_ssis-#.#.#-py3-none-any.whl)
...
Step 1: Create the Source in K
...
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 SSIS whl via Platform Settings → Sources → Download Collectors
...
Run the following command to install the collector
...