Versions Compared

Old Version 23

changes.mady.by.user Chichi

Saved on

compared with

New Version Current

changes.mady.by.user Chichi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

K Platform currently offers the following Collector Methods:

Page Tree
root@self
startDepth1
sortnatural

Filter by label (Content by label)
showLabelsfalse
max500
maxCheckboxtrue
sorttitle
showSpacefalse
reversefalse
cqllabel = "source_collector"

...

About Collectors

Excerpt
nameabout

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:

  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.

...

The latest core library needs to be installed prior to deploying a Collector. You can download the latest Core Library and Collector whl via Platform Settings → Sources → Download Collectors

...

Collector

...

Server Minimum Specifications

Excerpt
nameCollectorServerSpec

For the collector to operate effectively, it will need to be deployed on a server with the below minimum specifications:

  • CPU: 2 vCPU

  • Memory: 8GB

  • Storage: 30GB (depends on historical data extracted)

  • OS: unix distro e.g. RHEL preferred but can also work with Windows Server.

  • Python 3.10.x or later

  • Access to K landing directory

...

About Landing Directories

...