...
K Platform currently offers the following Collector Methods:| Page Tree |
|---|
| root | @self |
|---|
| startDepth | 1 |
|---|
sort | natural| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 500 |
|---|
| maxCheckbox | true |
|---|
| sort | title |
|---|
| showSpace | false |
|---|
| reverse | false |
|---|
| cql | label = "source_collector" |
|---|
|
...
About Collectors
| Excerpt |
|---|
|
Collectors are extractors that are developed and managed by you (A customer of K). KADA provides python libraries that customers can use to quickly deploy a Collector. Why you should use a Collector 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.
|
...
