K uses 2 approaches to load metadata and logs
Extractor: K can connect to the source and extract metadata/logs directly from the source.
Collector: K cannot access the source. A collector can be deployed within the network to extract metadata/logs from the source. Think of this as an agent that is managed by the client.
All Integrations are available in Collector form. Some Integrations are available in Extractor form where it makes sense to (e.g. SaaS products like Snowflake)
We are constantly rolling out new integrations. Reach out to let us know what you need and we can prioritise the roadmap to meet your requirements. |
The list of integrations (and their current status: production ready, beta, in progress, in review and not started) is below.
Integration | Status | Collector available | Extractor available |
|---|---|---|---|
Alteryx | Yes | No | |
AWS Athena |
| Yes | Yes |
AWS DynamoDB |
| No | No |
AWS Redshift | Yes | Yes | |
AWS S3 (via Glue Catalog) | Yes | Yes | |
Azure Data Factory | Yes | Yes | |
Azure SQL | Yes | Yes | |
Cognos | Yes | Yes | |
Databricks | In progress | No (roadmap) | |
DB2 | Yes | No (roadmap) | |
DBT Cloud | Yes | Yes | |
DBT Core (Self Hosted) | Yes | N/A | |
ElasticSearch | |||
Fivetran | Yes | Yes | |
Great Expectations | Yes | No | |
Hevo | Yes | Yes | |
Hightouch | Yes | Yes | |
Informatica | Yes | No | |
Kafka | In progress | No (roadmap) | |
Mysql | Yes | Yes | |
Netezza | |||
Oracle (12C/ADW) | Yes | Yes | |
Oracle Analytics Cloud | Yes | Yes | |
Postgres | Yes | Yes | |
Power BI | Yes | Yes | |
Presto / Trino | |||
SAP Business Objects | |||
SAP HANA | |||
Snowflake | Yes | Yes | |
SQL Server | Yes | Yes | |
SSAS | |||
SSIS | Yes | Yes | |
SSRS | Yes | Yes | |
Tableau Server | Yes | Yes | |
Tableau Cloud | Yes | Yes | |
Teradata | Yes | No (roadmap) | |
Thoughtspot | Yes | Yes |
We can provide guides if you are interested in building your own integrations to K. Please reach out to support@kada.ai to organise a walkthrough.
Related articles